How to Migrate Repositories from CloudStorage to Local Storage

Use the following steps to migrate from CloudStorage to local storage only. If you want to migrate from CloudDR to local storage, see Migrate Repositories from CloudDR to Local Storage.

Complete these steps on each repository you want to migrate.

Step 1. Stop the Service

1. Open the ArchiveOne Admin console.
2. Right-click Policies, and then click View Status.
3. If the first phase is running, click Stop the current policies.
4. If the second phase is running, click Stop second phase.
5. Verify both phases display a status of Not running.
6. Click Close status window, and then close the ArchiveOne Admin console.
7. Open Microsoft Services console (services.msc).
8. Right-click ArchiveOne Data Manager Service, and then click Properties.
9. Select Disabled as the Startup type, click Stop, and then click OK.

The ArchiveOne Data Manager Service is now stopped and disabled. No archiving to any repository can take place, and the repository can now be migrated to local storage.

Step 2. Migrate to Local Storage

1. Create a local folder to store the repository archive data, for example, D:\ Repository_Name\Archive
   

   The ArchiveOne Service account requires Full Control NTFS permissions on this folder.

2. Within this directory create a subfolder named TempZipFiles, for example, D:\Repository_Name\Archive\TempZipFiles.

   1. If you are using Barracuda CloudStorage contact Support to get a copy of the repository .zip files.

   2. If you are using Amazon CloudStorage then use your preferred tool to access the Amazon S3 files.

3. Copy all the .zip files into the TempZipFiles directory, for example, D:\Repository_Name\Archive\TempZipFiles.

   Do not remove the files from Amazon until the entire process is complete and the data is successfully retrieved. 

    

4. Create a PowerShell script named CloudZipRename.ps1, and add the following content to the script:

   gci *.zip | foreach{ if($_.FullName.Length -ge 33){$start = $_.FullName.IndexOf("A1P")

   $newFilename = $_.FullName.SubString($start, $_.FullName.Length – $start)

   $newFilename

   ren $_.Fullname -NewName "$newFilename"

   }

   }

5. In PowerShell, change the directory to the repository TempZipFiles directory.

6. Run CloudZipRename.ps1  in the directory. The .zip files copied from cloud storage are renamed appropriately for a repository stored locally.
7. Confirm the current location of the repository’s index from the ArchiveOne Admin console:
   1. Expand Repositories, navigate to and right-click the repository you are migrating, and then click Properties.
   2. Click the Index tab, and note the Index Base Directory location, for example, D:\Repository_Name\Index.

Step 3. Update the Repository Configuration

1. Open the ArchiveOne Admin console.
2. Expand Repositories, navigate to and right-click the migrated repository, and then click Run Repository Configuration Wizard.
3. In the first page of the Wizard, click Next.
4. In the Storage Manager page, select None from the drop-down menu (or select another Storage Manager for your system), and click Next.
5. Do not make any changes in the Index Location page; click Next.
6. In the Archive Location page, browse to and select the Archive Base Directory to the new local folder path you created, for example, D:\Repository_Name\Archive\TempZipFiles.
7. Click Next.
8. Click Next again, and then click Finish to complete the Wizard.
9. Right-click the repository again, and click Properties.
10. Click the Temporary Data tab, and update the folder path to a suitable local folder location, for example, the repository Index folder, and then click OK.

The repository configuration is now complete. Once you complete the migration for each repository, you can restart the service.

Step 4. Restart the Service

1. Open Microsoft Services console (services.msc).
2. Right-click ArchiveOne Data Manager Service, and then click Properties.
3. Select Manual as the Startup type, click Start, and then click OK.

To confirm data migration was successful, run an archive search from the ArchiveOne admin console for all messages in any repositories you have migrated. On the search results, the Status column should show the messages as Available indicating that the archived data is accessible.