Topic: backup2ws strange problems (6.0.1, beta version of contrib)

[Brushfireb]

Everyone,

I have been seeing a strange problem with the Backup2ws contrib. I am using the beta version released for SME 6.

Essentially, I have the regular backup set to run every night at 10pm. And it does. However, it doesnt finish until about 10am the next day. At first I thought the network was just slow, but then I realized that the problem is that each night, the backup2ws creates about 30gigs of backup files (each file is 665 megs, so about 47 files).

The strange part about this is that the hard drive on SME that it is backing up is a 20GB drive, with only 2GB used. (This according to two different SME contribs that monitor disk space/usage).

Any ideas why this program would take 2GB of files to backup and generate about 30GB of backup files from it?

Brian

[pkidd]

what is in the 47 files?

[Brushfireb]

Strangely, I never bothered to look.

Most of them are filled with 1 folder, "dev"

and inside that folder are many files, like below:

Code: [Select]


hda <-> size: 0 packed: 21,788,957,206
hda1 --> size: 0 packed: 41,517,720
hda10 size: 0 packed: 8

With sort of random variations on the packed size and file name within the dev folder.

This is really odd. Am i having some issue with the program that creates the archives?

[Brushfireb]

Anyone have any ideas here? Still searching but no solutions yet.

Im concerned I am not getting any sort of valid backup files.

Brian

[Mumm-Ra]

Brian,
I'm assuming that you're doing a disaster recovery backup job?
Have you tried just backing up your Primary i-bay just as a test
use

Code: [Select]

/home/e-smith/files/ibays/Primary as your source with no exclusions.  Enter your username & password for your share and set it to manual.  Create this backup job then save the changes.
Then run a manual backup to see if it will complete this.
Check the message log for any errors. If this completes try removing the disaster recovery job, saving the changes then re-setting it up then saving the changes again.
The run the job manually to see what it backs-up, remember to check you message log for errors.
You could also remove the /dev folder from the backup job by entering

Code: [Select]

/bin,/boot,/etc,/home,/initrd,/lib,/opt,/quota.group,/quota.user,/root,/sbin,/service,/usr,/var for your source then see what backs-up.
The try putting the /dev folder back in and running the backup again.