|
From: Hugo L. <hug...@gm...> - 2012-06-15 13:33:00
|
2012/6/15 Hugo Letemplier <hug...@gm...>: > 2012/6/15 Uwe Schuerkamp <uwe...@ni...>: >> >> On Thu, Jun 14, 2012 at 11:25:03PM +0200, Yougo wrote: >> >>> Is it possible to check a free space ratio on the storage daemon, >>> fail a job if required instead of failing also the volumes, waiting >>> for a mount… and thus avoid a lot of successive error that could >>> cause miscomprehension for the operator. Else have you got a >>> solution to avoid my issue. I will have more space in few weeks but >>> my backups are also being much larger due to enterprise expansion. >> >> For the moment I think your best bet would be a RunBeforeJob script >> that checks the free space on the filesystem, retrieves the size of >> the last full backup for the client being backed up and then does some >> comparisons based on these parameters. >> >> If the question is allowed: Why do you have so many pools defined? I >> usually only have my incremental an full pools, but of course once the >> PHBs start bugging you with different backup "classes" and >> "strategies", that's the first thing that usually goes out of the >> window. >> >> All the best, Uwe >> >> > I have different classes of jobs because I have about 4 different > kind of backup > I split data from the system backup ( I need b, so we had 6 pools also > I have an old mail system based on big database files that need to be > kept for a shorter time Sorry my mail was sent before I finished writing :-( Also I have got different kind of content that should be kept for a very long time. To finish I have an Archive pool that stores job copies on LTO Tapes |