Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Backing up remote database schemas on i5/OS
This topic provides instructions on backing up remote Workplace database schemas on IBM® i5/OS using the savWpRmtDb.sh script. The instructions describe running the script manually from a QShell session. You can also schedule the script to run periodically as part of a comprehensive backup and recovery strategy.
Before performing this task, you should have backed up your Workplace profile. For more information, see Backing up a profile on i5/OS. Follow these steps to back up remote database schemas on i5/OS:
- If IBM WebSphere Portal Express is not installed on the system containing the remote schemas, copy the file /QIBM/ProdData/PortalExpress/V6/Tools/savWpRmtDb.sh from a system where WebSphere Portal Express is installed to a location in the Integrated File System (IFS) of the system where the remote database schemas are located.
- Stop the profile associated with the remote database schemas you are backing up.
- Start the QShell Interpreter on the system containing the remote database schemas by entering the following on an i5/OS command line:
STRQSH
- Change to the directory containing the savRmtDb.sh file.
If WebSphere Portal Express is not installed on the system, change to the directory where you copied the savRmtDb.sh file.
If WebSphere Portal Express is installed on the system, change to the Workplace tools directory by entering the following:
cd /QIBM/ProdData/PortalExpress/V6/Tools
- Enter the following command to back up the remote database schemas:
savWpRmtDb.sh parameters
The command takes the following parameters as listed in the table, with these being required:- a list of schemas (-t)
- either a media device (-m) or save file library (-s)
Parameter names are case-sensitive.
Parameter Description -help (-h) Displays help for the command
-schemaList (-t) Specifies a list of schemas to save. Schemas listed must be separated by commas, with no spaces in between.
-mediaDevice (-m) Specifies a media device to save to
-saveFileLib (-s) Specifies a library where save files are created to save the data. The library name must be 10 characters or less.
-logDir (-l) Where to save log files for this command. If a log directory is not specified using this parameter, logs are created by default in /savRstWp60.
-verify (-v) Verifies the command. If this parameter is used, the command outputs what would be done according to the parameters being used, without actually performing the backup.
Examples:
-
In the following example, eight schemas are saved to library savlib1:
savWpRmtDb.sh -schemaList lib1,lib2,lib3,lib4,lib5,wcs01,wcs02,wcs03 -saveFileLib savlib1
- The following is an example of using the i5/OS command Add Job Schedule Entry (ADDJOBSCDE) to make the savRmtDb.sh script run on a regular schedule. The ADDJOBSCDE command must be run from an i5/OS command line. In this example, the savWpRmtDb.sh parameters are the same as in the previous example. However, the script is run with a job name (JOB) of WPSRMTBU on a frequency (FRQ) of once per week with a schedule day (SCDDAY)
of Sunday and a schedule time (SCDTIME) of 11:30 p.m:
The profile associated with the remote schemas must be stopped for this command to complete successfully. In order for a scheduled backup such as the following to complete successfully, it would have to be coordinated with a shutdown of the profile.
ADDJOBSCDE JOB(WPSRMTBU) CMD(QSH CMD('/qibm/proddata/portalexpress/v6/tools/ savWpRmtDb.sh -t lib1,lib2,lib3,lib4,lib5,wcs01,wcs02,wcs03 -s savlib1')) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*SUN) SCDTIME('23:30:00')For detailed information on the ADDJOBSCDE command and its parameters, see the IBM eServer™ i5 Information Center at http://publib.boulder.ibm.com/iseries/.