IBM Storwize v3700 Configuration Backup

-
Since IBM Storwize storage system doesn't use typical command line interface, you need to know its special commands in order to carry out your stuff via CLI. 

 I needed to create backup of storage configurations and transfer them to my local computer. Things didn't go quiet easy as after logged in to CLI you will notice even "ls" or "cd" commands are not exist.

 Here is how I carry out this task together with the commands and results.

lsdumps


To check the previous backed up files, use "lsdumps":

 IBM_2072:STGHostname:superuser>lsdumps
id filename
0  ethernet.7806628-1.trc
1  livedump.7806628-1.140819.163538
2  snap.7806628.tgz
3  7806628-1.trc
4  svc.config.cron.bak_7806628-1
5  svc.config.cron.sh_7806628-1
6  svc.config.cron.xml_7806628-1
7  svc.config.cron.log_7806628-1

svcconfig


To create the backup, "svcconfig" is the command:

 IBM_2072:STGHostname:superuser>svcconfig backup
................................................................................ 
................................................................................                                           ................................................................................                                           ................................................................................                                            
CMMVC6155I SVCCONFIG processing completed successfully
After backup finished successfully, there would be 3 new files created as per lines 8,9 and 10:

 IBM_2072:STGHostname:superuser>lsdumps
id filename
0  ethernet.7806628-1.trc
1  livedump.7806628-1.140819.163538
2  snap.7806628-1.tgz
3  7806628-1.trc
4  svc.config.cron.bak_7806628-1
5  svc.config.cron.sh_7806628-1
6  svc.config.cron.xml_7806628-1
7  svc.config.cron.log_7806628-1
8  svc.config.backup.xml_7806628-1
9  svc.config.backup.log_7806628-1
10 svc.config.backup.sh_7806628-1

PSCP


It is actually not possible to use WinScp to transfer config backups over offside due to Storewize lack of basic commands such as "cd". But "pscp" does the trick. 

 You need to download it from it's official website (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html), then using following commands to transfer config backup files to your computer: 

 If you downloaded "pscp.exe" in your windows desktop folder, and
using "superuser" as default admin account of Storwize, and
10.8.224.163 is IP of Storwize, and
you would like to transfer the backups to your desktop folder, then
the command would be:

 C:\Users\username\Desktop>pscp superuser@10.8.224.163:/tmp/svc.config.backup.* C:\Users\username\Desktop/
superuser@10.8.224.163's password:
svc.config.backup.log     | 27 kB |  27.8 kB/s | ETA: 00:00:00 | 100%
svc.config.backup.sh      | 13 kB |  14.0 kB/s | ETA: 00:00:00 | 100%
svc.config.backup.xml     | 221 kB | 221.2 kB/s | ETA: 00:00:00 | 100%



Comments

Post a Comment

Popular posts from this blog

Linux and AIX user non expiry and force password change at first login

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more