Hello community
I would like to create secondary backups to alternating shares, i.e. two SMB shares on a USB-connected NAS.
Either one of the SMB-shares is available at any given time and should be used as backup target.
As I understand, the repository option "backed by rotated drives" does not apply in this scenario.
Right now I have created two identical (except 'target') backup copy jobs to each of the SMB-shares.
I haven't completed the backups jobs towards these repositories, but I expect to get Failure reports whenever any one of the shares is not available.
Is there any way to avoid this?
Thanks a lot, Sebastian
-
- Novice
- Posts: 4
- Liked: never
- Joined: Mar 29, 2022 6:50 am
- Full Name: Sebastian Bartel
- Contact:
-
- Veeam Software
- Posts: 2838
- Liked: 650 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Backup Copy to alternating shares
Hi Sebastian,
I moved your topic to the Veeam Backup and Replication general forum as it's mostly just about Backup Copy behavior.
With the two jobs, I think the simplest solution is just to disable the job when it's not in use to avoid the failure messages.
You are correct, with how the Rotated Drive detection works, unless the SMB share was mapped to a drive letter, it wouldn't work. While this is feasible, please note that there are quite a few nuances to mapping network drives, so I'm not sure it's the best solution here. However, can the server for the SMB share present the same share as an iscsi target? That would work with rotated drives.
I can imagine some other solutions with Scale-out Backup Repositories and putting the extents into maintenance mode, but this seems overly complex and prone to manual error, or would require a pre-job script to set maintenance mode appropriately.
I moved your topic to the Veeam Backup and Replication general forum as it's mostly just about Backup Copy behavior.
With the two jobs, I think the simplest solution is just to disable the job when it's not in use to avoid the failure messages.
You are correct, with how the Rotated Drive detection works, unless the SMB share was mapped to a drive letter, it wouldn't work. While this is feasible, please note that there are quite a few nuances to mapping network drives, so I'm not sure it's the best solution here. However, can the server for the SMB share present the same share as an iscsi target? That would work with rotated drives.
I can imagine some other solutions with Scale-out Backup Repositories and putting the extents into maintenance mode, but this seems overly complex and prone to manual error, or would require a pre-job script to set maintenance mode appropriately.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Amazon [Bot] and 18 guests