A Backup is a routine runs everyday/week/month per your schedule, takes a copy of the file system or Snapshot of entire OS and so on.
backupConfig command
The backupConfig command is a simple utility to back up the configuration of your node to a file.
By default, all servers on the node stop before the backup is made so that partially synchronized information is not saved. For more information about where to run this command, see the “Using command line” tools article in the information center. If you do not have root authority, you must specify a path for the backup file in a location where you have write permission. The backup file will be in zip format and a .zip extension is recommended.
In a UNIX or Linux environment, the backupConfig command does not save file permissions or ownership information. The restoreConfig command uses the current umask and effective user ID (EUID) to set the permissions and ownership when restoring a file. If it is required that the restored files have the original permissions and ownership, use the tar command (available on all UNIX or Linux systems) to back up and restore the configuration.
Usage
The following example creates a new file that includes the current date:
![[AIX]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/aixlogo.gif)
![[HP-UX]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/hpux.gif)
![[Linux]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/linux.gif)
![[Solaris]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/solaris.gif)
backupConfig.sh WebSphereConfig_2005-04-22.zip
![[Windows]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/windows.gif)
backupConfig.bat WebSphereConfig_2005-04-22.zip
![[z/OS]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ngzos.gif)
backupConfig.sh WebSphereConfig_2005-04-22.zip
The following example creates a file called myBackup.zip and does not stop any servers before beginning the backup process:
![[AIX]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/aixlogo.gif)
![[HP-UX]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/hpux.gif)
![[Linux]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/linux.gif)
![[Solaris]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/solaris.gif)
backupConfig.sh myBackup.zip -nostop
![[Windows]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/windows.gif)
backupConfig.bat myBackup.zip -nostop
![[z/OS]](http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ngzos.gif)
backupConfig.sh myBackup.zip -nostop Example: I am using windows. My server profile is located at: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\AppSrv01Secure
backupConfig.bat file for my server is located at: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\AppSrv01Secure\bin Run command prompt (cmd) and open bin folder of profile and run this command. Change backup file name as you want. See image.
backupConfig.bat myBackup.zip -nostop
Source: IBM