Installing and Configuring Arcserve Backup UNIX and Linux Data Mover › Migrate Media Management Option Data from a Previous Release to the Arcserve Backup Database

Migrate Media Management Option Data from a Previous Release to the Arcserve Backup Database

Arcserve Backup lets you migrate Media Management Option (MMO) data from BrightStor ARCserve Backup r11.5 to this release. This capability is beneficial under the following scenarios:

• You have a high volume of tapes stored in off-site vaults.
• You rely on running vault cycles to generate shipping and receiving reports.
• You want to check in your tapes to the libraries in your current Arcserve Backup for Windows implementation.
• You want to or plan to upgrade the UNIX or Linux server to a Arcserve Backup data mover server.

Arcserve Backup lets you migrate the MMO data from BrightStor ARCserve Backup r11.5 installations (includes the general availability release and all of the latest service packs) to this release.

If your BrightStor ARCserve Backup r11.5 implementation consists of a SAN primary and SAN distributed servers, you can migrate the MMO data from the SAN primary server and the SAN distributed servers. However, you must migrate the MMO data from the SAN primary server before you migrate the MMO data from the SAN distributed servers.

Arcserve Backup lets you migrate the following data:

• Backup session data
• Tape data
• Media pool data
• Vault data
• Miscellaneous MMO data

Important! Do not uninstall BrightStor ARCserve Backup r11.5 from the target UNIX or Linux computer before you complete this task.

To migrate Media Management Option data from a previous release to the Arcserve Backup database

1. Ensure that all BrightStor ARCserve Backup services are running on the UNIX or Linux server.

   Ensure that all staging migration jobs on the UNIX or Linux server are complete. This task does not let you migrate staging information from your previous implementation.

2. (Optional) As a best practice, you should perform a full backup of the UNIX or Linux server. This lets you create a recovery point that you can revert to in the event you need to revert back to your BrightStor ARCserve Backup r11.5 implementation.
3. On the UNIX or Linux server, execute IngresDBDump.sh.

   Note: You must specify the credentials for the root account to execute IngresDBDump.sh. However, IngresDBDump does not require parameters.

   IngresDBDump.sh dumps the data into the following directory:

   $BAB_HOME/dbase/ingres/tmp
   

   Note: As a best practice, create a backup of the dumped data by copying the data to an alternate directory on the UNIX or Linux server.

4. Identify the directories that contain the data for the file system devices that you will migrate. You can identify the directories by examining the following configuration file:

   $BAB_HOME/config/camediad.cfg
   

5. Uninstall BrightStor ARCserve Backup r11.5 from the UNIX or Linux server.
6. Install UNIX and Linux Data Mover on the server.

   Note: You must register the server with the Arcserve Backup primary server while you install UNIX and Linux Data Mover.

7. Copy the dumped data from the data mover server to the Arcserve Backup primary server.
8. Do one of the following:
   • To migrate data for all tapes, execute the following command on the primary server:

     MergeIngres2SQL.exe -dir <path to the dumped data>
     

   • To migrate data for only the detected tapes, do the following:
     1. Create file system devices on the data mover server using the paths identified in the camediad.cfg configuration file.
     2. Execute the following command on the primary server:

        MergeIngres2SQL.exe -dir <path to the dumped data> -migrate4recognizedmedias
        

9. Open the Restore Manager on the primary server.

   Click the Source tab and select Restore by Session (or Restore by Tree) from the drop-down list.

   The migrated backup sessions appear and are listed under the corresponding media.

10. Click a migrated session.

    Arcserve Backup prompts you to merge the specified session.

    Click Yes.

    Repeat this step for all migrated sessions.