Description

This article describes the steps to change the configured bucket of an existing Amazon Simple Storage Service (S3) partition.

Steps

Changing the configured AWS S3 bucket of an existing Amazon Simple Storage Service (S3) partition consists of the following steps:

Step 1:

Ensure that you have created the AWS S3 source and destination buckets as per your business requirements. You must confirm that the new AWS S3 bucket is created with the existing settings and policy as existing AWS S3 bucket attached to the Amazon Simple Storage Service (S3) partition.

Step 2:

Configure replication on the AWS S3 source bucket with a new or existing IAM role. Ensure that all the files are replicated to the destination bucket before using the destination bucket on the Amazon Simple Storage Service (S3) partition.

Refer to the “How to enable replication of delete marker from AWS S3 source bucket to destination bucket” tech note.

Step 3:

Confirm that all the archived items have been backed up.

1. Open the SQL Server Management Studio.
2. Run the following query:
   USE [Vault Store Database Name]
SELECT COUNT(*)
FROM WatchFile
3. If the count is 0, perform step 4. If the count is greater than 0, there are items left waiting either backup or indexing.

Step 4:

Set the vault store backup mode and then stop services on the Enterprise Vault server.

1. To set the backup mode:
   1. Open the Administration Console.
   2. In the left pane of the Administration Console, expand the Vault Store Group container.
   3. Right-click the vault store group whose vault stores need to be placed in the backup mode, and click Set State > Set Backup Mode on all Vault Store.
      For details, see Enterprise Vault backup mode.
2. Stop all Enterprise Vault services.

Step 5:

Confirm that all the archived files from the existing AWS S3 bucket are moved to the newly created AWS S3 bucket. Refer to the AWS S3 documentation for detailed instructions.

Step 6:

Update partition with the new bucket in the SQL Server.

1. Open SQL Server Management Studio.
2. Expand Databases.
3. Select EnterpriseVaultDirectory.
4. Create a new SQL query.
5. Copy-paste the following SQL query:

   USE EnterpriseVaultDirectory

   DECLARE @PartitionName AS VARCHAR(200)

   DECLARE @NewBucket    AS VARCHAR(200)

   SET @PartitionName = 'Legal_HR_Data'

   SET @NewBucket = 'destination-bucket101'

    

   SELECT settingValueText AS 'Previous Bucket' FROM ExtendedSetting

   WHERE RootId = (SELECT PartitionEntryId FROM PartitionEntry WHERE PartitionName = @PartitionName)

     AND settingTypeId = 2725

    

   UPDATE ExtendedSetting SET settingValueText = @NewBucket

   WHERE RootId = (SELECT PartitionEntryId FROM PartitionEntry WHERE PartitionName = @PartitionName)

     AND settingTypeId = 2725

    

   SELECT settingValueText AS 'New Bucket' FROM ExtendedSetting

   WHERE RootId = (SELECT PartitionEntryId FROM PartitionEntry WHERE PartitionName = @PartitionName)

     AND settingTypeId = 2725

6. Replace @PartitionName and @NewBucket variables in the above script.
7. Execute the above SQL script.
8. Verify that the bucket is changed for that partition.
9. Repeat these steps for each partition that is being updated.

Step 7:

Start Enterprise Vault services, confirm that the archived items can be opened, and clear the backup mode on the Enterprise Vault Server.

1. Start all Enterprise Vault services.
2. Confirm that the archived items can be opened.
3. Clear the backup mode.
4. In the left pane of the Administration Console, expand the Vault Store Group container.
5. Right-click the vault store group whose vault stores need to have the backup mode cleared, and then click Set State > Clear Backup Mode on all Vault Stores.

For more information about Enterprise Vault backup mode, see How to verify backup mode for Enterprise Vault (EV) event log using Event ID messages.

Important Notes

• Change the replication from “replicated on the cloud storage” to “exist on the cloud storage”, as AWS does not support reverse replication. Else, users will get the error related with Storage File Watch and Storage Management under Window event viewer.
• It will stop updating the information related to secured and unsecured items on Replication tab Details pop-up.
• Your newly archived items to the destination bucket will not get replicated to the source bucket.
• On the destination bucket, AWS admin can only configure the storage classes supported by Enterprise Vault.