TMS makes that backup very easy. That's the best way to go. You still don't schedule a backup in TMS but it makes it easy to make a config backup of all your devices at once from a single interface. Very handy. Typically TelePresence equipment configurations (especially infrastructure) don't typically change very often. Not as much as a server, for example, so it's usually safe to backup the systems each time you've made a configuration change. And, as we all know, those are not always "scheduled" but are in response to an event or directive. So that is how TMS is structured.
If you are not using TMS you could theoretically use either an SCP client to log on to the VCS root account and make a copy of the config.db file. But you would have to allow root account access to the server logging on, and that might be a bit more risk than it's worth. You could probably also configure a (safer) SSH log on and text capture running the xconfig command in the CLI. But by the time you set up all that automated programming you might be just as well to do a manual backup.
Remember you don't want to backup the VCS if something has changed that you don't want to keep! Unlike a server there isn't dynamic data stored in the actual configuration database on the system. It's just settings information.
Hope that helps.
Eric
CCSI, Compass Business Solutions (TelePresence)
