Cisco Cisco StadiumVision Mobile Reporter 维护手册
© 2011 Cisco Systems, Inc. All rights reserved.
Page 15 of 21
Restoring the Primary Server
After a backup is done on the primary server, you can do a restore on the primary
system right away. Assuming the secondary server is configured, you can do an
automated or manual restore on the secondary server as well. This restore will be
able to use the files that the backup task will place on the secondary server at
completion of the backup step. The backup files will be on both systems.
system right away. Assuming the secondary server is configured, you can do an
automated or manual restore on the secondary server as well. This restore will be
able to use the files that the backup task will place on the secondary server at
completion of the backup step. The backup files will be on both systems.
In the event a disaster occurs, you can manually copy a backup. For example if the
primary server loses a backup set that exists on the secondary server, you can copy
the backup from the secondary to the primary, and then do a restore. One item to
note is that the backup is really comprised of two files with the same name but
different suffices. The file sv-2.2*.tar is a tar file with all the data of the backup. The
file sv-2.2*.chksum is a checksum file containing the md5 signature of the tar file.
You must copy both files. The restore script will verify the md5 signature.
primary server loses a backup set that exists on the secondary server, you can copy
the backup from the secondary to the primary, and then do a restore. One item to
note is that the backup is really comprised of two files with the same name but
different suffices. The file sv-2.2*.tar is a tar file with all the data of the backup. The
file sv-2.2*.chksum is a checksum file containing the md5 signature of the tar file.
You must copy both files. The restore script will verify the md5 signature.
The backups on the primary server are stored in a directory /var/sv/BACKUP. On
the secondary server, the backups are copied to /var/sv/RESTORE. When the
manual restore screen is displayed, it lists backups in either directory, concatenated
together. This allows you to run manual restore on either the primary or the
secondary. An automated restore only looks for files in the RESTORE directory.
the secondary server, the backups are copied to /var/sv/RESTORE. When the
manual restore screen is displayed, it lists backups in either directory, concatenated
together. This allows you to run manual restore on either the primary or the
secondary. An automated restore only looks for files in the RESTORE directory.
Two components warrant special explanation. The backup system assumes that
StadiumVision will run with an automated High Available configuration. In this
configuration, some of the Unix level files are different between the primary and
secondary servers. Therefore, the Unix files are not automatically restored in the
RestoreTask on the Dashboard.
StadiumVision will run with an automated High Available configuration. In this
configuration, some of the Unix level files are different between the primary and
secondary servers. Therefore, the Unix files are not automatically restored in the
RestoreTask on the Dashboard.
Likewise, the schedule of tasks to run in the primary database and the secondary
database will be different, due to the existence of the backup and restore tasks.
Therefore, the schedule itself is not automatically restored. To restore the schedule
from a backup file, specify that component as described in the
database will be different, due to the existence of the backup and restore tasks.
Therefore, the schedule itself is not automatically restored. To restore the schedule
from a backup file, specify that component as described in the
Running a ‘Restore system data from backup’
The automatic restore process is appropriate when setting up a High Availability
backup server to automatically get the state from the primary server. However, there
may be cases when you need to restore a backup on demand as described here:
backup server to automatically get the state from the primary server. However, there
may be cases when you need to restore a backup on demand as described here:
1. Open SV Director and click Management Dashboard.
2. Select Tools > Advanced > Restore system data from backup.
3. Select the desired components to restore and select the date of the backup file
to use for the restore.
4. Click Apply. The restore will run.