# Migrating V1 Compliance Archiver Data to V2 Exchange Client Using Case Manager

An admin user or a master user can migrate the Exchange Journal Mailbox data backed up and archived using the V1 Exchange Compliance Archiver Agent, to the V2 Exchange Journal Mailbox client or the SMTP ContentStore Journal client using Case Manager.

After the migration is complete, the V1 Exchange Compliance Archiver data can be accessed along with content of the V2 Exchange client on the Compliance Search page. Compliance officers can browse and search the migrated Exchange Journal Mailbox data that was content indexed using the V1 Search Engine.

Important

- After the migration process is complete,

  - Backups of the V1 Exchange Compliance Archiver data must not be deleted.

  - Restores can be performed only if data is available on the backup source.

  - Remove permissions to the V1 Compliance Archiver client for the user with the Case Manager role.

- You must remove the backup schedule from the server plan associated with the mailbox.

## Before You Begin

Configure the EnableV1JournalContentIdFormat additional setting and set the value to true. For more information, see Adding a CommCell Setting.

## Procedure

1. Create a user with Case Manager role. For more information, see Creating a User.

2. Configure permissions on the Exchange client which needs to be migrated with new Case Manager user. For more information, see Set Server Permissions for Case Manager.

3. Assign Plan Subscription Role to the Case Manager user on the data classification plan and on the backup plan. For more information, see Set Plan Permissions for Case Manager.

4. Disable the Index Copy schedule policy. For more information, see Disabling a Schedule Policy.

5. Login to the Command Center application as a compliance officer or as a user with Case Manager role.

6. Create a case of type ReviewSet with Data type as Exchange journaling. For more information, see Creating a Case for Email Data.

   Note

   Commvault recommends that you create multiple case definitions to migrate data in batches for better performance. For more information on case definitions, see Adding a Definition to a Case for Email Data in Case Manager.

7. In the case details page, copy the case id from the URL.

   The case id will be used as a value for the <clientId> parameter in subsequent steps of this migration process.

8. Login to the CommServe server.

9. Download the CMArchiverMigration_PreProcess.sqle QScript from the Commvault Store.

10. From the command prompt, run the following command on the CommServe server.

        qoperation execscript -sn CMArchiverMigration_PreProcess -si $[clientId]

    <clientId> is the case id that you copied when the case is created.

    The Qscript Execution Succeeded! message appears.

11. In the Command Center application, navigate to the case details page and click Submit collection job. For more information, see Collecting Data for a Case On Demand in Case Manager.

12. Wait until the Case Manager Index copy job and the Content Indexing job completes.

    The Case Manager user will be able to view the case and the number of items imported under the Statistics section of the Comply > eDiscovery & Compliance > Case manager page.

13. On the CommServe server, download the CMArchiverMigration_PostProcess.sqle QScript from the Commvault Store.

14. From the command prompt, run the following command.

        qoperation execscript -sn CMArchiverMigration_PostProcess -si $[client ID of the case] -si $[client ID of the access node]

    <clientId> is the case id that you copied when the case is created.

    The QScript Execution Succeeded! message appears.

    /// note | Important To apply retention to migrated data, you must supply a valid `case client ID` and `access node client ID` when running the script. The access node can be any server with the Exchange or Office 365 package installed.

    - To find the `case client ID`, go to Data Insights > Case Manager > Review Set Name. The ID appears in the URL after `appDetails`.

    - To find the `access node client ID`, go to Manage > Infrastructure > Servers > Server Name. The ID appears in the URL after `clientDetails`.

    You can also use the following tools to find the client ID for any Commvault server:

    - Commvault PowerShell module.

    - REST API. ///

    Once the QScript has been executed successfully, the case will no longer be visible in the Comply > eDiscovery & Compliance > Case manager page as it is now converted to an Exchange Journal client. You can view and browse the Exchange Journal client from Protect > Exchange to see the number of items imported.

15. Create an Exchange Journal plan with desired retention. For more information, see Creating an Exchange Journal Mailbox Plan.

16. Configure the Exchange servers and the Exchange connection setting for the migrated journal client. For more information, see Creating an Exchange Journal Mailbox Plan.

17. Add the migrated journal mailbox with the corresponding Exchange Journal plan. Retention that is set in the plan selected will be applied by the background process which runs every 24 hours.

18. Search engine data is successfully migrated to the Index Server to which the Case Manager Data Classification plan is pointing to. Compliance officers can search migrated data in the Compliance Search page of the Command Center application.

    The new V2 Exchange client is created with same name as the ReviewSet case. To verify the client, navigate to Protect > Exchange.

    Important

    To search migrated data, the Admin user must give Case manager user capabilities to the compliance officers for the imported V2 Journal Mailbox client.

×

Loading...