Using object storage as a backup target
Post Reply
asifganai
Influencer
Posts: 20
Liked: never
Joined: Dec 11, 2017 6:32 am
Full Name: Asif Ganai
Contact:

Backup Copy to Glacier

Post by asifganai »

Hi,
We have around 200TB of data captured via backup copy jobs. We need to decommission the underlying backup copy repository and migrate this data(200TB) to Glacier. Please let me know if it is possible and how.
Note that the backup copy jobs are not active and were stopped around 6 months ago.
Regards
Asif Ali

Mildur
Veeam Software
Posts: 4862
Liked: 1459 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Backup Copy to Glacier

Post by Mildur » 1 person likes this post

Hi Asif

You need to create a SOBR with a capacity tier and archive tier to move the backups to AWS Glacier.
Only GFS Restore Points can be moved.
Direct Move to Glacier is not possible with Veeam.

Thanks
Fabian
Product Management Analyst @ Veeam Software

asifganai
Influencer
Posts: 20
Liked: never
Joined: Dec 11, 2017 6:32 am
Full Name: Asif Ganai
Contact:

Re: Backup Copy to Glacier

Post by asifganai »

Hi Fabian,
Thank you for your response.
Does that mean the backup copy jobs must be active and data must go to capacity tier before landing in the archive tier.
I am assuming GFS can't be applied to the jobs not working since 6 months or so.
Regards
Asif Ali

Mildur
Veeam Software
Posts: 4862
Liked: 1459 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Backup Copy to Glacier

Post by Mildur »

Hi Asif
I am assuming GFS can't be applied to the jobs not working since 6 months or so.
Correct, the job must already be marked as GFS recovery points. It is not possible to do this after the RP's have been created.
But you can export backup files manually for each month. Exported backups can also be offloaded to the archive tier.
Does that mean the backup copy jobs must be active and data must go to capacity tier before landing in the archive tier
Your Backup Copy Jobs doesn't have to be active. The SOBR will move the restore points first to capacity tier (Move Policy) and then to the archive tier. If you have deleted the backup copy jobs or removed the old machines from a copy job, restore points should be visible as orphaned backups. Orphaned GFS backup files can also be offloaded to the capacity tier and archive tier.
Imported backups can not be offloaded to archive tier.

If you create a SOBR with the existing repository as the performance tier, offload will happen for all backup and backup copy jobs targeted to this SOBR. Not just from a single backup copy job.
Product Management Analyst @ Veeam Software

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests