-
- Expert
- Posts: 206
- Liked: 14 times
- Joined: Jul 23, 2013 9:14 am
- Full Name: Dazza
- Contact:
Protecting SQL VMs
Obviously, as some services like SQL become increasingly first class citizens with the infrastructure with higher I/O burdens, am I right to assume that generally everyone moves away from using Veeam? I say this because normally with a high importance and high I/O SQL platform you probably have tighter RPOs. If you do have tighter RPOs (perhaps 60 minutes), utilising Veeam replication means hourly stun, which is often an unacceptable side affect to be experiencing so often.
We want to remain a SQL Standard house if possible, we want OS maintenance capabilities and we don't want any re-pointing of apps should we have a site DR event (I know - a lot of want!!). I wonder how many of you also have higher end virtual SQL platforms and how you get the balance right?
I see that Zerto might be a nicer fit alongside a Windows MSCS cluster, but be interested to see what else you guys are doing.
Thanks
We want to remain a SQL Standard house if possible, we want OS maintenance capabilities and we don't want any re-pointing of apps should we have a site DR event (I know - a lot of want!!). I wonder how many of you also have higher end virtual SQL platforms and how you get the balance right?
I see that Zerto might be a nicer fit alongside a Windows MSCS cluster, but be interested to see what else you guys are doing.
Thanks
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Protecting SQL VMs
Hi Dazza,
Thanks!
I would say that most of the people move from using backup jobs on hourly basis to using SQL backup jobs, which have a separate RPO configuration.gingerdazza wrote:am I right to assume that generally everyone moves away from using Veeam?
Thanks!
-
- Expert
- Posts: 206
- Liked: 14 times
- Joined: Jul 23, 2013 9:14 am
- Full Name: Dazza
- Contact:
Re: Protecting SQL VMs
Hi Vitaliy
thanks for this information, but this continuous logs backup also uses hypervisor snapshots too doesn't it? This is the part that doesn't make sense to me, because it means you have a regular stun on the SQL server, no? Wouldn't people be better doing nightly VM backups alongside native SQL log shipping to avoid stun?
thanks for this information, but this continuous logs backup also uses hypervisor snapshots too doesn't it? This is the part that doesn't make sense to me, because it means you have a regular stun on the SQL server, no? Wouldn't people be better doing nightly VM backups alongside native SQL log shipping to avoid stun?
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Protecting SQL VMs
No, it doesn't. During sql backup job run VM snapshot is not taken, it is similar like doing logs backup via native tools, but on top of that we also provide SQL Explorer restore capabilities.gingerdazza wrote:but this continuous logs backup also uses hypervisor snapshots too doesn't it?
-
- Influencer
- Posts: 14
- Liked: 3 times
- Joined: Jul 09, 2010 7:39 pm
- Contact:
Re: Protecting SQL VMs
Very good info Vitaliy! Thank you. We are facing similar RPO/RTO requirements for our SQL databases. We also are implementing SQL 2014 Always On Availability Groups with 3 nodes each. 2 in the prod DC, 1 in the DR DC. Any tips on backing up Always On groups?
I did read this: http://helpcenter.veeam.com/backup/80/v ... pport.html
I did read this: http://helpcenter.veeam.com/backup/80/v ... pport.html
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Protecting SQL VMs
There is an existing topic about Always On groups backup as well, please check it out > Backing up Always On MSSQL with Veeam
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 21 guests