• Raw diagnostic and report logs.  Optionally report data in SQL is saved.
• If you’ve changed your logging location for diagnostics and/or data files, this will be forced back to the default location under the install directory.  You will need to make this change again if you wish this directory to be moved again.
• Any mappings made with the GrantUnityAccess tool.  Any non subscriber accounts you had configured to have SA access to the Unity server will need to be remapped using GrantUnityAccess after the restore is complete.
• If you’ve moved the UnityMTA directory share, this will be put back to the default folder under the installation directory.  You will need to make this change again if desired.
• Any customizations made to the ENU (Error Notification Utility) will not be preserved.  If, however, you are using the new Event Monitoring Service (EMS) which replaces the old ENU tool, this information is restored properly.
• If you’ve setup the use of a custom codec (i.e. G729a) this information is not saved, you will need to configure that again using the SetRecordFormat tool.
• System prompts and language information - no prompts are backed up and all languages you wish to have on the new system needs to be installed there during the installation of that server.  If you restore a system that references a language that you did not install on your new server, you will get errors when running Unity.
• Most customizations made via the AST tool - in particular settings such as "Disable AD accounts created by Unity".  You will want to review your AST customizations on the new installation prior to restoring.

 

NOTE: While switch configuration information is saved, it is not restored onto the system.  The data is in the original backed up files in case TAC needs to get to it.  Since switch configuration can and does change between back up and restore (i.e. when moving systems) the local switch configuration needs to be configured and will not be restored.