I have an infrastructure today that uses veeam 11 with continuous schedule replication but no cdp. This infrastructure is managed by a 24/24 service provider.
The customer wants to add backup to this infrastructure, but the service provider doesn't want to manage it with his veeam.
The customer has a second architecture with Veeam 12.
Won't I have a CBT problem if I put both veeams on the same source vm? The service provider is willing to put a pause in its replication to let the backup through, so as not to have both at the same time.
I've seen a lot of discussion on the forum, but is there a kb somewhere that clearly states the subject?
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 02, 2009 12:23 pm
- Full Name: LE COQ MANUEL
- Location: Bretagne
- Contact:
-
- Veeam Software
- Posts: 2110
- Liked: 509 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Use two architecture veeam with one source VM
Hi petitbleu,
When any backup application utilizes CBT, CBT gives a change ID after the backup operation is completed. (same with snapshot based replication)
The ChangeID is then presented to VMware during the next backup session, and all changed blocks since that ID are returned, and the process repeats.
In your scenario, this means a few things:
1. By default, Veeam resets CBT on Active Fulls, though this can be disabled.
2. There must be no snapshots when enabling CBT, else it won't be usable until the snapshots are cleared and CBT is reset
How continuous is continuous for the replication? The main concern I would have is multiple snapshots at the same time, if only for the extra pressure on the VMware environment and the resultant performance impacts. While it can work as you're hoping, it might be easier to go with Agent backups in this scenario, as the restore narrative is very similar to snapshot based backups, or just revisit managing both with the same Veeam server, as the scheduler will ensure that the jobs don't have overlapping snapshots.
(p.s. - Probably you're aware, but Veeam v11 is already at the End of Support phase, so consider upgrading)
When any backup application utilizes CBT, CBT gives a change ID after the backup operation is completed. (same with snapshot based replication)
The ChangeID is then presented to VMware during the next backup session, and all changed blocks since that ID are returned, and the process repeats.
In your scenario, this means a few things:
1. By default, Veeam resets CBT on Active Fulls, though this can be disabled.
2. There must be no snapshots when enabling CBT, else it won't be usable until the snapshots are cleared and CBT is reset
How continuous is continuous for the replication? The main concern I would have is multiple snapshots at the same time, if only for the extra pressure on the VMware environment and the resultant performance impacts. While it can work as you're hoping, it might be easier to go with Agent backups in this scenario, as the restore narrative is very similar to snapshot based backups, or just revisit managing both with the same Veeam server, as the scheduler will ensure that the jobs don't have overlapping snapshots.
(p.s. - Probably you're aware, but Veeam v11 is already at the End of Support phase, so consider upgrading)
David Domask | Product Management: Principal Analyst
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 02, 2009 12:23 pm
- Full Name: LE COQ MANUEL
- Location: Bretagne
- Contact:
Re: Use two architecture veeam with one source VM
Thanks i choose the solution with agent.
Who is online
Users browsing this forum: Bing [Bot] and 2 guests