Cisco ANA Registry Backup and Restore
Cisco ANA Registry Backup and Restore
Note Any new AVM that is added will not be deleted after the restore. So if a backup is made, and then another
AVM is added, and the last backup is restored, the newly added AVM will still be available after the
restore.
Note SSH daemon must be enabled in order for the backup and restore to work.
Overview
The backup procedure is used to perform data backup once a week. It operates through the UNIX cron
mechanism. The factory settings entry in the cron table (crontab) runs the backup procedure every
Sunday at 1:00 AM. To activate the backup procedure, the user needs to remove the comment for the
relevant line in the cron table.
The restoration is done manually by executing the restore.csh script.
Backed-Up Content
The data that has been backed-up is:
• Cisco ANA registry (Golden Source)
• cron table (crontab)
Backup Procedure
The backup script is a scheduled task. It operates through cron.
The backup files are stored in the following directory,
~[ana install directory]/db/db_backup/[date+time].
Note The filler [date+time] is a directory name composed of a date and time of the backup. For example,
~[ana install directory]/db/db_backup/200604130404/ is created on 13 April 2006 at 4:04 AM. By
default the cron table executes the backup procedure every Sunday at 1:00AM.
Note Important: Reinstalling the server from scratch (install.pl) deletes the sheer user, and the content under
it. The default backup directory is located under sheer, and it can be changed (see configuring the registry
below) to another location, which must be accessible to writing for the sheer user, for example, the
default directory permissions are: (“drwx------ 2 sheer sheer 512 Sep 24 02:54”)
It is also recommended that you do not locate the backup directory under /tmp, since this directory is
deleted whenever the server is rebooted, and the backup content will be lost.
To maximize data safety, it is recommended that you copy the backed-up directory to another external
storage location, for example, a DVD or another server’s disk.
The location is configurable through the registry. For more information, refer to registry path,
avm11/agents/integrity/backup.
Figure A-1 displays the backup registry entries.
Note Refer to crontab(1) in the Solaris documentation for a detailed explanation about the cron table format.
Note If null appears after running ./mc.csh localhost 8011 integrity.executeTest backup this is normal.
Troubleshooting
The following message may be displayed when using the backup procedure:
1. sheer@sh-nv210-1v5 [~/Main]% The authenticity of host ‘127.0.0.1 (127.0.0.1)’ can’t be
established.
DSA key fingerprint is 4e:cb:81:1c:bf:38:5c:ec:6e:b8:a8:d3:3b:d4:fe:b9.
Are you sure you want to continue connecting (yes/no)?
Solution
From sheer user do the following:
ssh 127.0.0.1
Restore Procedure
Install the Cisco ANA gateway. For more information, refer to the Cisco Active Network Abstraction
Installation Guide. Note that you will need to login as root.
To restore from a backup:
Step 1 Change the directory /export/home/[ana install directory]/Main/scripts by executing the following
command:
cd ~[ana install directory]/Main/scripts
Step 3 Once the restoration is successful, initialize the Cisco ANA gateway by running the following command:
su - sheer
cd Main
./mvm.csh
Note When the registry is restored from the last backup, if new AVMs were added after this last registry
backup, all the new AVMs that were added after this backup are still present.
Note This section is provided as an example only of the Oracle database backup and restore procedure. For
more information see the:
Oracle Database Recovery Manager Quick Start Guide
Overview
Oracle databases have a backup and restore Recovery Manager (RMAN) tool. To use this tool for online
backup, the Oracle database must be in ARCHIVELOG mode, (see Create RMAN Catalog Database).
RMAN maintains the bookkeeping intelligence of backup and recovery files and backs up data at the
block level. Therefore, RMAN can significantly speed up backups and reduce the server load by using
incremental backups.
Figure A-2 displays the Oracle Database Backup diagram.
RMAN db
RMAN
sheer.db
187199
For more information about RMAN for Oracle 10g see the:
Oracle Database Recovery Manager Quick Start Guide
Note RMAN is convenient to use. However, it only provides a command line interface, and it still demands
database analyst knowledge when recovery is needed.
Be sure that the backup data and RMAN catalog are located on a different disk from where the Oracle
database (data files, redo logs, and control files) are located. Both can however reside on the same
ANA database server.
The Oracle Enterprise manager (GUI) can be used to set up RMAN.
Alternatively, the RMAN configuration is explained in the following sections, and should be
implemented sequentially:
Note These steps are provided as an example only of the Oracle database backup and restore procedure. For
more information see the:
Oracle Database Recovery Manager Quick Start Guide
The default password for an Oracle sys account after Oracle installation is change_on_install. Replace
this sys account password with the correct sys account password for the ANA database.
Step 1 To ensure the database is in archive log mode, enter the following:
SQL> alter system set log_archive_dest_1 = ‘location=</var/tmp/oradata/arch>’ SCOPE=BOTH;
SQL> alter system archive log start;
Backup Database
To backup the database, do the following:
Step 1 Create a file called full_backup.rcv. Inside the file, enter the following text.
run {
allocate channel d1 type disk;
backup
incremental level = 0 cumulative
database
format ‘/var/tmp/backup/db_%d_%s_%p_%t’
include current controlfile for standby
tag = ‘ANA_WEEKLY_FULL’;
sql ‘alter system archive log current’;
backup
archivelog all delete input
format ‘/var/tmp/backup/ar_%d_%s_%p_%t’;
release channel d1;
}
Make sure the directory such as ‘/var/tmp/backup’ has enough space to hold the backup and also the
Oracle user has write permissions.
Step 2 Run the rman command:
rman target / catalog rmanuser/rmanpassword@rcat @full_backup.rcv
Recover Database
To recover a database, do the following:
• Please put a desirable restore time in the SET UNTIL TIME clause.
• After a time based recovery, it is important to immediately do another database backup, since at this
time, the database can only be recovered after last recovery time, and all the previous backups used
for the last recovery are no longer recoverable.