[BUG] several issues when using backups to move sites to new server

[cagivacode]

I just did a server upgrade/move...I had to get off of centos 7. This was a long term cyberpanel install so it had been through a lot (remember when passwords were not hashed and then an upgrade went to hash --- I unexpectedly had to issue over 50 new email passwords in one day.).

So far I have had the following issues....

1). Broken DKIM on the transferred sites, I think it is worse as the DNS has invalid dkim txt files from the old server. 2). Forwarders do not transfer. It would require a change to the DB table structure (I had sqldumped all tables out of caution.). 3). No FTP passwords. Again, it is due to the DB table structure (I had sqldumped all tables out of caution.) All of my clients use FTP even the wordpress guys. 4). I don't have any of my CP accounts or packages, (I had tiered accounts that are bandwidth limited and assign to different packages).

I would have liked it if it was easier to get the backup files downloaded and uploaded to the new server. There was some issue with permissions on /home/backup.

In general, the transfer of sites was pretty quick.

[cagivacode]

Most of this is probably for a readme on using backups to move server (or reinstall server).

I should also note that I had several wordpress site backups that did not move their database. They "moved" a non-existent default database.

This is not CPs fault. This is because the site was originally created through CP and wordpress was installed through CP. However, the actual site was moved/deployed using a wordpress plugin. The plugin created its own database and therefore CP did not know about it. CP was not backing up the database for the website at all.

Just something to keep in mind....unless there is some way to let cyberpanel know about extra "associated" databases.