Moving DA to new server

W

wanos

Verified User
Joined
Aug 5, 2004
Messages
16
Hi,
I have been using DA for a while & am now migrating all users etc to a new server. This appears to be harder than installing DA & restoring from the admin level backup.

I am moving from RH9 to Debian Lenny.

Some observations so far -
There appears to be a need to add a user before restoring... why ? Even if restored from the admin/reseller who created or the admin account, if I don't add the user first it fails. After I add the account permissions are still an issue.

Bind 9 seems to have issues with ".options" & ".local" files & DA prefers to just append to the end of named.conf.

MySQL has issues all over the place.

Exim has issues with exim4 - partly cured from this forum.
Mail seems to place the mail in a location which is hard to imap into & pop which is /var/spool/virtual/domain/user

That's what I have found so far.

Can anyone suggest a simple way to get the users moved over & create accounts etc ?(or point to some stuff in the forum I haven't found yet)

Cheers,

Wanos
 
We move users from one server to another by
1. Installing the new server first
2. Creating user account backups from the reseller level
3. Creating reseller (let's call it newreseller) on the new server
4. Copying backups to newreseller/user_backups/ directory of the new reseller
5. Logging into DA account of newreseller and executing backup restore from the reseller level

If your users do not use advanced MySQL options such as stored procedures, this little HOWTO should work well for you. Otherwise, you will have to transfer MySQL databases manually. Other than that, everything should work smoothly.

wanos said:
Mail seems to place the mail in a location which is hard to imap into & pop which is /var/spool/virtual/domain/user
Click to expand...
When you install a new server using custombuild, make sure to select dovecot. It uses different mailbox structure and stores everything under user's home directory. The mailboxes of the user accounts will be automatically converted during restore if necessary.


If you want help with some other issues, you need to be more specific ;)
 
I'd recommend using the admin level Admin Backup/Transfer; it will restore on a newly installed server without having to create anything first.

It will also convert mailboxes to Dovecot/Maildir, if they were formally mbox on the old server.

Jeff
 
jlasman said:
I'd recommend using the admin level Admin Backup/Transfer; it will restore on a newly installed server without having to create anything first.

It will also convert mailboxes to Dovecot/Maildir, if they were formally mbox on the old server.
Click to expand...
Well, it might sound like paranoia, but I don't trust system level restores, especially while transferring between different Linux distributions. For administrators who don't mind a little extra work to ensure system and data integrity, I would strongly suggest sticking with reseller backups/restores.
 
jlasman said:
I'd recommend using the admin level Admin Backup/Transfer; it will restore on a newly installed server without having to create anything first.

Jeff
Click to expand...

I have attempted to use the Admin Backup/Transfer; method & it fails with the error
Code: 
Unable to read the User data files for tlaa.
The permissions are ok. If the permissions are set to root or other users it fails with the error
Code: 
Unable to extract backup/user.conf from /backups/user.(reseller).(user).tar.gz : Error while extracting backup/user.conf to /backups/(user) as marcus : /bin/tar: /backups/(user): Cannot chdir: No such file or directory
/bin/tar: Error is not recoverable: exiting now
gzip: stdout: Broken pipe
Cannot read /backups/(user)/backup/user.conf : Unable to open /backups/(user)/backup/user.conf for reading.
The logs don't seem to have any more info than that.
 
Webcart said:
Well, it might sound like paranoia, but I don't trust system level restores, especially while transferring between different Linux distributions. For administrators who don't mind a little extra work to ensure system and data integrity, I would strongly suggest sticking with reseller backups/restores.
Click to expand...
Paranoia can be a good thing but in this case the admin backup simply makes and packages individual reseller backkups, and restores them in the right order.

Jeff
 
now MySQL DB's have an issue

Ok - have users restoring fine.
Now databases seem to have permission errors.
The problem is that although the users are added to the mysql table their passwords are invalid.
moving the username table doesn't work .. breaks roundcube as well.

Any ideas ?
 
wanos said:
Ok - have users restoring fine.
Now databases seem to have permission errors.
The problem is that although the users are added to the mysql table their passwords are invalid.
moving the username table doesn't work .. breaks roundcube as well.

Any ideas ?
Click to expand...

2 actually:
1. Try user level backup and see whether you are experiencing same problem
2. Check MySQL versions of the old and the new servers
 
You must log in or register to reply here.
Back
Top