From: Stephan W. <sw...@co...> - 2004-03-03 22:21:07
|
I noticed this before on occasion and never paid attention to it. But if you run a stat cmd from console it somehow seems to call and activate code which expires volumes and other date in the DB. This has been observed in 1.32f-3 and -4 I did not observe it in version 1.32a which I ran before the -3 version. Here is a snipped of the console action. I also noticed that on occasion running the stat command it would take some time to print out the detail, possibley due to the DB activity to clean up. I think running a stat command should not make changes to any database. Maybe it is just coincidence and the scheduler runs cleanups all along -sww *me You have no messages. *stat Status available for: 1: Director 2: Storage 3: Client 4: All 1elect daemon type for status (1-4): backup-dir Version: 1.32f-4 (24 Jan 2004) i686-pc-linux-gnu redhat 8.0 Daemon started 03-Mar-04 09:05, 0 Jobs run. Scheduled Jobs: Level Type Scheduled Name Volume =============================================================================== Incremental Backup 04-Mar-04 01:30 jon-fd PVol0014 Incremental Backup 04-Mar-04 01:30 cvs-job Vol0002 Incremental Backup 04-Mar-04 01:30 gnats-job Vol0002 Incremental Backup 04-Mar-04 01:30 home-job IVol0011 Incremental Backup 04-Mar-04 01:30 user-job IVol0011 Incremental Backup 04-Mar-04 01:30 doc-job Vol0002 Full Backup 04-Mar-04 01:10 BackupCatalog Vol0002 No Running Jobs. No Terminated Jobs. ==== You have messages. *mes 03-Mar-2004 14:08 backup-dir: Max configured use duration exceeded. Marking Volume "IVol0010" as Used. 03-Mar-2004 14:08 backup-dir: Pruned 1 Job on Volume IVol0014 from catalog. 03-Mar-2004 14:08 backup-dir: Pruned 1 Job on Volume IVol0015 from catalog. 03-Mar-2004 14:08 backup-dir: Pruned 1 Job on Volume IVol0016 from catalog. 03-Mar-2004 14:08 backup-dir: Recycled volume "IVol0011" |