Configuring the Backup Exec Migrator to communicate with Enterprise Vault

Use the following steps to configure the Backup Exec Migrator to communicate with Enteprise Vault.

See Configuring the Backup Exec Migrator.

To configure the Backup Exc Migrator to communicate with Enterprise Vault

  1. At the Enterprise Vault server, navigate to a vault store partition from which to migrate data.

  2. Right-click the vault store partition, and then click Properties.

  3. On the Migration tab, check Migrate files.

  4. In Remove collection files from primary storage, set the time period for this option to something longer than zero days.

    Do not set it to zero days. Setting the time period to zero days causes Enterprise Vault to immediately delete the migrated data from the partition. More importantly, it causes the Backup Exec Migrator to create separate migration jobs for each partition folder being migrated during a migration period. If separate jobs are created, the resulting overhead that is required to run the jobs results in degraded migration and retrieval performance.

    See Configuring the Backup Exec Migrator.

  5. Set other migration options as appropriate.

    See Vault store partition properties – Migration options.

  6. On the Advanced tab, ensure that Symantec Backup Exec appears in the List setting from field.

  7. In the window below the List setting from field, select Backup Exec media server.

  8. Click Modify.

  9. Type the name or the IP address of the destination Backup Exec server.

  10. Click OK.

  11. Select Backup Exec DBA-initiated template.

  12. Click Modify.

  13. Enter the name of an existing template that uses the Enterprise Vault server Vault Service account credentials.

    The template that you select must be configured to use the Enterprise Vault server Vault Service account. The template you use must also match the template name that you used when you configured the Backup Exec Migrator to work with a media server.

    See Configuring the Backup Exec Migrator to work with a Backup Exec media server.

  14. Click OK.

  15. Ensure that the name of the template that contains the Enterprise Vault server Vault Service account credentials appears in the Setting pane.

    See Configuring the Backup Exec Migrator to work with a Backup Exec media server.

  16. To test the communications between the Enterprise Vault server and the Backup Exec media server, click Test Configuration.

  17. If the test fails, ensure that you used the correct credentials for the Vault Service account , and then click Test Configuration again.

  18. Click OK after the test successfully completes.

  19. Click OK.

Vault store partition properties – Migration options

Select the Enterprise Vault migration property options that you want to use.

Table: Vault store partition properties – Migration options

Item

Description

Migrate files

Lets you migrate archived Enterprise Vault data to a Backup Exec storage device.

Migration can help reduce storage costs by moving collection files to tertiary storage devices. However, retrieval times can increase.

See your Enterprise Vault documentation.

Migrator

Indicates the name of the migration application.

Symantec Backup Exec must appear in this field.

Migrate files older than

Indicates the amount of time that must elapse since files were last modified before they are eligible for migration.

See your Enterprise Vault documentation.

Remove collection files from pri
mary storage

Indicates the age at which migrated collection files are removed from the primary storage location.

Files that have been migrated to Backup Exec storage media can remain in their primary location for the period of time you specify.

Note:

Symantec recommends that you set the time period for this option to something longer than zero days, with a longer time period being best. Do not set it to zero days. Setting the time period to zero days causes the Backup Exec Migrator to create separate migration jobs in a migration period for each partition being migrated. If separate jobs are created, the resulting overhead that is required to run the jobs results in degraded migration and retrieval performance.

See Configuring the Backup Exec Migrator.

Configuring the Backup Exec Migrator to communicate with Enterprise Vault