Giant Plesk Web Site Migration

11 posts / 0 new
Last post
#1 Fri, 05/16/2008 - 12:30
katir

Giant Plesk Web Site Migration

hmm I thought I already submitted this, but don't see it:

Our sites migration is going well. I'm moving up now to the larger sites. Himalayan academy.com has 32 GIGS of data in the httpdocs(public_html) directory. No data bases, 1 SSL and two mail users. Simple but a lot of data. The PLESK Back up will be gigantic. Well, at least in my experience (others will have even more data no doubt)

Will the VirtualMin Migration tool handle it? I just want to check first before ordering the Plesk back up. Three directories contain the bulk of the content audio, movies etc and photo gallerys from our daily blog doing all the way back to 1998. So, if VirtualMin will choke on 32 GIG, maybe there's a way to leave out those three directories and then move them manually?

When we initiate the migration from the GUI as a remote call, it's going to take a long time... if the web connection from my machine to the GUI breaks, will the migration break? Or will the migration continue as a background process on the server, whether or not the socket from here to the VirtualMin interface is open or closed?

Fri, 05/16/2008 - 12:58
Joe
Joe's picture

Your conversion is happening at the right time. Jamie just made some changes to allow Virtualmin to deal with really large Plesk backups. I've asked him to chime in here, to confirm that 32GB is not beyond the realm of sanity. I suspect that it will be fine with the new 3.57 version of Virtualmin (rolled into repos this morning, so you can get the upgrade already, though I haven't actually announced it yet).

--

Check out the forum guidelines!

Fri, 05/16/2008 - 13:13 (Reply to #2)
Joe
Joe's picture

As of Virtualmin 3.57, large Plesk backups shouldn't be a problem - older releases read the whole backup file into memory to decode it, which is going to be a problem if you don't have 32GB of RAM :-)

The new migration code extracts the backup in a streaming fashion, so any size is theoretically supported. Just make sure you have plenty of free disk space in /tmp, as it will extract the tar file of the home directory from the backup to /tmp/.webmin, and then un-tar its contents to the domain's home directory.

--

Check out the forum guidelines!

Fri, 05/16/2008 - 13:38
katir

OK, yes I have 3.56; then I need guidance on the upgrade... I don't see any "Check for Updates" on the GUI. and there is no "Upgrade Existing Installation- How To" in the documentation.

Fri, 05/16/2008 - 13:51 (Reply to #4)
Joe
Joe's picture

How did you do the original install? Was it from the .sh script we provide, or by manually installing the RPMs, Debian packages or Webmin modules?

--

Check out the forum guidelines!

Sun, 06/07/2009 - 07:22 (Reply to #5)
katir

I just ran

wget -O install.sh http://software.virtualmin.com/cgi-bin/install.cgi?serial=######\&key=######; /bin/sh install.sh

and it worked (sweet!)

Sun, 06/07/2009 - 07:22 (Reply to #6)
katir

I just ran

wget -O install.sh http://software.virtualmin.com/cgi-bin/install.cgi?serial=######\&key=######; /bin/sh install.sh

and it worked (sweet!)

Sun, 06/07/2009 - 07:22 (Reply to #7)
katir

I just ran

wget -O install.sh http://software.virtualmin.com/cgi-bin/install.cgi?serial=######\&key=######; /bin/sh install.sh

and it worked (sweet!)

Fri, 05/16/2008 - 14:05
Joe
Joe's picture

You should have a "Package Updates" section in the System Information page...if you don't, something is a wee bit amiss.

--

Check out the forum guidelines!

Fri, 05/16/2008 - 14:05
Joe
Joe's picture

Ok, so a regular pro version install.

When you login, you should see on the right-hand System Information page a list of updated packages available. But since we just released and there is caching done by YUM and virtualmin, they may not show up till tomorrow.

You can force an update from the command line though, with the commands :

yum clean all
yum install wbm-virtual-server wbt-virtual-server-theme

--

Check out the forum guidelines!

Fri, 05/16/2008 - 17:17 (Reply to #10)
katir

I ran the cmd line yum cmds. it worked

System read out on log in reads:
Virtualmin version 3.57 (Pro)

You and Jamie won't have enough room on your vests for all my medals (smile)

Topic locked