Hi All,
Support case: #07268037
We recently setup backup copy jobs that used a registry key as per the following post: veeam-backup-replication-f2/feature-req ... 70646.html
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Name: BackupCopyMirrorAll
Type: Multi-string value (REG_MULTI_SZ)
Data: Backup Copy job names you want to behave this way.
This has done as expected - copied all previous restore points.
My concern is that it has copied the first full and then listed all of the other restore points as incremental. The first full has the R flag, meaning short term retention, which is immutable until 4/6/24 (as are all the other restore points).
Why didn't the original retention flags get mirrored in the backup copy files? Are the copied restore points going to disappear?
Is there any way around this?
Thanks.
-
- Novice
- Posts: 6
- Liked: never
- Joined: Feb 20, 2017 4:42 am
- Contact:
-
- Veeam Software
- Posts: 2123
- Liked: 513 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Backup Copy Job - Copy all restore points
Hi xpose,
The registry value BackupCopyMirrorAll is working as expected here, and a bit further down in the thread you linked it's explained.
Backup Copy jobs are not "simple" file copies, but instead a "backup of a backup" -- that means the Backup Copy chain is not just copying the VBK/VIB from the source to target, but instead intelligently moving the data for the most recent restore point from the source backup to the backup copy backup. By default Backup Copy only works on the most recent restore point, and this registry value simply tells it to process all restore points instead during the Backup Copy.
May I ask, what is the intended goal? Are you wanting to have multiple copies of the Backup Copy or just periodically have an extra copy of the current chain for a one-off need? If it's a one-time event, consider Copy Backup as it will do what you're needing. If you want to have multiple copies to meet 3-2-1, consider multiple Backup Copy jobs; similarly, in the just released 12.1.2 update, you can now use Backup Copies as a source for other Backup Copies for specific workloads, so that may be an option also.
The registry value BackupCopyMirrorAll is working as expected here, and a bit further down in the thread you linked it's explained.
Backup Copy jobs are not "simple" file copies, but instead a "backup of a backup" -- that means the Backup Copy chain is not just copying the VBK/VIB from the source to target, but instead intelligently moving the data for the most recent restore point from the source backup to the backup copy backup. By default Backup Copy only works on the most recent restore point, and this registry value simply tells it to process all restore points instead during the Backup Copy.
May I ask, what is the intended goal? Are you wanting to have multiple copies of the Backup Copy or just periodically have an extra copy of the current chain for a one-off need? If it's a one-time event, consider Copy Backup as it will do what you're needing. If you want to have multiple copies to meet 3-2-1, consider multiple Backup Copy jobs; similarly, in the just released 12.1.2 update, you can now use Backup Copies as a source for other Backup Copies for specific workloads, so that may be an option also.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 27 guests