Difference between revisions of "MailStore Server to MailStore SPE Migration"

[unchecked revision][unchecked revision]
(Created page with "This guide shows, how to migrate a MailStore Server installation into the MailStore SPE. This can be useful, if the customer has used MailStore Server before, but now he want...")
 
Line 3: Line 3:
 
This can be useful, if the customer has used MailStore Server before, but now he wants the archive to be stored in a service provider's datacenter.  
 
This can be useful, if the customer has used MailStore Server before, but now he wants the archive to be stored in a service provider's datacenter.  
  
−
Also, when an on-premise mailserver or on-premise e-mail files, like PSTs, should be archive by an SPE instance, it might be a good decision to do the [http://en.help.mailstore.com/Archiving_Email intial archiving with MailStore Server] in the customer's infrastructure, and then migrating the resulting MailStore databases into the SPE.
+
Also, when an on-premise mailserver or on-premise e-mail files, like PSTs, should be archive by an SPE instance, it might be a good decision to do the [http://en.help.mailstore.com/Archiving_Email intial archiving with MailStore Server] in the customer's infrastructure, and then migrating the resulting MailStore databases into the SPE. Usually a [https://my.mailstore.com/TrialLicense/RequestForm?lang=en MailStore Server Trial license] will do for that purpose.
  
 
Since the MailStore databases usually are considerable smaller then the uncrompressed e-mail volume, the amount of data to be transferred initially is significantly less.
 
Since the MailStore databases usually are considerable smaller then the uncrompressed e-mail volume, the amount of data to be transferred initially is significantly less.
Line 9: Line 9:
 
The two product use a slightly different format of the ''MasterDatabase'', which holds the configuration items, therefore it is not possible just to move the entire ''MailArchive'' directory of MailStore Server into the SPE.
 
The two product use a slightly different format of the ''MasterDatabase'', which holds the configuration items, therefore it is not possible just to move the entire ''MailArchive'' directory of MailStore Server into the SPE.
  
−
However, it is possible to move all the ''archive stores''.
+
However, it is possible to transfer all the ''archive stores''.
 +
 
 +
* First you have to [[Instance_Management_-_General_Administration#Creating_Instances| create an instance]]. The instance does not have to be started yet.
 +
* Stop all archiving profiles in MailStore Server, either by setting the execution mode to ''manual'' or by disabling all scheduled tasks.
 +
* [http://en.help.mailstore.com/MailStore_Server_Service_Configuration Stop] the MailStore Server service.
 +
* Copy the ''archive stores'' directories from MailStore Server into the instance's ''Data' directory. You do not need to transfer the ''MailStoreMaster.fdb'' and ''MailStore.xml''. Make sure, there is no remaining ''.lock'' file in of the ''archive store'' directories. If there is any, the service is not stopped yet completely.
 +
* Start the instance.
 +
* [Instance_Management_-_Instance_Administration#Attach_Existing_Archive_Store Attach] the transferred ''archive stores'' to the newly created instance.
 +
*: '''Hint:''' If there are lots of ''archive stores'' to be attached, you can use a Python script to attach them automatically. More about this [[Migrate_from_MailStore_Server_to_SPE#Script|here]]
  
−
* First you have to [[Instance_Management_-_General_Administration#Creating_Instances| create an instance]].
 
−
* Click on ''General'' > ''Instances''.
 
−
* Select the instance to move.
 
−
* Stop the instance.
 
−
* Open the ''Instance Configuration''.
 
 
[[File:Ms_spe_move_instance_01.png|center]]
 
[[File:Ms_spe_move_instance_01.png|center]]
−
* Move the ''Base Directory'' of the Instance with your preferred file explorer to the new location. It is not sufficient just to change the ''Base Directory'' in the ''Instance Configuration''. This will not move the instance automatically. You are able to move the ''Base Directory'' to a different ''Instance Host'' or to a storage, that is accessible from a different ''Instance Host'' if you want that instance being run on a different ''Instance Host''.
+
[[File:Ms_spe_move_instance_04.png|600px|center]]
 +
 
 
*: '''Hint:''' If you need a minimal downtime of the instance, you could stop all archiving processes, create a backup of the instance with VSS, and store the backup in the new location. Then you just have to change the path instead of waiting for the transfer process.
 
*: '''Hint:''' If you need a minimal downtime of the instance, you could stop all archiving processes, create a backup of the instance with VSS, and store the backup in the new location. Then you just have to change the path instead of waiting for the transfer process.
−
* Change the ''Base Directory'' in the ''Instance Configuration'' if you just have changed the location on the same ''Instance Host''.
+
 
−
[[File:Ms_spe_move_instance_02.png|center]]
+
 
−
* If you want the instance being run on a different ''Instance Host'', change the ''Instance Host'' and the ''Base Directory'', if it has changed.
+
= Script =
−
[[File:Ms_spe_move_instance_03.png|center]]
+
 
−
* Close the ''Instance Configuration''.
+
Here comes the scripting part, yeah.
−
* Start the instance.
 
−
* Doubleclick on the instance and navigate to the ''Archive Stores'' tab.
 
−
* Verify that all stores are loaded correctly.
 
−
[[File:Ms_spe_move_instance_04.png|600px|center]]
 
−
* If an archive store is in an error state, because the path could not be found, follow these steps:
 
−
** Remember the current ''Requested State'' of the archive store.
 
−
** Set the ''Requested State'' to ''disabled''.
 
−
** Select the ''Set Path'' command of the archive store.
 
−
** Change the path to the new path. You either can enter the full absolute path, or you can enter a relative path from the instance's ''Data'' directory, by appending a ''~'' in front of the archive store directory.
 
−
** Set the ''Requested State'' of the store back to the previous state.
 
−
[[File:Ms_spe_move_instance_05.png|600px|center]]
 
−
* Restart your archiving profiles if you have paused them.
 

Revision as of 15:05, 14 November 2014

This guide shows, how to migrate a MailStore Server installation into the MailStore SPE.

This can be useful, if the customer has used MailStore Server before, but now he wants the archive to be stored in a service provider's datacenter.

Also, when an on-premise mailserver or on-premise e-mail files, like PSTs, should be archive by an SPE instance, it might be a good decision to do the intial archiving with MailStore Server in the customer's infrastructure, and then migrating the resulting MailStore databases into the SPE. Usually a MailStore Server Trial license will do for that purpose.

Since the MailStore databases usually are considerable smaller then the uncrompressed e-mail volume, the amount of data to be transferred initially is significantly less.

The two product use a slightly different format of the MasterDatabase, which holds the configuration items, therefore it is not possible just to move the entire MailArchive directory of MailStore Server into the SPE.

However, it is possible to transfer all the archive stores.

  • First you have to create an instance. The instance does not have to be started yet.
  • Stop all archiving profiles in MailStore Server, either by setting the execution mode to manual or by disabling all scheduled tasks.
  • Stop the MailStore Server service.
  • Copy the archive stores directories from MailStore Server into the instance's Data' directory. You do not need to transfer the MailStoreMaster.fdb and MailStore.xml. Make sure, there is no remaining .lock file in of the archive store directories. If there is any, the service is not stopped yet completely.
  • Start the instance.
  • [Instance_Management_-_Instance_Administration#Attach_Existing_Archive_Store Attach] the transferred archive stores to the newly created instance.
    Hint: If there are lots of archive stores to be attached, you can use a Python script to attach them automatically. More about this here
Ms spe move instance 01.png
Ms spe move instance 04.png
  • Hint: If you need a minimal downtime of the instance, you could stop all archiving processes, create a backup of the instance with VSS, and store the backup in the new location. Then you just have to change the path instead of waiting for the transfer process.


Script

Here comes the scripting part, yeah.

Retrieved from "https://help.mailstore.com/en/spe/index.php?title=MailStore_Server_to_MailStore_SPE_Migration&oldid=1173"