MailStore Server to MailStore SPE Migration - Revision history

Ltalaschus at 13:26, 5 February 2025

2025-02-05T13:26:52Z

Ltalaschus at 13:04, 5 February 2025

2025-02-05T13:04:02Z

Ltalaschus at 12:48, 5 February 2025

2025-02-05T12:48:34Z

Ltalaschus at 12:46, 5 February 2025

2025-02-05T12:46:30Z

Cstelzmann at 13:35, 3 December 2024

2024-12-03T13:35:22Z

Ltalaschus at 17:07, 2 December 2024

2024-12-02T17:07:58Z

Bmeyn at 09:22, 17 June 2019

2019-06-17T09:22:32Z

Ltalaschus at 11:16, 28 March 2019

2019-03-28T11:16:14Z

Ltalaschus at 11:13, 28 March 2019

2019-03-28T11:13:10Z

Ltalaschus at 10:41, 28 March 2019

2019-03-28T10:41:36Z

@@ Line 4: / Line 4: @@
 As the two products use a slightly different format of the master database (''MailStoreMaster.fdb''), which contains the configuration, it is not possible to move the entire ''MailArchive'' directory of MailStore Server onto a MailStore SPE Instance Host. However, it is possible to transfer all archive stores, which contain the actual messages, by following these simple steps:
-<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on version 24.2.1 or higher and they must not need an upgrade. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. Internally an upgrade to Firebird 4 database engine will be performed. See [https://help.mailstore.com/en/server/Update_Notices_for_MailStore_Server_to_version_25.1_or_newer#Update_from_version_24.x the update notices] for more information. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
+<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on version 24.4 or higher and they must not need an upgrade. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. Internally an upgrade to Firebird 4 database engine will be performed. See [https://help.mailstore.com/en/server/Update_Notices_for_MailStore_Server_to_version_25.1_or_newer#Update_from_version_24.x the update notices] for more information. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
 * First [[Creating_Instances| create a new MailStore SPE Instance]]. The instance must not be started yet.
 * Stop all archiving profiles in MailStore Server, either by setting the execution mode to ''manual'', by disabling all ''Jobs'' or by disabling all scheduled tasks.

@@ Line 11: / Line 11: @@
 <p class="msnote">'''Important Notice:''' After this step, do not run any of the archiving profiles in MailStore Server again, otherwise you might risk that  emails are not getting archived by the MailStore SPE Instance (i.e. when a profile contains automatic deletion rules).</p>
 * Start the MailStore SPE Instance.
-* [[Instance_Management#Attach_Existing_Archive_Store|Attach the archive stores]] that were previously transferred to the newly created instance. In case the archive store is migrated from MailStore Server 10 or newer the recovery key (product key or generated value) of the source MailStore Server installation is required. You have to use the ''UnlockStore'' command in the ''DEVELOPER'' > ''Management API'' window of the Management Console as described [[Instance_Management#Unlock_Archive_Stores|here]].
+* [[Instance_Management#Attach_Existing_Archive_Store|Attach the archive stores]] that were previously transferred to the newly created instance. The recovery key (product key or generated value) of the source MailStore Server installation is required. You have to use the ''UnlockStore'' command in the ''DEVELOPER'' > ''Management API'' window of the Management Console as described [[Instance_Management#Unlock_Archive_Stores|here]].
 * Set the state of one archive store to ''Current''.

@@ Line 4: / Line 4: @@
 As the two products use a slightly different format of the master database (''MailStoreMaster.fdb''), which contains the configuration, it is not possible to move the entire ''MailArchive'' directory of MailStore Server onto a MailStore SPE Instance Host. However, it is possible to transfer all archive stores, which contain the actual messages, by following these simple steps:
-<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on version 24.2.1 or higher and they must not need an upgrade. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. Internally an upgrade to Firebird 4 database engine will be performed. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
+<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on version 24.2.1 or higher and they must not need an upgrade. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. Internally an upgrade to Firebird 4 database engine will be performed. See [https://help.mailstore.com/en/server/Update_Notices_for_MailStore_Server_to_version_25.1_or_newer#Update_from_version_24.x the update notices] for more information. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
 * First [[Creating_Instances| create a new MailStore SPE Instance]]. The instance must not be started yet.
 * Stop all archiving profiles in MailStore Server, either by setting the execution mode to ''manual'', by disabling all ''Jobs'' or by disabling all scheduled tasks.

@@ Line 4: / Line 4: @@
 As the two products use a slightly different format of the master database (''MailStoreMaster.fdb''), which contains the configuration, it is not possible to move the entire ''MailArchive'' directory of MailStore Server onto a MailStore SPE Instance Host. However, it is possible to transfer all archive stores, which contain the actual messages, by following these simple steps:
-<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on Firebird 4 or higher. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
+<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on version 24.2.1 or higher and they must not need an upgrade. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. Internally an upgrade to Firebird 4 database engine will be performed. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
 * First [[Creating_Instances| create a new MailStore SPE Instance]]. The instance must not be started yet.
 * Stop all archiving profiles in MailStore Server, either by setting the execution mode to ''manual'', by disabling all ''Jobs'' or by disabling all scheduled tasks.

@@ Line 4: / Line 4: @@
 As the two products use a slightly different format of the master database (''MailStoreMaster.fdb''), which contains the configuration, it is not possible to move the entire ''MailArchive'' directory of MailStore Server onto a MailStore SPE Instance Host. However, it is possible to transfer all archive stores, which contain the actual messages, by following these simple steps:
-<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on Firebird 4 or higher. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>When the customer does not want to share the product key, to decrypt the archive store, with the service provider, the recovery key can be set to a generated value before migrating.</p>
+<p class="msnote">'''Important Notice:''' The MailStore Server archive stores must be on Firebird 4 or higher. If this is not the case, the entire archive (MasterDatabase and Archive Stores) must be loaded once into a MailStore Server 24.4 before it can be migrated to the SPE. All archive stores must be manually upgraded to the latest version, because then some necessary database upgrades will be performed. The MailStore SPE version must be equal or higher than the MailStore Server version where the archive stores were attached to last. <br/><br/>If the customer does not want to share the product key to decrypt the archive store with the service provider, the recovery key can be set to a generated value before migrating.</p>
 * First [[Creating_Instances| create a new MailStore SPE Instance]]. The instance must not be started yet.
 * Stop all archiving profiles in MailStore Server, either by setting the execution mode to ''manual'', by disabling all ''Jobs'' or by disabling all scheduled tasks.