The following topics explain how and when Prime Network performs backups.

Transcription

1 CHAPTER 8 These topics describe how to back up and restore your data: Backing Up Your Data, page 8-1 Restoring Prime Network Data, page 8-4 For information on how to backup and restore an embedded database, see Working With an Embedded Database, page Backing Up Your Data The following topics explain how and when Prime Network performs backups. The procedures described in these topics do not back up the Oracle database. If you have installed an embedded database, you can follow the procedure in Backing Up an Embedded Database and Prime Network, page Otherwise, see your Oracle documentation for instructions on how to back up the database. Overview of the Backup Procedure, page 8-1 Changing the Periodic Backup Time, page 8-3 Performing a Manual Backup, page 8-4 Overview of the Backup Procedure Which Files Are Backed Up The following topics provide an overview of the standard backup procedure and its default settings. Prime Network backs up its registry data, encryption keys, and reports using the operating system cron mechanism. If you have installed an embedded database, see Backing Up an Embedded Database and Prime Network, page Table 8-1 lists the directories that are backed up. 8-1

2 Backing Up Your Data Chapter 8 Table 8-1 Directories Backed Up by Prime Network Type of Data Location Description Registry information NETWORKHOME/Main/registry Prime Network registry, which includes changes made since the installation (new soft properties, Command Builder commands, alarm customizations, and so forth) General information NETWORKHOME/Main/.encKey SSH encryption key files NETWORKHOME/Main/to_backup Other user-specified data NETWORKHOME/Main/reportfw/rptdocu ment Prime Network reports 1 1. Some report data is stored in the database, so you must back up both the database and the Prime Network data to capture all report information. How Many Backups Are Saved By default, Prime Network saves five backups. Where Backups Are Stored When the backup files are created, they are stored in the directory NETWORKHOME/backup. If you reinstall the server using the install.pl script, the user network-user and the content under it is deleted. This includes the default backup directory. (network-user is the operating system account for the Prime Network application, created when Prime Network is installed.) In this example, network-user is network38. You can change the location, but the user network-user must be able to write to the location. For example, the default directory permissions are: ( drwx network38 network Sep 24 02:54 ) We recommend that you do not locate the backup directory under /tmp, since this directory is deleted whenever the server is rebooted, and the backed-up content lost. To maximize data safety, we recommend that you copy the backed-up directory to an external storage location, such as a DVD or a disk on a different server. When Backups Are Performed Changing the Default Backup Directory By default, backups every 12 hours at 4:00 a.m. and 4:00 p.m, as defined in the crontab file. You can change the backup time using the procedure described in Changing the Periodic Backup Time, page 8-3. To restore data, you must execute the restore.pl command manually. You can change the default backup directory by editing the registry using the runregtool.sh script. Changes to the registry should be performed only with the support of Cisco. For more information, contact your Cisco account representative. 8-2

3 Chapter 8 Backing Up Your Data Before You Begin Make sure that network-user has the necessary write permissions for the new backup directory. Log into the gateway as network-user. (network-user is the operating system account for the Change the directory to the Main directory: # cd $ANAHOME/Main Step 3 Specify the new backup directory by providing a complete pathname for new-directory: #./runregtool.sh -gs set site/mmvm/agents/integrity/backup/backupoutputfolder new-directory Changing the Periodic Backup Time Do not change the periodic backup schedule if you have installed an embedded database (see Working With an Embedded Database, page 11-1). If this is required, contact the Technical Assistance Center. The integrity service runs regular backups, along with other integrity tests, according to the settings in the system crontab file. Registry backups are controlled according to commands in the crontab file. To change the backup time, you must edit the crontab file. The crontab file consists of lines, where each line contain six fields: min hour day-of-month month-of-year day-of-week command The fields are separated by spaces or tabs. The first five are integer patterns that can contain the following values: Field Acceptable Values min Minute in range 0-59 hour Hour in range 0-23 day-of-month Day in range 1-31 month-of-year Month in range 1-12 day-of-week Day in range 0-6 (0=Sunday). command Command To specify days using only one field, set the other fields to *. For example, 0 0 * * 1 runs a command only on Mondays. In the following example, core files are cleaned up every weekday morning at 3:15 a.m.: 15 3 * * 1-5 find $HOME -name core 2>/dev/null xargs rm -f 8-3

4 Restoring Prime Network Data Chapter 8 The sequence 0 0 1,15 * 1 runs a command on the first and fifteenth of each month as well as every Monday. Use this procedure to change when Prime Network backs up its registry (this command also changes when Prime Network will run integrity tests; see Archiving and Purging Data, page 10-4). Log into the gateway as network-user (where network-user is the operating system account for the Edit the cron table as follows: # crontab -e Step 3 Make your changes to the crontab file. Step 4 Save your changes by entering Ctrl-x, and confirm your changes by entering y. Step 5 Restart the gateway server. Performing a Manual Backup This procedure explains how to perform an on-demand backup contains the information described in Table 8-1 on page 8-2. This procedure does not back up any database information. For more information, see Overview of the Backup Procedure, page 8-1. Step 3 Log into the gateway as network-user (where network-user is the operating system account for the Change the directory to the Main/scripts directory: # cd $ANAHOME/Main/scripts Start the backup: # backup.pl backup-folder It is normal for null to appear in response to this command. Restoring Prime Network Data The following procedure restores the Prime Network data that is backed up, as listed in Which Files Are Backed Up, page 8-1. The procedures described in these topics do not restore the Oracle database. If you have installed an embedded database, you can follow the procedure in Restoring an Embedded Database and Prime Network, page Otherwise, see your Oracle documentation for instructions on how to restore the database. 8-4

5 Chapter 8 Restoring Prime Network Data To restore Prime Network data from a backup: Step 3 Step 4 Step 5 Log into the gateway as network-user (where network-user is the operating system account for the Stop the gateway server and all units: # cd $NETWORKHOME/Main # networkctl stop # rall.csh networkctl stop From the NETWORKHOME/Main directory, change to the directory NETWORKHOME/Main/scripts: # cd scripts Execute the restoration script: # restore.pl backup-folder Once the restoration is successful, initialize the Prime Network gateway by running the following commands: # cd Main # networkctl restart 8-5

6 Restoring Prime Network Data Chapter 8 8-6