#14 FTP aborts prematurely

[Anonymous]

I was recently trying to do a G4L backup/restore of a CentOS 4.6 machine running on top of VMWare Server 1.X. I was able to get the backup portion to finish (seemingly) but I haven't had any luck restoring. I tried for about 3 hours last night and the restore process would hit 20% - 40% after around 1 hour then jump to 100%. Obviously the resulting disc was not bootable. Any suggestions or places to look. The ftp long just said "transfer aborted".

Thanks.

[Michael Setzer II]

A number of questions come to mind?
First, were you doing an image of a disk or partition?
What was the ftp server that was being written two, and what was the file system?
What was the size of the image file? Does the image pass the compression test?

If the files system of the ftp server was fat32, it limits the size to 2 or 4G.
If the image eas completed, a test can be run using the compression option.
lzop -t image.lzo
If it passes the test, the image should be good.
After the failure, you can check the files in the /tmp directory, and see if it reports what the error was.
Was it an ftp error or a write error.

I generally can do an 80GB drive in about 45 minutes, so unless you have a huge drive or very slow network, sonething isn't correct.

[Michael Setzer II]

A number of questions come to mind?
First, were you doing an image of a disk or partition?
What was the ftp server that was being written two, and what was the file system?
What was the size of the image file? Does the image pass the compression test?

If the files system of the ftp server was fat32, it limits the size to 2 or 4G.
If the image eas completed, a test can be run using the compression option.
lzop -t image.lzo
If it passes the test, the image should be good.
After the failure, you can check the files in the /tmp directory, and see if it reports what the error was.
Was it an ftp error or a write error.

I generally can do an 80GB drive in about 45 minutes, so unless you have a huge drive or very slow network, sonething isn't correct.

[Nobody/Anonymous]

I was doing an image of the source disk (125GB, of which 68GB or so is used). The FTP Server I was using was my standard work PC With Vista x64 (ntfs FS) running Filezilla Server. The image completed, I didn't try any lzop testing, I'll need to find a windows tool to do this. The problem was the restore, after between 20% - 25% (varied by attempt) it would jump to 100% and say it was done. The FTP server log just states a Transfer abort from the client side.

The 3 hours I mentioned involved 4 failed attempts like this, always failing at different percentages. I'll try to check the lzop status and go from there. Thanks.

[Nobody/Anonymous]

Yes the lzop compressed file failed the test, how can I be sure the file gets compressed and sent over correctly? I'm trying to move productions servers and the downtime needs to be kept to a minimum. Thank you for any advice.