Simple configuration. Disk backup. 30 volumes, 30 day retention,
Recycle automatically.
Pool {
Name = clients_Pool
Pool Type = Backup
Recycle = yes # Bacula can automatically
recycle Volumes
Recycle Oldest Volume = yes
AutoPrune = yes # Prune expired volumes
Volume Retention = 30 days # one year
Volume Use Duration = 24h
Accept Any Volume = yes # write on any volume in the
pool
LabelFormat = "clients-"
Maximum Volumes = 30
}
This is the message that concerns me:
Begin forwarded message:
> 11-Sep 11:05 backup0-sd: Job hostname.client.com.
> 2006-09-11_11.05.00 waiting. Cannot find any appendable volumes.
> Please use the "label" command to create a new Volume for:
> Storage: "Dev_clients" (/bacula/clients)
> Media type: File_clients
> Pool: clients_Pool
What is confusing is that there is a volume available it should be
writing to:
Pool: clients_Pool
+---------+--------------+-----------+----------------+----------
+--------------+---------+------+-----------+--------------
+---------------------+
| MediaId | VolumeName | VolStatus | VolBytes | VolFiles |
VolRetention | Recycle | Slot | InChanger | MediaType |
LastWritten |
+---------+--------------+-----------+----------------+----------
+--------------+---------+------+-----------+--------------
+---------------------+
| 1 | clients-0001 | Used | 9,418,659,725 | 2 |
2,592,000 | 1 | 0 | 0 | File_clients | 2006-09-07
22:21:46 |
| 2 | clients-0002 | Used | 10,270,194,708 | 2 |
2,592,000 | 1 | 0 | 0 | File_clients | 2006-09-08
22:25:46 |
| 3 | clients-0003 | Used | 10,301,616,376 | 2 |
2,592,000 | 1 | 0 | 0 | File_clients | 2006-09-09
22:23:12 |
| 4 | clients-0004 | Used | 12,072,651,723 | 2 |
2,592,000 | 1 | 0 | 0 | File_clients | 2006-09-10
23:26:29 |
| 5 | clients-0005 | Full | 4,779,329,250 | 1 |
2,592,000 | 1 | 0 | 0 | File_clients | 2006-08-17
22:19:18 |
clients-0004 was first used 10 hours ago, so it should be available...
APPARENT BUG: What is interesting is that it is complaining about
wanting a new volume exactly 24 hours *AFTER* it last tried to run,
and didn't find a new volume. (You can see that a we're a few days
ahead of 30 days, so I'm having to manually purge the volumes each
day until we catch up)
HOWEVER: I didn't purge the volume and release it for writing until
11pm last night.
ANALYSIS: So.. the volume's usage period is being determined not by
when it was first written to, but instead by the start time of the
first job that wrote to it.
Is this behavior known? Is it fixed in current? Obviously it's not
a crucial flaw, but if its decided not to fix it then it should be
documented.
--
Jo Rhett
senior geek
Silicon Valley Colocation
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
