Hello ppdeonet,
5GB of exported data, which are ~10GB of actual data, in 6 hours are nowhere near good...
As perfectly analyzed by Trantor, the bottleneck is on the I/O performances of your ferry store (running an `htop` during the export will surely show that the impact on CPU and RAM is minimal).
I'd really follow Trantor's suggestion to directly connect the disk to the SATA bus of the server in order to let the disk work at full speed.
The steps would be:
- Stop Zimbra and shutdown the source server.
- Connect the ferry store to the source server's SATA bus.
- Start the server and mount the new disk.
- Stop the real time scanner, set the backup path to a directory on the ferry store and perform a FullScan operation.
- Stop Zimbra and shutdown the source server.
- Remove the ferry store from the server.
- Start the source server and shutdown the destination server
- Connect the ferry store to the destination server's SATA bus.
- Start the destination server, mount the ferry store and import your data (DO NOT initialize ZeXtras Backup).
- Mount the ferry store through SSHFS on the source server.
- Perform a SmartScan on the source server.
- Switch the mail flow to the destination server.
- Perform a SmartScan on the source server.
- Import again to align the data.
I know it is a long procedure which requires 2 server restarts, but it's the only way to speed up the process...
Keep us up to date with the status of your migration, we'll do our best to help
Have a nice day,
Cine
[Edit: When setting up a new server, always keep in mind the official guidelines posted HERE, they are not strictly related to very large deployments.]
Bookmarks