Hey All, Hope you're doing well
I'm new in this forum and English is not my mother tongue so my excuses for the mistakes
I was wondering how I could process the move of my old backups to the new s3. To explain the situation I have my old backup copy on a Windows server-based repository and now I want to move to s3.
Upgrading from Veeam 11 to Veeam 12.1 made my old backup copy as "Legacy VMware backup copy" and I did not have the "move backup" option on the disks. Reading the forum I managed to convert the legacy backup copy to Veeam12 standard and in the process (the mapping process) I was told by Veeam that creating a new backup task and mapping the old backup from the repository would synthesize a full backup from the last restore point and continue backup incrementally and old backup chain will be detached, marked as orphaned and processed by the time-based retention policy.
I was thinking that after converting to the new standard I would have the "move option" but I only have it on the new disk of the task, not on the orphaned one. So I move the converted disks to an S3 repository will it manage (somehow) to include the old chain (old orphaned disk) or it will just move the new synthetized full and newer incremental?
And if so, what is the best solution to move all to s3 including the old chain (showing now as orphaned disks)?
For the record, I have other backup copy jobs in the old standard (legacy VMware backup copy) not been converted yet because I was trying on just one task and keeping it done before trying on others.
Thanks for all the responses and have a good day
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Mar 24, 2024 1:46 pm
- Full Name: Augustin DIDJEIRA
- Contact:
-
- Product Manager
- Posts: 9417
- Liked: 2504 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: ADVICE FOR migration to S3 object repository
Hello Augustin
Best,
Fabian
Backup chains from the "legacy periodic copy" format cannot "be moved" to any repository.what is the best solution to move all to s3 including the old chain (showing now as orphaned disks)?
Only the new backup chains attached to the backup job will be moved.So I move the converted disks to an S3 repository will it manage (somehow) to include the old chain (old orphaned disk) or it will just move the new synthetized full and newer incremental?
Is there a reason why you want to use direct backup or copy to object storage instead of a SOBR? A SOBR with capacity tier and Copy policy would allow you to have the legacy chain and upgraded chains on object storage.For the record, I have other backup copy jobs in the old standard (legacy VMware backup copy) not been converted yet because I was trying on just one task and keeping it done before trying on others.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Mar 24, 2024 1:46 pm
- Full Name: Augustin DIDJEIRA
- Contact:
Re: ADVICE FOR migration to S3 object repository
Backup chains from the "legacy periodic copy" format cannot "be moved" to any repository.
OK got it. only new V12 standard backup can be movedOnly the new backup chains attached to the backup job will be moved.
I'll look at it. Never heard before. And to explain a little more the situation the Windows server based repository is doomed to be deleted soon.Is there a reason why you want to use direct backup or copy to object storage instead of a SOBR? A SOBR with capacity tier and Copy policy would allow you to have the legacy chain and upgraded chains on object storage.
Who is online
Users browsing this forum: No registered users and 22 guests