[ZendTo] Protip: Server Migrations and Remote Databases, Orphan Dropoff Cleanup

[Ricky Boone]

I'm writing this while restoring [most] of the dropoffs affected by
this, but wanted to at least get it out there in case anyone else
attempts to do something like this (or has to clean up someone else's
mess).

If your ZendTo environment uses a remote database, and you want to
migrate to another server, don't point the new server to the same
remote database.  Or, if you do, make sure the cron jobs don't run.

Assuming you aren't using a synchronized file system between the old
and new servers for dropoffs, you'll have one system finding a
boatload of orphaned dropoffs that don't exist on the filesystem that
it will want to wipe out of the database, then the other system will
have a boatload of missing dropoffs that it will want to clean up from
the filesystem that were just wiped by the other system.  It will
ignore dropoffs that are newer than 24 hours old... but that means the
longer it's left in this state, more gets wiped.

What fun!

Also: make sure you have frequent backups, and verify them... frequently.