For additional guidance, check out our community articles detailing the process of migrating from your current platform to Carbonio CE.
For enterprise-level requirements and advanced features, consider checking out Zextras Carbonio – the all-in-one private digital workplace designed for digital sovereignty trusted by the public sector, telcos, and regulated industries.
Mailbox Move is a function present in Zextras Powerstore. Through the command doMailboxMove, an action is performed to let you move all of the accounts inside a domain or a set of them (even just one if needed), from a storage server to another one.
How it Works
Before starting the moving operation, you need to verify that on your destination server you have enough space for data that will be transfered.
After doing that, you can start performing the Mailbox Move by using the following syntax:
zxsuite powerstore doMailboxMove {destinationHost} [attr1 value1 [attr2 value2...]]Where destinationHost is the host where you want to move your mailbox and it is the only Mandatory parameter to enter.
For a complete list of parameters you can add to the command, and their explanation, I suggest you to read our official documentation.
For each mailbox there are 3 stages for the operation to be completed:
- blobs: All blobs are copied from the source server to the destination server.
- backup: All backup entries are copied from the source server to the destination server.
- account: All database entries are moved as-is and LDAP entries are updated, effectively moving the mailbox.
Scenarios
There are various scenarios related to mailboxmove command. The best one, probably, is with Centralized Storage. Having this kind of structure, the blobs will not be migrated, since the storage is “centralized”.
Another scenario is the use of a classic storage system. In this case, when you are going to use MaiboxMove command, you can decide to apply or not HSM rules at the end of the process. That can be done by setting the hsm parameter to true or false.
But what it is interesting to be considered, is that if you decide to use HSM after moving data, you’ll probably don’t want to apply that only after moving all accounts. This also thinking about the possibility that the destination server is too small.
By default HSM is set to false so if you want to choose this option you don’t need to enter the parameter in your command line. In this case no defined policy of the destination server will be applied after a mailbox (or a set of them) is successfully moved.
On the other hand, setting HSM to true can be useful when you want some of the data to stay on the primary volume even after mailboxmove. You can eventually also set a rule to move them later or after a specific time range.
It is also important to note that setting HSM to true will apply the rules only to the account or mailbox (or set of them) you are moving and not to all domain’s account.
