Hello,
On 1/18/23 11:47, Yateen Shaligram Bhagat (Nokia) wrote:
Hi all,
We are using disk based Bacula backup up. (9.4.4)
We want to archive older backups into a separate archive pool (with a long
retention time) with no associated job record in the catalog.
We are doing it by migrating current backup job to an archive pool, then do a
job purging from the archive volume.
Further we need to relabel the new archive volume with a specific name like
archive_2022.
We tried it using the relabel command. (relabel oldvolume=xxx volume=yyy )
Observations:
1. In the catalog, it renames the old volume name to a new volume name ;
this is expected.
2. However, on the storage side, the old disk volume got truncated to 254
bytes, all the contents were lost .
Expectation was that on the storage side also the old volume will get renamed
to a new volume with no loss of data.
relabel means that you rewrite a label to a volume, so the content is lost. If
you want to rename a volume, I would suggest to take a different approach.
It's not in the Bacula's spirit to allow such operation (it might be difficult
to find back where is your data if you start to rename volumes).
You can still change the catalog Media table and move the physical file to
a new name for example.
Hope it helps!
Best Regards,
Eric
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
