Backup and Restore of WebSphere Application Server configuration

                      Backup & Restore of IBM WebSphere Application Server Configuration


Backup configuration in WebSphere


One of the major activity that we can perform in Websphere as a pre-requisites when ever we intended to perform any major configuration changes like Fix Pack upgrade ,Interim Fix upgrade, JDK upgrade etc.

For any mission critical application, taking frequent backups is essential for recovering from severe errors. In the case of WebSphere Application Server, setting up of the application server environment is a demanding task and it is not an easy to repeat the setup if something bad happens. So, its wise to take backups whenever we make the first setup or when we do configuration changes.

Depending upon our diskspace availability two types of backups is possible .

1) Full Backup


A full backup can be performed by running the ./backupConfig command from the<WAS-ROOT>/bin directory. 
This will backup all the configuration files under<WAS-ROOT>. We can go for a full backup if we have enough disk space.
<WAS-ROOT> is the directory where the Network Deployment Package is installed.

Syntax:

We need to run the command from profile_root/bin 

./backupConfig.sh

This will stop the nodeagent process and the servers linked to that nodeagent as managed servers. All the files under the <profile-root> will be backed up into a zip file named WebsphereConfig_DATE.zip where DATE is in the format YYYY-MM-DD. This zip file will be placed in the current directory. The information about the backup will be logged into a file named backupconfig.log under the <profile-root> 


Note : This is bit expensive operation by default the servers under the profile which is being backed up will be stopped. This option instructs the command, not to stop any of the servers. The backup obtained will be a snapshot of what is there in memory. This will be suitable for production environments.

If we want to have a different name for the backup file, we can do so by running the command as follows. We can also generate log in a different name.

./backupConfig.sh [backup_filename] [-logfile <filename>] -username  <username> -password  <password> -nostop

Ex:

./backupConfig.sh  /opt/waslogs/backup/ProfileName.B4_MQ8Upgrade.zip  -username  <username> -password  <password> -nostop


2 ) Individual profile backup



We can perform backup for specific profiles by running the ./backupConfig command from the <WAS-ROOT>/bin directory with –profileName option.

e.g.

./backupConfig.sh –profileName <Profilename>

An alternative to this is to run the ./backupConfig command directly from the

<PROFILE-ROOT>/bin directory without –profileName option.

<PROFILE-ROOT> is the directory where the configuration files for the particular profile is located.



3) TAR BACKUP


This is not a WebSphere provided method where we can take tar backup of complete cell or was installation directory or folder using tar command.


Syntax:

tar -cvzf  <Backupfile name.tar.gz> <Original Folder>



RESTORING THE BACKUP FILE


The restoreConfig command is a simple utility to restore the configuration of your node after backing up the configuration using the backupConfig command. By default, all servers on the node stop before the configuration restores so that a node synchronization does not occur during the restoration

The backup created in the above process can be restored for an emergency using restoreConfig command provided by Websphere. The usage of the command is as follows:

restoreConfig backup-file [-location <location>] [-quiet] [-nowait] [-logfile <logfile>]

[-replacelog] [-trace] [-username <username>] [-password <password>] [-profileName

<profileName>] [-help]


Ex:


./restoreConfig /opt/wasbkup/WebSphereConfig_2022-01-22.zip  -username  admin -password  admin -nostop


-location

This is the location to which the backup will be restored. The default location is <WASROOT>/config. This option will be useful if we have backed up the configuration of individual profile and want to restore it to the <PROFILE-ROOT>/config directory.

-nowait

This instructs the command to restore the configuration without stopping the servers.This is similar to nostop in backupConfig.

Note that the restoreConfig command will not run if you do not mention the backup-file name.

Comments

Post a Comment

Popular posts from this blog

IBM WebSphere - Synchronize a node (syncNode)

Image
  IBM WebSphere - Synchronize a node (syncNode) Before we get into synchronization, let's talk about nodes and the master configuration. The master configuration is a collection of XML files that contain all sorts of information about a cell, such as the security settings and the applications in the cell. A node contains one or more WebSphere application servers. When a managed nodes is federated into the dmgr, the node needs to be synchronized with the master configuration so that the node is using the dmgr configuration. The synchronization is always from Dmgr to Nodes and it never happens vise versa. If you made any changes from the node side it will be cleared during next synchronization process. Let's consider a common example. You make some change in the WebSphere admin console, and you are presented wit the Save option. Selecting save updates the master configuration. This will cause the node to be out of sync with the master configuration. To know if a node is synchroni...
Read more

Daily usage Linux Commands for Any Middleware Administration

Daily usage Linux Commands for Any Middleware Administration Processes related: ------------------ $ ps -ef | grep <process_name> ----- will show the process ID of the proces $ ps -eaf --> to see the Process ID's $ telnet <hostname> <Port_Number> --> It is used to check whether port(server) is listening or not $ scp    -r     file_Name     username@hostname:path  ----- If you want to copy a file from one linux server to another sever $ kill -9 PID ----- Killing an unwanted process $ kill -3 PID ----- Used to take thredDump of the process $ ssh username@servername --> Command used to login to server $ nslookup <host_name> --> Query the nameserver for the IP address of the given HOST optionally using a specified DNS server (To identify the server ip_address by using nslookup command ) $ crontab Minute Hour DayOfMonth Month DayOfWeek (eg: 30 08 10 06 * /home/was/full-backup) ----- Used to scheduled a job on Li...
Read more