Hi
I have been trying to sort out some issues that occur in my backup logs to no avail, and I was wondering if anybody else has had/got the same issues.
The start of the log file is as follows:
[cpbackup] Started at Fri Jul 6 22:29:18 2012
[cpbackup] Mount found (********-backups.vps-10.com:/backups/**.**.***.** on /backups type nfs (rw,noexec,noatime,hard,intr,rsize=8192,wsize=8192,n
Hi!
I look at ls -ltr /backup/cpbackup/monthly and I see those backups are three months old, two months old and the like across all of my Cpanel servers.
I renamed monthly to monthly.0 and then created an empty monthly hoping that would flush something wrong with the backup system.
Ran backups this morning, but the logs say...
At the end of my log file I have:
HTML Code:
.....
[cpbackup] Copying weekly backups to monthly backups for retention
Waiting for load to go down to continue
Waiting for load to go down to continue
'top' gives me load average: 1.65, 1.15, 0.98
The backup disk is mounted on /backup with SSHF
I've changed the "Extra CPUs for server load" from "0 (default)&quo
I've been looking at the backup option in cPanel while it would be great to have it able to do versioning, for now I think a small change would make it even better.
When backup is scheduled for Daily, Weekly and Monthl. cpbackup does the daily first then copy it over to weekly and monthly.
This means, there is at least once a week when daily = weekly and once a month daily = monthly.
Hello,
Is it possible to put the date in the backup file?
The cpbackup run every day and send backups to a remote FTP server, with the name "user.tar.gz", it is possible change the name to "user.YYYY.MM.DD.tar.gz"?
I believe that the code responsible for this in cpbackup is:
Code:
(...)
my $target_file = ( $CONF{'COMPRESSACCTS'} eq 'no' ?
We are looking at getting a new server, and we are thinking about getting 4 drives in a Raid 1+0 array (mirrored and striped).
However, we cannot get more than 4 drives, so we can't get a 5th drive as an "onsite" backup.
Hi,
Currently cpbackup makes a copy of each site home directory (/home/username) in "/home/cpbackuptmp/cpbackup/daily" and then creates an archive from those files. Can the cpbackup process be modified so that it creates the archive directly from the /home/username directory. This will save a lot of time and disk/io during the backup process.
Some folks do a manual backup, then they leave the big file, eg. backup-9.23.2012_18-55-42_user.tar.gz in their subweb, then later they do another manual backup....
I'm sure you get where I'm going here, each backup archive expands exponentially in size because it includes a backup, of the previous backup archive, of the previous backup archive, etc. etc.
Some of our accounts on our server do not have database or are so rarely updated.
Will the new backup system allow for backups that are daily on some accounts while weekly etc on others.
If not, please request this :)