On 07/09/2014 19:52, Gary Dale wrote: > Not a big deal, but somehow I've ended up with a file storage volume > that has a different naming convention from others in the pool. The > naming convention was "daily-backup-" + a single-digit volume number. > The amount of data keeps growing so I need to add new volumes from time > to time. Somehow the last time I ended up with one with the wrong name. > > I don't actually need to rename it. Migrating to another volume in the > same pool would also work, as would telling bacula to stop using it for > new backups, so that it would eventually be empty.
For tapes, it used to be possible to rename them by manually writing a label to them (btape label) and then mangling the SQL database to fit that (don't forget to restart everything afterwards) but even there, doing a rename of a volume carrying data wouldn't have worked (needed to be empty to be sure). Your best bet is probably to empty the volume and just delete/recreate it. - Michel ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
