Documentation Update - Migrating to new host

[Ryan Blenis]

http://www.mailpiler.org/wiki/current:migration-to-new-host

Should probably include an instruction to disable the purge.sh script in cron on the new host until copying of all files from oldHost to newHost is complete.

This might be an edge case since I’m migrating servers AND upgrading the install, but would still apply to someone migrating then upgrading.

Situation: Upgrading and migrating servers from 1.1.0 to 1.3.8, the purge.sh cronjob did not exist and was not being run frequently. With 1.3.8 the purge.sh/pilerpurge.py utility is in cron and runs daily. Hence the “deletions” started happening before the files exist on that server, so now when the transfer from the old host completes, those emails that are supposed to be deleted will exist on the new host, taking up space that they should not.

‌

Thanks as always.

‌

PS. I thought about resetting the `deleted` in the metadata to 0 and re-running the purge once the transfer is complete, but this could screw up refcounts for attachments- so if you know of a better way to fix this, I’m all ears, otherwise I’ll have to live with the ~660,000 extra emails existing on the new host that no longer need to be retained.

[Janos SUTO]

Thanks for the hint, I've fixed the docs.

[Janos SUTO]

I’m confused. Did you run the purge script on the old host? If so, then those extra emails shouldn’t exist on the old host, and they certainly couldn’t end up on the new host.

[Ryan Blenis]

I actually couldn’t run the purge script on the old host before the migration. There were so many [to be purged] the old pilerpurge (c version, 1.3.8’s python version runs fine on the new server, apparently) choked the server for memory and it killed the process before it could actually do anything- so I had to wait until after the move.