H
Helter
Guest
I'm doing a migration, going from 7.5 to 8.6. I have about 26 clients, and about 80 domains. Total data size should be around 40-50 GB.
I started the migration last night, and it was moving along well for a few hours, then just *stopped* progress wise. The /migration/ folder on the remote host has not had any changes for 16 hours, the progress meter on the new server has not moved for the same period. The migration script is still running on the remote host and taking up quite a lot of resources though. What caught my eye is that the migration folder is taking up exactly 4.0 GB... which makes me think that it's a built in limit of some kind, rather than just where it happened to stop. I have plenty of space on the drive that it's on, but I have clients with domains larger than 4 GB...
I checked the manual for the migration manager before running it, and didn't notice any limits that I could change like that, or any config files that I could customize. I did notice that if it runs out of disk space, it can trash the remote host though. On my new server, the migration log and dumping status xml file *are* still being written too, and don't have any errors that I can find...
Before doing this I did a test migration with a single client, which went fine (had a problem with a single mysql db, that was all).
Any advice? If I need to stop this and adjust file limits or something, I'd rather do it now than later...
I started the migration last night, and it was moving along well for a few hours, then just *stopped* progress wise. The /migration/ folder on the remote host has not had any changes for 16 hours, the progress meter on the new server has not moved for the same period. The migration script is still running on the remote host and taking up quite a lot of resources though. What caught my eye is that the migration folder is taking up exactly 4.0 GB... which makes me think that it's a built in limit of some kind, rather than just where it happened to stop. I have plenty of space on the drive that it's on, but I have clients with domains larger than 4 GB...
I checked the manual for the migration manager before running it, and didn't notice any limits that I could change like that, or any config files that I could customize. I did notice that if it runs out of disk space, it can trash the remote host though. On my new server, the migration log and dumping status xml file *are* still being written too, and don't have any errors that I can find...
Before doing this I did a test migration with a single client, which went fine (had a problem with a single mysql db, that was all).
Any advice? If I need to stop this and adjust file limits or something, I'd rather do it now than later...