-
- Enthusiast
- Posts: 38
- Liked: 2 times
- Joined: Nov 07, 2014 3:51 pm
- Full Name: Miles Lott
- Contact:
Exchange 2013 DAG support
We have a 5 server DAG with 4 databases live on each of 3 hosts. The remaining 2 servers are passive in our DR location.
I just wanted to make sure that this configuration will work. My plan is to backup the 3 servers with active databases. Worst case, that should give us 3 copies of each database per cumulative backup. I have already asked tech support and this was their recommendation. Is anyone actually doing this who can comment on the results?
I just wanted to make sure that this configuration will work. My plan is to backup the 3 servers with active databases. Worst case, that should give us 3 copies of each database per cumulative backup. I have already asked tech support and this was their recommendation. Is anyone actually doing this who can comment on the results?
-
- Enthusiast
- Posts: 38
- Liked: 2 times
- Joined: Nov 07, 2014 3:51 pm
- Full Name: Miles Lott
- Contact:
Re: Exchange 2013 DAG support
FYI, the target repo is Veeam B&R. So far this is working great for SQL and SharePoint.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Exchange 2013 DAG support
Hi Miles,
The problem with this kind of setup is the log handling... Only one backup is allowed to purge the logs... So if you are going to do this, you need to make sure that VEB is purging the logs on the node that actually is responsible for it, and that it doesn't do that on the other nodes. You can do that with the following procedure:
1. run regedit
2. go to HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Endpoint Backup
3. create DWORD value VSSForceCopyOnly = 1
4. re-start Veeam EndPoint Backup service
That being said... VAW 2 (the new name for VEB) server edition is going to fully support a single protection node scenario on a passive node. I frankly always propose to protect the passive node because it is not operational and does not affect server performance. This is actually what most people recommend.
My 2 cents
The problem with this kind of setup is the log handling... Only one backup is allowed to purge the logs... So if you are going to do this, you need to make sure that VEB is purging the logs on the node that actually is responsible for it, and that it doesn't do that on the other nodes. You can do that with the following procedure:
1. run regedit
2. go to HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Endpoint Backup
3. create DWORD value VSSForceCopyOnly = 1
4. re-start Veeam EndPoint Backup service
That being said... VAW 2 (the new name for VEB) server edition is going to fully support a single protection node scenario on a passive node. I frankly always propose to protect the passive node because it is not operational and does not affect server performance. This is actually what most people recommend.
My 2 cents
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Exchange 2013 DAG support
Hi Miles,
May I ask how this DAG is configured? Thanks!
May I ask how this DAG is configured? Thanks!
-
- Enthusiast
- Posts: 38
- Liked: 2 times
- Joined: Nov 07, 2014 3:51 pm
- Full Name: Miles Lott
- Contact:
Re: Exchange 2013 DAG support
Mike, that would be difficult. Three servers have four active databases each. All five servers have a copy of the twelve databases. So, setting that registry key on any one server would prevent log truncation there. Since it is global we cannot select which databases are handled or not handled.
I suppose I should wait for a more advanced backup client. We're trying to get away from DPM asap, although the Exchange backups with DPM have been mostly working for a couple of years.
I suppose I should wait for a more advanced backup client. We're trying to get away from DPM asap, although the Exchange backups with DPM have been mostly working for a couple of years.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Exchange 2013 DAG support
Miles,
Understood. I hope that we have a VAW 2 beta soon so you can test it out
Thanks
Mike
Understood. I hope that we have a VAW 2 beta soon so you can test it out
Thanks
Mike
-
- Enthusiast
- Posts: 38
- Liked: 2 times
- Joined: Nov 07, 2014 3:51 pm
- Full Name: Miles Lott
- Contact:
Re: Exchange 2013 DAG support
I could backup one of the passive nodes, if that works with the registry key set. Then I would have to find a way to handle log truncation on the active servers, if that makes sense.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Exchange 2013 DAG support
Miles,
The registry key will make sure that the logs are not being truncated. So that would work but you would indeed need to find a way to handle log truncation.
The registry key will make sure that the logs are not being truncated. So that would work but you would indeed need to find a way to handle log truncation.
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Exchange 2013 DAG support
Miles,
Thanks for the clarifications. If you have all the databases copied between all the nodes, why do you want to backup every node separately? I’d rather install VEB on a single passive node, perform transaction log backup if required and that’s it.
Thanks for the clarifications. If you have all the databases copied between all the nodes, why do you want to backup every node separately? I’d rather install VEB on a single passive node, perform transaction log backup if required and that’s it.
-
- Influencer
- Posts: 13
- Liked: 2 times
- Joined: Apr 28, 2016 4:29 pm
- Full Name: Richard Jaworski
- Contact:
Re: Exchange 2013 DAG support
Thank you Gentlemen for these valuable comments!!!
-
- Enthusiast
- Posts: 26
- Liked: 11 times
- Joined: May 01, 2014 9:48 am
- Full Name: marc.rousseau
- Contact:
Re: Exchange 2013 DAG support
Hello,
I would like to know if backup of Exchange 2013 DAG and Exchange 2016 DAG are officially supported now by VAW 2 ?
Is there some limitations ? Is there some best practices to follow (timeouts, regkey to change, prefer to backup a single passive node,...) ? I found nothing really relevant in veeam official documentation,release notes, what's new...
Thanks
Marc
I would like to know if backup of Exchange 2013 DAG and Exchange 2016 DAG are officially supported now by VAW 2 ?
Is there some limitations ? Is there some best practices to follow (timeouts, regkey to change, prefer to backup a single passive node,...) ? I found nothing really relevant in veeam official documentation,release notes, what's new...
Thanks
Marc
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 15 guests