View Full Version : Migraton of DA from server to server possible?
etegration
02-16-2004, 02:00 AM
I am about to upgrade my hdd to SCSI drives and there'll be a need to change the mobo as well. Will DA be able to migrate all existing accounts, files and settings?
I see http://www.directadmin.com/features.php?id=293 but when i i check out my CMD_USER_BACKUP=reseller/backups.html as in http://www.mydomain.com:2222/CMD_USER_BACKUP=reseller/backups.html
I get an error:
You cannot execute that command
--------------------------------------------------------------------------------
Details
The request you've made cannot be executed because it does not exist in your authority level
hmmm...why so? i am logged in as admin. If admin cannot do that, no one can right?
DirectAdmin Support
02-16-2004, 09:23 AM
Hello,
1) Make sure you've updated to 1.21.0 (we'll be forcing it out soon)
2) Make sure you're actually logged in as admin (so it's probably #1)
John
etegration
02-16-2004, 07:31 PM
Originally posted by DirectAdmin Support
Hello,
1) Make sure you've updated to 1.21.0 (we'll be forcing it out soon)
2) Make sure you're actually logged in as admin (so it's probably #1)
John
does backing up of all user feature backup everything including their mySQL database, POP3 userID/ password? and can be restored weith everythin intact?
btw, or there any easy way to upgrade DA to 1.21.0 leaving all data and accounts on the server intact too?
DirectAdmin Support
02-17-2004, 09:23 AM
Hello,
Backups store all user data, including the mysql datbases and pop acccounts/passwords, as you've mentioned.
The upgrade to 1.21.0 doesn't change any of the existing user data. It just provides a new binary and some skin updates.
John
etegration
02-18-2004, 07:21 AM
Originally posted by DirectAdmin Support
Hello,
Backups store all user data, including the mysql datbases and pop acccounts/passwords, as you've mentioned.
The upgrade to 1.21.0 doesn't change any of the existing user data. It just provides a new binary and some skin updates.
John
Thanks for the reply.
etegration
02-22-2004, 12:10 AM
Originally posted by DirectAdmin Support
Hello,
1) Make sure you've updated to 1.21.0 (we'll be forcing it out soon)
2) Make sure you're actually logged in as admin (so it's probably #1)
John
Hi John, dies Directadmin gets updated automatically? As i have this in my message system.
Subject: DirectAdmin has been updated 02/17/2004
This is an automated message notifying you that the DirectAdmin software has been successfully updated.
To view what has changed, please visit:
http://www.directadmin.com/versions.php
From: Message System
etegration
02-22-2004, 12:12 AM
Originally posted by etegration
Hi John, dies Directadmin gets updated automatically? As i have this in my message system.
sorry, i have seen the answer @ http://www.directadmin.com/forum/showthread.php?s=&threadid=2046
I have tried running http://www.mydomain.com:2222/CMD_USER_BACKUP=reseller/backups.html
Same error:
You cannot execute that command
--------------------------------------------------------------------------------
Details
The request you've made cannot be executed because it does not exist in your authority level
i am logged in as admin. I'm gonna migrate to another hdd and running RAID 0 soon, i hope i can get this migrartion working...
DirectAdmin Support
02-22-2004, 11:33 PM
Hello,
the link is actually just:
mydomain.com:2222/CMD_USER_BACKUP
If you're using our skins, it's accessible from the Reseller Panel. The reseller/backups.html part is only for skin designers to place inside the files_reseller.conf
John
etegration
03-30-2004, 06:31 AM
Originally posted by DirectAdmin Support
Hello,
the link is actually just:
mydomain.com:2222/CMD_USER_BACKUP
If you're using our skins, it's accessible from the Reseller Panel. The reseller/backups.html part is only for skin designers to place inside the files_reseller.conf
John
Hi john, suggestion: a "Check All" function in Step 1. ;)
For the restoration do i:
1. Setup the server, install redhat 9 and Directadmin
2. Copy all files from old server to new server and place all files in ~/admin/user_backups/ on new server then use the Restore Backup function?
regards.
?
DirectAdmin Support
03-30-2004, 10:18 AM
Hello,
You should be able to click "Select" in the top right hand corner of the list of Users. That should "Check All" users in the list.
We will be adding an admin version of the "Manager User Backups" once the bugs get ironed out.
Yes, your steps should be all that's needed for user restores.
John
etegration
04-03-2004, 08:27 AM
Originally posted by DirectAdmin Support
Yes, your steps should be all that's needed for user restores.
John
Hi john, "should" work? It's not been tested before as a migraiton tool? Just seriously considering the migration this week so i hope it can really work before i do anything that may turn "deadly". :(
DirectAdmin Support
04-03-2004, 02:50 PM
Hello,
I didn't mean to alarm you. What I meant is that the backup/restore/transfer system is very new, so that always increases the probability of minor bugs popping up. We've addressed them all to this point though, so you are unlikely to experience anything catastrophic. Just make sure you have the most current version of DA before starting. :)
John
etegration
05-01-2004, 07:17 AM
Originally posted by DirectAdmin Support
Hello,
I didn't mean to alarm you. What I meant is that the backup/restore/transfer system is very new, so that always increases the probability of minor bugs popping up. We've addressed them all to this point though, so you are unlikely to experience anything catastrophic. Just make sure you have the most current version of DA before starting. :)
John
thanks John for the reply. I also see that DA is tied to a specific IP address. Thus, a specific way i am thinking of but need your kind advise:
1. Up the new server first with everything install, install DA etc etc. This new server will use another 2 IPs, do i request through my provider to allow DA to work with one of this IP to install DA and allowing it to run properly.
2. Do all the copying from the old server the this new server either through hdd to hdd or via the datacenter's internal network. "Copy all files from old server to new server and place all files in ~/admin/user_backups/ on new server then use the Restore Backup function"
3. Use the restore and backup function in DA.
That should do it right? i am still in the mist of configuring the new server, problems with the SCSI part but should be up soon...just found great drivers for the SCSI chip...
nobaloney
05-01-2004, 12:08 PM
Originally posted by etegration
That should do it right? i am still in the mist of configuring the new server, problems with the SCSI part but should be up soon...just found great drivers for the SCSI chip...
We ran into some problems recently with external drivers; we couldn't update the kernal on the machine in question, because we couldn't drivers that would work with the updated kernel.
When choosing SCSI, an otherwise unsupported RAID card, or an otherwise unsupported ethernet card, be aware of the fact that you may never be able to upgrade your kernel.
Jeff
etegration
05-09-2004, 12:04 AM
Originally posted by jlasman
We ran into some problems recently with external drivers; we couldn't update the kernal on the machine in question, because we couldn't drivers that would work with the updated kernel.
When choosing SCSI, an otherwise unsupported RAID card, or an otherwise unsupported ethernet card, be aware of the fact that you may never be able to upgrade your kernel.
Jeff
Thanks Jeff for the headsup. I just got my SCSI drives up with RAID 1 in place. The problem was with HostRAID. I used http://www.adaptec.com/worldwide/support/driverdetail.jsp?sess=no&language=English+US&cat=/Product/ASC-29320-R&filekey=a320raid-1.2.0-14-rh90_i686.rpm and it solved everything. it did mention http://www.tux.org/lkml/#export-tainted which i have gone through i hope i do not get into any probloems. Just need a confirmation of some sort from DA team on the migration. I really don't wanna messed things up.
XYZed
05-09-2004, 01:21 PM
Hi etegration,
If you haven't done this yet - I just have - and well it went rather smoothly, some accounts failed, but after removing and doing again it restored on a per failed basis.
It didn't restore any domain pointers (parked domains), so keep a list of those. It did do subdomains thankfully.
The only glitch I had was MySQL not connecting with da_admin@localhost even though I could in SSH. That was just the random password in /usr/local/directadmin/conf/mysql.conf.
Hope it goes as easy for you.
etegration
05-11-2004, 07:07 PM
Originally posted by XYZed
Hi etegration,
If you haven't done this yet - I just have - and well it went rather smoothly, some accounts failed, but after removing and doing again it restored on a per failed basis.
It didn't restore any domain pointers (parked domains), so keep a list of those. It did do subdomains thankfully.
The only glitch I had was MySQL not connecting with da_admin@localhost even though I could in SSH. That was just the random password in /usr/local/directadmin/conf/mysql.conf.
Hope it goes as easy for you.
superb! Thanks for the feedback man. So parked domains, i have a few accounts with parked domain, i think can just simply jot them down manually before migrating them then. I'll be migrating slowly over a span of one month just in case anything unexpected happens. Thanks again!
i don't get what you mean on
The only glitch I had was MySQL not connecting with da_admin@localhost even though I could in SSH. That was just the random password in /usr/local/directadmin/conf/mysql.conf.
what implications are there when mySQL cannot connect to da_admin@localhost? it will not be tied together with DA?
XYZed
05-11-2004, 07:32 PM
Basically, that even if you can log in to MySQL using da_admin and your password. Make sure that password is also listed in /usr/local/directadmin/conf/mysql.conf
If it is different (and even if you can log into MySQL with your password) the transfered sites won't be able to restore and it will tell you incorrect password. So just double check that it is the same password and that you can login to MySQL at the command line and then the users databases will work perfectly.
Ohh also don't forget to install any Perl modules etc that you may have installed (such as DBD::mysql).
It only took about 3 hours very late at night to get everything backed up, moved over and restored, not 1 single customer on that server even noticed :-)
What I did was get the backed up data on the new server with a different IP (DA let me 'borrow' a license for that - thanks guys) and then once I had restored the sites, checked what I could at IP/~username and then blocked the old server and then put the old main IP on the new server and changed each account to that. So to a customer there was probably 10 minutes downtime they may have seen.
Cheers.
etegration
05-13-2004, 12:01 AM
Originally posted by XYZed
Basically, that even if you can log in to MySQL using da_admin and your password. Make sure that password is also listed in /usr/local/directadmin/conf/mysql.conf
If it is different (and even if you can log into MySQL with your password) the transfered sites won't be able to restore and it will tell you incorrect password. So just double check that it is the same password and that you can login to MySQL at the command line and then the users databases will work perfectly.
Ohh also don't forget to install any Perl modules etc that you may have installed (such as DBD::mysql).
It only took about 3 hours very late at night to get everything backed up, moved over and restored, not 1 single customer on that server even noticed :-)
What I did was get the backed up data on the new server with a different IP (DA let me 'borrow' a license for that - thanks guys) and then once I had restored the sites, checked what I could at IP/~username and then blocked the old server and then put the old main IP on the new server and changed each account to that. So to a customer there was probably 10 minutes downtime they may have seen.
Cheers.
sounds great, my plan is slightly different. i have 4 IP currently but using only 3. One of it is for DA. I gotten another 2 IP from my provider for the new server's DNS and making use of the extra 1 IP for one more DA license. I'll be migrating slowly over a span of one month as i may be keeping that old server active for other stuffs still in the works (wish me luck!) while using the better server for the hosting stuffs. :D
Thanks again for all the knowledge sharing!
Powered by vBulletin™ Version 4.0.4 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.