Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 – Backing up a Cisco VCS
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X6)
Page 49 of 76
Appendix 1 – Backing up a Cisco VCS
Backing up a pre X3.0 VCS
To save the configuration of a Cisco VCS running a version of code prior to X3.0:
1. Use SSH, Telnet or a serial link to log into the Cisco VCS CLI as an admin user.
2. Type:
xconfiguration
3. Copy the results to a text file and save it.
To save the VCS FindMe data and certificates:
1. Log into the Cisco VCS CLI as root and save:
a. persistent/policy/policy.xml
b. persistent/oti/*.*
c.
persistent/certs/*.*
Backing up an X3.0 or later Cisco VCS
1. On the Cisco VCS web UI go to Maintenance > Backup and restore.
2. Click Create System Backup File and save the file.
3. If Cisco VCS is X5 or later:
a. Click Create TMS Agent backup file and save the file (this backs up FindMe entries that are
in X5 FindMe database format).
Note:
If the TMS Agent backup is restored (uploaded) to Cisco VCS then:
from a root login run “tmsagent_reindex_database” to ensure the uploaded data is linked into the
database correctly.
from a root login run “tmsagent_reindex_database” to ensure the uploaded data is linked into the
database correctly.
A TMS Agent backup contains the whole of the Cisco TMS’s provisioning and FindMe database
(for all clusters and non-clustered Cisco VCSs with which Cisco TMS is replicating). It is saved
for emergency use only – if restored to a cluster it will only get overwritten by the Cisco TMS
data. It can be restored to a non-clustered Cisco VCS that is not replicating with Cisco TMS.
(for all clusters and non-clustered Cisco VCSs with which Cisco TMS is replicating). It is saved
for emergency use only – if restored to a cluster it will only get overwritten by the Cisco TMS
data. It can be restored to a non-clustered Cisco VCS that is not replicating with Cisco TMS.