This article applies to:

• MailMarshal SEG 8.X
  • See note about MailMarshal 10.0 and above

Question:

• How can I change the location where automatic configuration backups are stored? 
• I want my automatic backups to be stored on a different physical disk from the SEG installation.

Procedure:

1. On the MailMarshal Array Manager server, create a folder in the desired location. For example: D:\CustomAutoBackup
   • CAUTION: Do not use an existing location that contains files. Do not store any other files in this location. XML files in this location will be deleted on a schedule.
2. Edit the Registry. In 8.X navigate to
   HKEY_LOCAL_MACHINE\SOFTWARE\Trustwave\Secure Email Gateway\Manager\ConfigBackup\
3. For full details of the location for each product version, see article Q10832.
4. Create a Reg_SZ (string) value named BackupLocation
5. Set the value to the absolute folder path (including drive letter) of the folder you created.
   • For the avoidance of doubt, UNC or mapped drive locations are not supported. Any issues encountered with such locations are at customer's risk and LevelBlue will not provide support assistance. Drives on SAN are supported.

To revert to the default location, delete the above Registry value.

Notes:

• On upgrade from 8.X to 10.X this setting is preserved in the new configuration format. It is not currently possible to add or modify the setting in MailMarshal 10.0 or above.
• This setting configures a location for the backups. It does not move the ConfigurationBackup subfolder that is created by the installation. Be sure that the folder name you enter in the Registry points to a valid folder. If you specify an invalid location, backups will fail.
• If you use this feature to set a location, purging of prior backups will only affect this location (files will not be purged from the ConfigurationBackup subfolder).

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. LevelBlue cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Make sure that you back up your Registry prior to making any changes.