RMAN CopyJob

[FreddyN]

Hello There

A Customer would like to copy RMAN Backups for long term to S3.
The retention policy in the BackupCopyJob settings has only "days" no GFS at all. I can not realy set this to 700days

What do you guys think of this work-a-round:
- Dedicated repo for full db backup
- Adding this repo to a 'standard' Backup Copy job? (never used this option before)
- Setting GFS in the 'standard' Backup Copy job to something like 34d, 4w, 12m, 3y

Kind regards
Freddy

[PetrM]

Hi Freddy,

It will not work because plug-in backups must be processed by a dedicated job for application backups. However, you can specify a longer retention period in this job. We are planning to provide GFS retention for both primary and secondary backups in one of our future releases, most likely, GFS retention for primary backups will be available first.

Thanks!

[FreddyN]

Hi Petr

So I cannot handle the full backup like a file.... Not good

And what about placing the RMAN Backups on a VM with NFS-Share?
Its really important to bring these backups somehow on the S3 for long term retention.

/Freddy

[FreddyN]

Or should we create a VM with NFS to store the first backup and the backup this VM with GFS?

/Freddy

[PetrM]

Hi Freddy,

I believe that storing RMAN backups on an NFS share of a virtual machine and then further processing that VM with GFS is a good approach. In fact, I’ve just realized that I proposed the same idea in another thread on this topic some time ago. Also, I strongly recommend testing the restore scenarios in your environment to ensure there are no infrastructure-specific issues that could impact the restore process.

Another idea is to run an application backup copy job to a repository hosted on a VM, and then back up this VM with GFS.

Thanks!