From: Ralph P. <ra...@de...> - 2007-10-09 19:41:46
|
Am Freitag, 5. Oktober 2007 10:52:04 schrieb Franky Van Liedekerke: > On 10/5/07, Vincent Fleuranceau <vi...@bi...> wrote: > > > How do people for now force full > > > backups to occur only eg. Saturday evening? > > > > Hi, > > > > I backup my server with BackupPC every night. I perform a full backup on > > monday and > > incremental backups the other days. > > > > I disable automatic backups for this specific host with the following > > directive in > > the host's config file (which overrides the global conf): > > > > $Conf{FullPeriod} = -1; > > > > This way, BackupPC will never automaticaly start a backup job. > > > > Then, I tell BackupPC to start a full backup via a simple bash script run > > from the > > crontab: > > > > --- > > > > #!/bin/bash > > > > DAY=`date +"%u"` > > > > if [ $DAY -eq 1 ] ; then > > BACKUP_MODE=1 > > else > > BACKUP_MODE=0 > > fi > > > > sudo -u backuppc /usr/share/backuppc/bin/BackupPC_serverMesg backup > > <server_IP> > > <server_name> backuppc $BACKUP_MODE > > > > --- > > > > I'm not a bash guru and I know that BackupPC has been designed for > > automatic backup > > scheduling, but this has been working perfectly for me for more than 2 > > years now. > > > > Give it a try! > > > > -- Vincent > > This is indeed a nice workaround for one server, but for 50 servers this > defeats all usefulness of a backup product :-) I don't like having 50 > cronjobs for my backups ... > > Franky You only need to script a bit more for that... Why not just parse the backuppc hosts file for all backuphosts and use them as servername for the actual backup command calls in the script. So you will have that done automaticly and you only need to add new backup hosts like you are already used to. But to be honest, you don't need weekly full backups at all and having all full backups on the same day is even also not so clever, because full backups takes longer, so that less pc's can be handled on the "full backup day" by your backup machine. Having a full backup once a month is normaly absolutly good enough. All other days incrementel backups will do the rest. In theory you don't even need to make more then one full backup for a host ever. Because of the pooling the result on the backuppc machine is more or less the same anyways. The main difference is only that on full backups all files gets transfered again and on incremental backups just the changed ones. Ralph |
From: Holger P. <wb...@pa...> - 2007-10-11 00:45:38
|
Hi, Ralph Passgang wrote on 09.10.2007 at 21:41:28 [[BackupPC-devel] Fwd: Re: some small questions]: > Am Freitag, 5. Oktober 2007 10:52:04 schrieb Franky Van Liedekerke: > > On 10/5/07, Vincent Fleuranceau <vi...@bi...> wrote: > > > [...] > > > I disable automatic backups [... and ...] > > > tell BackupPC to start a full backup via a simple bash script run > > > from the crontab [...] > > > > This is indeed a nice workaround for one server, but for 50 servers this > > defeats all usefulness of a backup product :-) I don't like having 50 > > cronjobs for my backups ... > > You only need to script a bit more for that... > > Why not just parse the backuppc hosts file [...] well, yes, you *can* implement an alternative BackupPC scheduler outside BackupPC. > But to be honest, you don't need weekly full backups at all [...] > and having all full backups on the same day is even also not so clever In case you hadn't noticed, this is backuppc-devel. Which is why your statement > In theory you don't even need to make more then one full backup for a > host ever. Because of the pooling the result on the backuppc machine is > more or less the same anyways. The main difference is only that on full > backups all files gets transfered again and on incremental backups just > the changed ones. is plain wrong. Search the archives of backuppc-users to find out why. Regards, Holger |