Hello, I developed a patch for my personal use and it has been working successfully for more than a year. It has the purpose of restricting the schedule of a backup to a definite time window and breaks up the default logic of starting a backup as soon as a computer is on the network.
I attached a tarball to this email. Inside the tarball there are a patch file for BackupPC 3.1.0 and another patch file for BackupPC 3.0.0. Their names are: RecurringBackups-3.1.0-v1.patch RecurringBackups-3.0.0-v1.patch Installing the patch is simple: backup your configuration files; unpack the sources of BackupPC; change current directory to the unpacked sources; execute "patch -p0 -b < /path/to/the/patch"; stop backuppc; execure "perl configure.pl" and proceed as you would for a product upgrade. start backuppc; configure the new feature. You shoud configure WeeklyBackups, DailyBackups, WakeupSchedule, BlackoutPeriods, FullPeriod, FullKeepCount, IncrPeriod, IncrKeepCnt as a minimum. Instructions are given inside the config.pl file, however, I shall add some notes I derived from my experience. - In the patch documentation I suggest using blackout periods along with recurring backups. Nowadays I never use blackout periods anymore, it is simpler to have recurring backups scheduled explicitly, in fact I am used to remove all BlackoutPeriods from my configuration files. - I noticed that the first time I add a new host to my backup server, its backup starts at the first WakeupShedule occurrence even if the occurrence is outside of all configured time windows. I consider this a minor bug and I have not investigated it as I am used to manually start a full backup of any newly added hosts. - I noticed that all my backups run twice when my servers leave DST time and enter non-DST time. I have not investigated this bug as I consider it a minor flaw. It happens that once in a year I execute two backups instead of one for all my hosts. Not so dangerous. - Care must be taken when scheduling nightly backup jobs as they can overlap the "non-DST to DST" time frame. Once in a year you risk that your backup jobs will not be executed if you schedule them to occur in the same time window adopted for "non-DST to DST" transition. For example, once in a year the time window between 02:00 and 03:00 does not occur for servers in CET time zone when the transition to CEST occurs. Usually I adopt a time window which includes the transition window, for example: 01:00 to 06:00. - You can run many backups per day without recurring to any cron jobs. - The web configuration is supported, you are not required to manually edit any configuration files, look at the "Schedule" section. I hope my experience will be helpful. Any suggestions are welcome. Alberto Marconi Scrive Sebastian Perkins <[EMAIL PROTECTED]>: > Hello, > > BackupPC is up & running for 6 months. > > One problem remains : backuppc's full/incr solution launches a full save > after a certain number of days. Unfortunately this happens most of the time > during office hours. > > The consequence is that certain servers are heavily loaded and users > complain... > > Is there any to force the full on weekends ? And just keep the incr on week > days ? > > Thanks in advance, > > > > > Sebastian Perkins > >
RecurringBackups-v1.tar.gz
Description: application/gzip-compressed
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
