Hi all. Maybe this is normal bacula behavior but it is causing me problems.
Say I have a large job to run (~28 hrs). I schedule the job to be run daily. Now, if there is not a suitable full backup already written (ie. the full backup is the current running job), the scheduled job happily checks and sees that there is not a full backup. Say the job gets scheduled twice before the first full backup completes. Now it will run through two more identical full backups filling my tapes until the whole pool is full. Shouldn't the scheduled jobs wait to check for a prior backup until the actual moment it is going to run, instead of two days before it will actually run (yes my backup takes days, a problem caused by data disorganization and a lack of proper archiving for the past 20 years). This doesn't really pose a huge problem though since it only happens when a job is scheduled while the full backup is being created. Thanks Nick ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
