Cisco Cisco StadiumVision Mobile Streamer Maintenance Manual
© 2011 Cisco Systems, Inc. All rights reserved.
Page 5 of 21
Backing Up the Primary Server
There are several components to SV Director that need to be backed up. The
backup process backs up the:
backup process backs up the:
-
SV Director database
-
System configuration files
-
Content repository
-
Ad Insertion Manager database
Each backup operation results in a tar file that contains separate compressed files
for each of the above. When complete, the backup file will be located in
/var/sv/BACKUP on the primary and /var/sv/RESTORE on the secondary server if
there is a secondary server and the steps for
for each of the above. When complete, the backup file will be located in
/var/sv/BACKUP on the primary and /var/sv/RESTORE on the secondary server if
there is a secondary server and the steps for
following format:
sv-VER-YYYYMMDDHHMMSSTZOFFSET.tar
where
:
•
Ver is the StadiumVision version the backup was created from.
•
YYYYMMDDHHMISS is the time of the backup in year, month, day, hour,
minute, second, of backup.
•
TZOFFSET is the time zone offset of the server in relation to GMT. An example
would be a file called “sv-2.2.55-20110202121212-0800.tar”.
To list the contents of a backup file, replace the “sv-2.2.55-20110202121212-
0800.tar” with the backup file you would like to list and run the following:
0800.tar” with the backup file you would like to list and run the following:
tar tvf sv-2.2.55-20110202121212-0800.tar
StadiumVision Director does not automatically delete backups from the
/var/sv/BACKUP or /var/sv/RESTORE directory. Disk space should be monitored
accordingly and un-needed backup files should be erased accordingly. As an
option, you can add a daily cron job to remove old files from the /var/sv/BACKUP or
/var/sv/RESTORE directories. For example, to remove all files from the backup
directory that are more than 30 days old run a command like:
/var/sv/BACKUP or /var/sv/RESTORE directory. Disk space should be monitored
accordingly and un-needed backup files should be erased accordingly. As an
option, you can add a daily cron job to remove old files from the /var/sv/BACKUP or
/var/sv/RESTORE directories. For example, to remove all files from the backup
directory that are more than 30 days old run a command like:
/usr/bin/find /var/sv/BACKUP -mtime +30 -exec rm {} \;
Be sure to note that when running or scheduling a backup, it cannot be run while an
event script is running. When the backup starts, it first checks to see if an event
script is running. If a running script is detected it aborts the backup. This situation
can be identified by looking for the following message in the “sv_dev_debug.log”:
event script is running. When the backup starts, it first checks to see if an event
script is running. If a running script is detected it aborts the backup. This situation
can be identified by looking for the following message in the “sv_dev_debug.log”:
"Backup is aborting, as a script is currently running"