Sending Orphaned Legacy BC jobs to tape

[mbd3]

Hi Guys - scenario is as follows. Looking to see if this is possible via workaround (Powershell, assistance from support etc.)

- VBR v12.3.1 (1139)
- There are approximately 30 backup files (vbk GFS yearly) as Legacy Backup Copy Files residing on a Catalyst (StoreOnce) repository.
- The files are orphaned (the jobs have been removed)
- There are no existing Legacy backup copy jobs.
- I have several years of backups from both the VBR server VM itself and the VBR server's configuration.

I would like to send only the orphaned files to tape to free up some repository capacity. There are approximately 1PB of other backup files on the repository which I would prefer to leave alone.

The challenge is:
- A new tape job can select only from existing jobs or "whole repository". I can not choose backups or deleted jobs.
- Catalyst cannot be used as a source for files-to-tape
- Move is not possible (legacy format), as discussed in this thread veeam-backup-replication-f2/veeamover-l ... 94200.html

An ideal situation would be if there was a means of creating a legacy BC job in v12.3, which I could clone and then re-map to the orphaned files, but to my knowledge this is not possible.

I believe my only two options would be:
1. Send the entire contents of the repository to tape (over 1PB), or
2. Manually restore the backup files I need from the orphaned files, back them up again using a new job, and send those new backups to tape.

I am looking to determine if there are any other options I have not considered, and/or whether there is a means of creating a legacy BC job in v12.3 which I can use for this process.

[david.domask]

Hi mbd3,

Do you have any other repository you can use to temporarily house the backups? Export Backup likely can help here, though depending on the size of the backups and your available extra space, you may need to do this in batches. (i.e., Export several backups to the staging repository, perform File to Tape for those backups, delete the backups and repeat with next batch for exporting)

[mbd3]

This is effectively the same as #2. Slightly different steps but logically the same. i.e. move the backups to a different disk location and then backup those backups.

[david.domask]

Correct, in essence it's similar but saves time on the restore operations and compute needed while the machines are running as well as not needing to create backup jobs for the restored VMs

Ultimately, either solution will work, but quickest way is probably Export Backup.