-
- Novice
- Posts: 5
- Liked: never
- Joined: Jan 28, 2025 1:15 pm
- Contact:
Case # 07579837
Hi,
I would like to perform backups on 2 different Synology NAS devices located at different sites (offices), alternating the jobs weekly between them.
Currently, I rotate the NAS devices with a scheduled Windows task.
I have as many jobs as I need, duplicated for each NAS.
I would like to achieve this with a single job, without duplicating jobs for each NAS.
How can this be done?
I would like to perform backups on 2 different Synology NAS devices located at different sites (offices), alternating the jobs weekly between them.
Currently, I rotate the NAS devices with a scheduled Windows task.
I have as many jobs as I need, duplicated for each NAS.
I would like to achieve this with a single job, without duplicating jobs for each NAS.
How can this be done?
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jan 28, 2025 1:15 pm
- Contact:
Re: Case # 07579837
The described jobs are of the following types: VMware Backup, File Backup, and Backup Copy.
-
- Veeam Software
- Posts: 2744
- Liked: 630 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Case # 07579837
Hi ticSer,
Just to confirm, the goal is to have a single job with all of your VMware Backups, and ensure that on Week 1 the job writes to NAS A, and on Week 2 the job writes to NAS B?
Can I ask why this particular model was chosen? Backup Copies I think are much more suitable for this and accomplish the same goal, but without the extra scripting layer to have to consider.
Backup copies are "backups of backups", stand-alone backup chains with their own retention, but the source of the data is your existing backups, meaning you will have the data duplicated in multiple locations to satisfy 3-2-1, and there are no extra steps required for recovery, simply proceed as you normally would.
I'm not sure I'm understanding the benefits gained from the proposed approach, but maybe you can explain your use case a bit more.
Just to confirm, the goal is to have a single job with all of your VMware Backups, and ensure that on Week 1 the job writes to NAS A, and on Week 2 the job writes to NAS B?
Can I ask why this particular model was chosen? Backup Copies I think are much more suitable for this and accomplish the same goal, but without the extra scripting layer to have to consider.
Backup copies are "backups of backups", stand-alone backup chains with their own retention, but the source of the data is your existing backups, meaning you will have the data duplicated in multiple locations to satisfy 3-2-1, and there are no extra steps required for recovery, simply proceed as you normally would.
I'm not sure I'm understanding the benefits gained from the proposed approach, but maybe you can explain your use case a bit more.
David Domask | Product Management: Principal Analyst
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jan 28, 2025 1:15 pm
- Contact:
Re: Case # 07579837
Hi,
My scenario is as follows, and I'm not sure if I'm structuring the process correctly:
NAS 1 in Site A
NAS 2 in Site B
Week 1: Backups (jobs) are performed on NAS 1, including:
VMware Backup (3 jobs)
Windows Agent Backup (1 job)
File Backup (2 jobs)
I rotate the jobs using a Windows scheduled task, enabling or disabling jobs as needed.
Week 2: Backups (jobs) are performed on NAS 2, including:
VMware Backup (3 jobs)
Windows Agent Backup (1 job)
File Backup (2 jobs)
Currently, with this setup, I have 6 jobs for NAS 1 and 6 jobs for NAS 2.
That's why I suggested the configuration described above—to simplify everything into one job per backup type instead of duplicating jobs for each NAS.
My scenario is as follows, and I'm not sure if I'm structuring the process correctly:
NAS 1 in Site A
NAS 2 in Site B
Week 1: Backups (jobs) are performed on NAS 1, including:
VMware Backup (3 jobs)
Windows Agent Backup (1 job)
File Backup (2 jobs)
I rotate the jobs using a Windows scheduled task, enabling or disabling jobs as needed.
Week 2: Backups (jobs) are performed on NAS 2, including:
VMware Backup (3 jobs)
Windows Agent Backup (1 job)
File Backup (2 jobs)
Currently, with this setup, I have 6 jobs for NAS 1 and 6 jobs for NAS 2.
That's why I suggested the configuration described above—to simplify everything into one job per backup type instead of duplicating jobs for each NAS.
-
- Veeam Software
- Posts: 2744
- Liked: 630 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Case # 07579837
Got it, understood on the configuration, but I guess if it were me, I would just pick one NAS to be the primary one and the other secondary -- I would send the 6 Jobs to primary NAS, then create a backup copy job for the VMware and Agent backups as well as set secondary targets on the File Backup jobs, both pointing to the secondary NAS.
Far less jobs to manage, and you get the same end result without having to do the switching between both NAS devices.
Similarly, if you prefer the rotation approach, I think review our Rotated Drive section of the User guide, as Veeam supports a repository backed by rotated storage. There is an important limitation with rotated drives in that you cannot store GFS points there, but otherwise I think it could work.
Basically, I'm not against the idea of scripting like you have been, but I think it's just a lot easier to use one of the options mentioned above. Less to keep track of.
Far less jobs to manage, and you get the same end result without having to do the switching between both NAS devices.
Similarly, if you prefer the rotation approach, I think review our Rotated Drive section of the User guide, as Veeam supports a repository backed by rotated storage. There is an important limitation with rotated drives in that you cannot store GFS points there, but otherwise I think it could work.
Basically, I'm not against the idea of scripting like you have been, but I think it's just a lot easier to use one of the options mentioned above. Less to keep track of.
David Domask | Product Management: Principal Analyst
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jan 28, 2025 1:15 pm
- Contact:
Re: Case # 07579837
I understand
But by setting one NAS as the primary and the other as the secondary, wouldn't they contain the same information (data) on both?
The idea is to have the data on one NAS for one week and on the other NAS for the next week,
so that if one NAS fails, we have a backup on the other.
Or is your described configuration better?
thx
But by setting one NAS as the primary and the other as the secondary, wouldn't they contain the same information (data) on both?
The idea is to have the data on one NAS for one week and on the other NAS for the next week,
so that if one NAS fails, we have a backup on the other.
Or is your described configuration better?
thx
-
- Veeam Software
- Posts: 2744
- Liked: 630 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Case # 07579837
Well, depends on your preference, but my take is that the rotated model is nice, but means you have gaps. Let's say the NAS usage is determined by even and odd weeks of the year. The NAS holding backups for odd weeks breaks, and you need to recover a server back to 1st week of January as it's last known good state of the server. In the rotated model, you're out of luck as the surviving NAS doesn't have backups from odd weeks.
You're duplicating data no matter which method you use, which is the point of 3-2-1 rule. In my mind, rotated drives result in potentially critical gaps in your backup coverage unless you're doing further copies, but depending on your use case that might not be an issue.
You're duplicating data no matter which method you use, which is the point of 3-2-1 rule. In my mind, rotated drives result in potentially critical gaps in your backup coverage unless you're doing further copies, but depending on your use case that might not be an issue.
David Domask | Product Management: Principal Analyst
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jan 28, 2025 1:15 pm
- Contact:
Re: Case # 07579837
Thanks for everything
I will use "Backup" to replicate the jobs from NAS1 to NAS2
I will use "Backup" to replicate the jobs from NAS1 to NAS2
Who is online
Users browsing this forum: No registered users and 1 guest