Backing Up and Restoring the Master Server

The software includes utilities for completely backing up and restoring a Master Server. These utilities are found in the N1SPS4.1-home/server/bin directory.

You can choose to back up or restore either or both the Resource Manager and the Postgres database. By default, the Resource Manager directory and the Postgres database contents are backed up or restored. You can skip one or the other of these components by using the appropriate command line arguments.

How to Back Up a Master Server

Before You Begin

Before you back up the Master Server, you must stop the Master Server. Any Plans or Preflights must be stopped, as well as any other tasks, such as comparisons.

Be sure to specify an output directory when you run the backup script. If you do not specify an output directory, the resultant backup file is saved in the N1SPS4.1-home/server/bin directory. If you are uninstalling and then reinstalling the Master Server and the backup file is in this directory, the backup file is deleted. Consequently, you are not able to restore the Master Server.

Steps

1. Stop the Master Server.

2. On the Master Server, change users so that you are root or the owner of the application.

3. Change to the directory where the backup script is located.

   % cd N1SPS4.1-home/server/bin

   N1SPS4.1-home is the home directory of the application.

4. Start the backup by typing:

   % ./cr_backup.sh options

   The following options are available for use with the cr_backup.sh command.

   -b

   Master Server base directory.

   -q

   Quiet. No informative messages are printed.

   -nors

   Skip the Resource Store back up.

   -nodb

   Back up the Resource Manager only.

   -o directory

   Save the backup file in this directory. The backup script verifies that you have write permissions for the directory you specified. If you do not have write permissions for this directory, the script generates an error.

   If you do not specify a directory, the files are saved in the N1SPS4.1-home/server/bin directory.

   -z

   Compress the resulting backup file using UNIX compression.

   -1 logfile

   Write log output to the logfile file instead of the default logfile file.

   -gz

   GZip the resulting backup file if gzip is in PATH.

   -shutdown

   Shut down the Master Server without prompting the user.

   -u

   Print this information.

   -h

   Print this information.

   The script warns that if you proceed Master Server process will stop, if it is not already stopped, thereby canceling any tasks, such as searches, plans, and comparisons, that are in progress

5. Type y to proceed with the backup.

   The script shows the progress of the backup and displays the location of the backup tar file.

   The script restarts the Master Server.

How to Restore a Master Server

Before You Begin

Before performing a restore, you must have an installation of the Master Server that contains no data.

Steps

1. Stop the Master Server.

2. On the Master Server, change users so that you are root or the owner of the application.

3. Change to the directory where the backup script is located.

   % cd N1SPS4.1-home/server/bin

   N1SPS4.1-home is the home directory of the application.

4. Start the restoration by typing:

   % ./cr_restore.sh options

   The following options are available for use with the cr_restore.sh command.

   -b

   Master Server base directory

   If you do not use the -b option to specify a directory to in which to restore the backup files, the files are put in the current directory, N1SPS4.1–home/server/bin. If you do not have write permissions for this directory, the software generates an error.

   -q

   Quiet. No informative messages are printed

   -nors

   Skip the Resource Store restore

   -nodb

   Skip the database restore

   -f backupfile

   Restore the contents of the backupfile file

   -l logfile

   Write log output to the logfile file instead of the default logfile

   -t temp_directory

   Use the temp_directory directory to save temporary files

   -overwrite yes

   Overwrite the existing data during restore

   -u

   Print this information

   -h

   Print this information

   The script verifies that the backup files do not contain any errors. The script warns that if you proceed the Master Server process will stop, if it is not already stopped, thereby canceling any tasks, such as searches, plans, and comparisons, that are in progress.

5. Type y to proceed.

   The script warns that any data currently in the databases will be overwritten with the data in the backup files.

6. Type y to proceed.

   The restoration proceeds. The script starts the Master Server: