I’ve moved to using AMP in a VM over its original home on a standalone server, and now I’d like to move my instances over from the old HD and I’m not seeing how I can do that. Is this even possible?
once you’ve installed amp on the new ‘system’ go to your old datastore location and copy the whole “Instances” folder over to the new datastore. restart amp and should work no problem
You can do that or you can create a backup of the instance and copy it over and restore it.
My problem is, it doesn’t give you the option to restore, even after the backup is transferred over to the new “back up” directory.
You treat it just as a normal zip file and extract it.
Hello,
I have spent hours trying to migrate from one linux server to another. I am not a linux admin guru, but I am an IT professional and have plenty of experience. I have 2 linux servers with SSH/SFTP access between them. I could not find any good articles here or on YouTube to do this, so I pieced together the steps below from what I could learn. However, it isn’t working. The Amp console reports no instances, but I can see the folders in the console when I go to File Manager and click into the “”__VDS__Datastore-DefaultDatastore" folder.
- SSH into old server and go to .ampdata folder in /home/amp
- tar instances folder
- Use SCP to get tar file from old server (file copy via SSH). Exit old server.
- SSH into new server. Confirm file copied.
- Use sudo tar to extract instances archive back to original location (run from root /)
- Use ls to confirm files
- Run ampinstmgr fixperms
- Reboot server
- Login to Amp console (note: password changed to password used on old server)
- From Main Menu > Datastores, run “Repair”
Consoles shows no instances.
Any guidance here? Thanks.
Ping @Mike or anyone on staff that can reply to my post. Thanks so much!
Guide to migrate individual instances by hand:
https://discourse.cubecoders.com/t/moving-instances-from-one-amp-server-to-another-with-existing-instances/18341
The following are a general list of steps that would be a tad safer migrating all your instances across systems, and doesn’t require the repair step.
Note, to log into the amp
user you can run (su -l amp
or sudo su -l amp
[lowercase L
, not a 1
])
On the old system:
- (if possible) Update AMP and
ampinstmgr
: https://discourse.cubecoders.com/t/how-to-update-amp-to-the-latest-version/2297 ampinstmgr stopall
asamp
On the new system do the following:
- install AMP
- as
amp
, runampinstmgr stopall
- stop the
ampinstmgr
service (service ampinstmgr stop
on debian) - nuke/remove
.ampdata
(or just rename it to be safe, you never know) - restore your own
.ampdata
folder on the new machine - as
root
, runampinstmgr fixperms
- start the
ampinstmgr
service (service ampinstmgr start
on debian) - as
amp
, runampinstmgr reactivateall
- reboot if things look funny
TPK,
Thanks for posting this! I learned a lot going through the process with my method. I feel better knowing if I have to do it again, there is an “official” guide!
Neo