JR5 to JR5 site to site import?

Environment - I'm on DigitalOcean hosting.
I have a situation where I need to move from a larger sized droplet to a smaller sized droplet. Unfortunately, DO doesn't have a way to resize down their droplets (with a few clicks) =(

https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/4074700-downgrade-option-not-just-upgrade

So, contacted DO support and they presented me with an option to:

1) create a new smaller droplet in the same datacenter
2) use rsync to sync the files between the two droplets
3) take a snapshot of the smaller server
4) destroy the larger server to release the IP
5) rebuild a new server from the snapshot and it should reclaim the same IP

My question is, does jamroom have the capability (perhaps a backend tool/module not offered to their customers) to do a site to site migration?

I understand it wouldn't be the same IP, but what I could do is prep a smaller sized droplet (install LAMP, etc), JR performs the JR5 to JR5 migration, then I can cut over DNS?

OR can JR perform the rsync migration as prescribed by DO, and I can pay for a custom support incident?

Please advise on any viable options.

Thanks!
BC
updated by @ilovehousemusic: 09/17/14 05:34:03AM

It's actually very easy:

- setup your other server identical one
- recursively copy the /home directory from your old to new server
- copy over the /var/lib/mysql directory to the new server (make sure and change ownership on it after the scp to the mysql owner).

Update DNS and you are on your new server. No need for any tool.

Hope this helps!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Documenting this thread here for everyone:
https://www.jamroom.net/the-jamroom-network/documentation/howto/1991/howto-move-jr5-to-a-different-server

Would it be possible to also

1. run a backup of the database using phpmyadmin.
2. destroy the droplet,
3. recreate a smaller one in the same datacenter
4. build out LAMP
5. reinstall Jamroom
6. reimport the database

Just reviewing my different options here...

Yes and No - if you only care about what is in the DB and don't care about any actual media files, then that will work. The media files are stored on the filesystem - NOT in the database.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

@Brian - understood. As a matter of fact, I am doing away with Audio uploads on my site and have notified my users it will be soundcloud import only.

And just so I have a complete picture. Would this method work also?

1. Run an full S3 backup to Amazon
2. Destroy droplet, create smaller droplet in same datacenter (digital ocean) obtains the same IP address
3. Build out LAMP, install JR
4. Use the restore tool to restore DB.

THanks for all the info and suggestions, I'm just trying to build a complete picture of my options (pros/cons) before I go through all this.

Thanks!
Brian

Yeah - that should work - or at least I would think so. It would be quicker though to just copy the /var/lib/mysql directory and restore it, but that's up to you.

Hope this helps!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net