In-house archiving migration during the HEX project

S14 currently creates new archive in Archiving12
S19 currently creates new archive in Archiving05

There are 3 possible scenarios:

Scenario 1: Client on S05 migrating to S19 and is archived in archiving05.sherwebcloud.com

Once the cutover is completed, make sure to note the current archiving settings to be able to recreate the same at the destination (Static, Dynamic, etc) then deactivate Archiving in the S05 Control Panel
Activate Archiving in the S19 Control Panel
Update the password of the new archive mailbox (S19) and update the POP account settings in the organization archiver’s settings.
Then go to the System Dashboard and test the pumping for that organization to make sure the system is working fine.
Finally, make sure that organization is not ‘flagged for deletion’ (most likely happening in scenario 3 but it’s always better to be safe).
Add a note to the ticket saying that the archiving migration was done and close it.

Scenario 2: Client on S12 migrating to S14 and is archived in archiving12.sherwebcloud.com

Once the cutover is completed, make sure to note the current archiving settings to be able to recreate the same at the destination (Static, Dynamic, etc) then deactivate Archiving in S12 Control Panel
Activate Archiving in S14 Control Panel
Update the password of the new archive mailbox (S14) and update the POP account settings in the organization archiver’s settings.
Then go to the System Dashboard and test the pumping for that organization to make sure the system is working fine.
Finally, make sure that organization is not ‘flagged for deletion’ (most likely happening in scenario 3 but it’s always better to be safe).
Add a note to the ticket saying that the archiving migration was done and close it.

Scenario 3: Client is migrating to S19 and archiving of source is not Archiving05 or client is migrating to S14 and archiving of source is not Archiving12.

Once the cutover is completed, make sure to note the current archiving settings to be able to recreate the same at the destination (Static, Dynamic, etc) then deactivate Archiving in source Control Panel

Next, activate the archiving in destination Control Panel.

The following steps will describe how to repoint the current organization to its right archiver.

In the XPS Database of ControlPanel3, run the script and take note of the ID of the destination store.
1. From the destination TS, open 'Microsoft SQL Server Management Studio'
2. Connect to one of these servers:
  1. S14 'S14VSQL1111\S14VSQL1111'
  2. S19 'S19-sqi-11001'
3. Run the query below to get the ID:
```
Use XPSSELECT Id, Name
FROM Xps..Stores
WHERE ServiceID = 9
```
  We want to take the ID associated with the following archiving platforms:
  
  Archiving01 = S05VARCBE1112
  Archiving05 = S05-ARCFE
  Archiving12 = s12-arcfe
In the XPS Database of ControlPanel3, run the script found below at point #3
1. From the TS, open 'Microsoft SQL Server Management Studio'
2. Connect on the right server depending on the destination platform
  1. S05 'S05-VSQL0101'
  2. S12 'S12VSQL1111\S12VSQL1111'
  3. S14 'S14VSQL1111\S14VSQL1111'
  4. S19 'S19-sqi-11001'
Modify and run the script as follows:
1. StoreID, i.e. 589 pour S05-ARCFE
2. EntityID, available in the Control Panel under organization Hosting administrator information - GUID i.e. 3f3acfa0-65d5-123f-a9c6-2ea78b12346e
```
UPDATE Xps..EntityStoresSizeUsed
SET StoreID = Id you got from the previous script run
WHERE EntityID = 'Organisation GUID’
AND StoreID IN (
SELECT Id
FROM Xps..Stores
WHERE ServiceID = 9
)
```

When this part has been completed, the organization should point to the right archiver.

Update the password of the new archive mailbox (S14 or S19 depending on scenario) and update the POP account settings in the organization archiver’s settings.

Then go to the System Dashboard and test the pumping for that organization to make sure the system is working fine.
Finally, make sure that organization is not ‘Flagged for deletion’
Add a note to the ticket saying the archiving migration was done and close it.

Organization deletion WiKi procedure for target platform that won't be used.

https://wiki.sherweb.com/display/SWAT/Supprimer+une+organisation

Helpdesk