What Geoff suggests is true for backing up the HDS's historical data.
One would never (ever) need to back up the actual awdb.
It is pointless to back up the awdb, as you would never have reason to restore said backup.
The Admin Workstation Database (awdb) contains configuration, script, and real-time data. The config & script data is modified whenever there is a config or script insert/update/delete. For most customers, this happens many dozens of times daily. The real-time data is refreshed every ten seconds.
If something happens to the AWDB whereby it became corrupted or something, you'd just drop it in SQL, then re-build it by re-running \icm\bin\icmsetup.exe. When the distributor service is restarted, the updateaw process pulls the current config & script data from the logger, and the real-time feed will be established from the callrouter to get current realtime data. It would therefore be un-necessary to have a backup copy of the awdb.
If you simply want to save off a snapshot of the configuration data (i.e. to set up a lab, or just to have a known good copy of your data), you'd use ICMDBA to export the awdb, or better-yet, the logger's copy of the configuration. If I was a customer, I'd consider setting up a macro to do this a few times every day.
-Steve
