Nice work, thanks for sharing!
Maybe a word or two on preventing this situation in the first place
might be helpful, like restricting volume sizes & number?
Also, you could consider documenting deleting a volume from a disk
pool (update pool from resource and so on) once the reader has cleaned
up the current mess ;-)
All the best, Uwe
Hi Uwe and John,
Thanks for the suggestions. I"ve added most of them except for the second from from Uwe about dleting a volume.
I already have details for deleting a volume, but I think I'm mis understanding what you mean by updating the pool afterwards.
Or do you mean that if you RM a volume before calling delete that you have to then do an update pool?
Jeff.
|
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
