Scott Gamble writes: > I know this has been touched on repeatedly - and from kinda glossing through > the archives I gather that its not a new idea at all, but is there any > reason why scheduling of backups couldn't be handled exclusively by cron > instead of the backuppc mechanism? The time functionality on backuppc seems > to be woefully incomplete in comparison, and the idea of being able to > schedule backups by time instead of by number of backups is vastly more > applealing. I guess what I'm asking is by using cron to handle scheduling, > am I missing anything or preventing any kind of critical functions from > happening such as the linking and the house cleaning? Below is my proposed > crontab (yes I comment this much on my machines - this is a straight pull)
BackupPC is intended to scale easily with a large number of hosts, distribute the load, adapt to machines being on or off the network etc. If you want a fixed schedule then cron is a good choice. However, do not run BackupPC_dump directly. Instead, use BackupPC_serverMesg to tell BackupPC to run the backup. That way it can run BackupPC_link, make sure that it doesn't overlap BackupPC_nighty etc. Look in the archives for how to run BackupPC_serverMesg. Also, it is likely sufficient to just run the full backup via cron. BackupPC will do the incrementals daily after that. Craig ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
