Database Backup and Recovery

Backup

Database backups are for restoring your Vulnerability ProtectionDeep Security system in the event of a catastrophic failure, or for transferring your Vulnerability ProtectionDeep Security Manager to another computer.

The Vulnerability ProtectionDeep Security Manager cannot initiate a backup of an Oracle database. To backup your Oracle database consult your Oracle documentation.
Internal Database or Microsoft SQL Server Database
Microsoft SQL Server Database

Database backups can be carried out using the Scheduled Tasks interface. Go to the Administration > Scheduled Tasks page. Click New and select "New Scheduled Task" to display the New Scheduled Task wizard. Give a name to this task and choose "Backup" from the drop-down list. The next page will prompt you for how often you want this task carried out and when. To carry out a one-time-only backup, choose "Once Only" and enter a time (5 minutes from now, for example). The next page will prompt you for a location to store the backup files. Click through to the end of the wizard to finish. A complete backup shouldn't take more than a minute or so to complete.

A "date-named" folder will be created in the backup location you specified. If you are using the Deep Security Manager's embedded Apache Derby database (which is intended for test purposes), a folder structure will be created beneath it that maps to the folders in the Deep Security Manager's install directory. To restore this database, shut down the "Trend Micro Deep Security Manager" service (using the Services Microsoft Management Console), copy the backup folders into the corresponding folders of the install directory, and restart Deep Security Manager.

If you are using a SQL Server database, a SQL Server database backup file named [timestamp].dsmbackup will be written to the backup folder specified in the Scheduled Task. (For instructions on how to restore a SQL Server database refer to your SQL Server documentation.)

If you are using a Microsoft SQL Server database, a database backup file named [timestamp].dsmbackup will be written to the backup folder specified in the Scheduled Task. (For instructions on how to restore a database, refer to your SQL Server or SQL Server Express documentation.)

Restore
The Vulnerability ProtectionDeep Security Manager cannot backup or restore an Oracle database. To backup or restore your Oracle database consult your Oracle documentation.
Database Only
  1. Stop the Vulnerability ProtectionDeep Security Manager service
  2. Restore the database (Must be a database from the same version number of the Manager)
  3. Start the Vulnerability ProtectionDeep Security Manager service
  4. Verify contents restored
  5. Update all of the computers to ensure they have the proper configuration
Both Vulnerability ProtectionDeep Security Manager and Database
  1. Remove any remnants of the lost/corrupted Manager and database
  2. Install a fresh Vulnerability ProtectionDeep Security Manager using a fresh/empty database
  3. Stop the Vulnerability ProtectionDeep Security Manager service
  4. Restore the database over the freshly installed one, must be the same database name (Must be a database from the same version number of the Manager)
  5. Start the Vulnerability ProtectionDeep Security Manager service
  6. Verify contents restored
  7. Update all of the computers to ensure they have the proper configuration
Export

You can export various Vulnerability ProtectionDeep Security objects in XML or CSV format:

When exporting to CSV, only displayed column data is included. (Use the Columns... tool to change which data is displayed.) Grouping is ignored so the data may not be in same order as on the screen.

Importing

To import each of the individual objects into Vulnerability ProtectionDeep Security, choose "Import From File" from the drop-down list next to the New button in the toolbar of the objects' respective pages.