WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Backing up and restoring a clustered environment on i5/OS

This topic describes the sequence of operations for backing up and restoring a clustered environment on IBM® i5/OS.

Each step includes a link to the topic containing detailed instructions, as well as an example command. Examples are based on the following cluster topology:

 

System A:

 

System B:

 

Parent topic:

Backup and restore on i5/OS

 

Backing up a clustered environment on i5/OS

The following is the sequence of operations for backing up a clustered environment on i5/OS:

  1. Save the HTTP server data for each node in the cluster using the savHttpInstance.sh command. For example:

    savHttpInstance.sh -p wpe07 –s wpe07htp –l /wpe07htplog –f -c -nd

  2. Back up the Deployment Manager profile using the savNdDm.sh command. For example:

    savNdDm.sh -p wpe07 -s wpe07DM -l /wpe07dmLog -u wpsadmin -w wpsadmin -f -c

  3. Back up each node in the cluster using the savWpProfile.sh or savNdProfile.sh command. For Base WebSphere Application Server profiles federated into the cluster, use savWpProfile.sh. For Network Deployment profiles, use savNdProfile.sh.

    For example:

    On System A:

    savNdProfile.sh -p wpe07 -s wpe07N1 -l /wpe07n1log -t *none -n -f -c

    On System B:

    savNdProfile.sh -p wpe08 -s wpe08N2 -l /wpe08n2log -t *none -n -f -c

  4. Back up any remote database schemas using the savWpRmtDb.sh command. For example:

    savWpRmtDb.sh -t NDWPECOM07,NDWPELDS07,NDWPELMS07,NDWPEWPS07 -s wpe07dbs -l /wpe07dbslog

    To determine which database schemas are associated with a particular profile, use the savNdProfile.sh command with the -verify (-v) parameter. For example: savNdProfile.sh -v -p wpe07 -s dummy -f

 

Restoring a clustered environment on i5/OS

The following is the sequence of operations for restoring a clustered environment on i5/OS:

  1. Restore any remote database schemas using the rstWpRmtDb.sh command. For example:

    rstWpRmtDb.sh -s wpe07dbs -l /wpe07dbslog -x -t NDWPECOM07,NDWPELDS07,NDWPELMS07,NDWPEWPS07

  2. Restore each node in the cluster using the rstNDProfile.sh command. For example:

    On System A:

    rstNDProfile.sh -p wpe07 -s wpe07N1 -l /wpe07n1log -n -f

    On System B:

    rstNDProfile.sh -p wpe08 -s wpe08N2 -l /wpe08n2log -n -f

  3. Restore the Deployment Manager profile using the rstNdDm.sh command. For example:

    rstNdDm.sh -p wpe07 -s wpe07DM -l /wpe07dmLog -u wpsadmin -w wpsadmin -f

  4. Restore HTTP server data using the rstHttpInstance.sh command. For example:

    rstHttpInstance.sh -p wpe07 -s wpe07htp -l /wpe07htplog -f