How can I restore a 20 gig website on a server that only has 60 gigs in /home

[DWHS.net]

I have 54G for /home and 54G /backup

The website to restore is 20 gigs, how can I use my current space to install this full back up. It looks like cpanel needs three times the space of the back up which is too much currently to do this.

Currently I moved the main tarball to back up, then created a symlink to it from the home directory so cpanel can see the restore file. But it looks like it make a new tar file and uncompressed it and copied it to the domain. This is three times the size again.

[d_t]

uncompress the backup tar.gz and move the folder that is bigger on the other partition (it may be homedir/public_html or homedir/mail ). Then compress it again and restore backup from cpanel. At the end, copy the folder back to user account (and ensure owner/permision are set ok)

[Spiral]

My first question before offering you a solution best suited for you ...

How in the world do you have a 20 GB web site?

And it's really 20 GB after archiving?

I have personally worked with some of the mega monster huge sites
from some of the most widely known name on the internet and I am
not sure I've ever seen any that were 20 GB excluding of course those
with streaming multimedia and such which are almost always stored
seperately and not part of the actual web site directly so don't really
count anyway.

Anyway, point in fact --- if it's really that large, I think you are probably going to be needing larger drives / partitions than what you mentioned.

[ManojB]

In order to restore huge data, you will have to do this manually like create a new account on new server, dump databases, rcync all the data ie public_html folder to new server and restore all the databases.

[cPanelDon]

I have 54G for /home and 54G /backup

The website to restore is 20 gigs, how can I use my current space to install this full back up. It looks like cpanel needs three times the space of the back up which is too much currently to do this.

Currently I moved the main tarball to back up, then created a symlink to it from the home directory so cpanel can see the restore file. But it looks like it make a new tar file and uncompressed it and copied it to the domain. This is three times the size again.

You may want to try leaving the full backup archive on your /backup partition or drive (without having to create a symlink), then run the restore script manually, using a command such as the following:

# /scripts/restorepkg /path/to/fullbackup.tar.gz

In the above example, replace "/path/to/fullbackup.tar.gz" with the actual full path and file name of where your full backup archive is located.

You may also want to check in the following directory to remove old backup archives or copies of such that you may no longer require or need: "/home/cprestore/" You can use a command such as the following to view a list of the directory contents and check its disk usage:

# ls -ahl /home/cprestore/
# du -ahx --max-depth=1 /home/cprestore/