Just wondering, are there any differences in Microsoft VSS performance between different versions of Windows or MSSQL?
For example, I am wondering if performance can be increased by simply upgrading to a newer version of a Microsoft product. Right now the Veeam application aware step is creating about a 5 second IO freeze on MSSQL databases as the server gets bigger and bigger and I am looking for ways to reduce this while continuing to use application aware technology. Disks are SSD.
Thanks in advance for any insights.
-
- Expert
- Posts: 192
- Liked: 9 times
- Joined: Dec 01, 2010 8:40 pm
- Full Name: Tom
- Contact:
-
- Veeam Software
- Posts: 3625
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Windows VSS performance between versions
Hi Tom,
I believe the question is worth asking on similar Microsoft Community Forums as any backup application just plays the role of VSS requestor and cannot affect performance of VSS framework.
Thanks!
I believe the question is worth asking on similar Microsoft Community Forums as any backup application just plays the role of VSS requestor and cannot affect performance of VSS framework.
Thanks!
-
- Expert
- Posts: 192
- Liked: 9 times
- Joined: Dec 01, 2010 8:40 pm
- Full Name: Tom
- Contact:
Re: Windows VSS performance between versions
Oh I agree with you, but I'm looking for a potential answer though from Veeam users experience.
-
- Expert
- Posts: 192
- Liked: 9 times
- Joined: Dec 01, 2010 8:40 pm
- Full Name: Tom
- Contact:
Re: Windows VSS performance between versions
I don't know if there is a way to request features or not, but you know what would be nice is for Veeam to have the ability to backup individual databases without backing up the entire server.
The reason for this would be VSS. With Veeam during a regular backup, during the application aware stage, it has to freeze IO for all databases which takes time because its single threaded and has to go through each database one by one to make it ready for backup, but if it could somehow just freeze the IO for a single database at a time, back it up, then go on to the next similar to how MSSQL handles database dumps, that would eliminate the issue of lengthy freezes. At least I think.
The reason for this would be VSS. With Veeam during a regular backup, during the application aware stage, it has to freeze IO for all databases which takes time because its single threaded and has to go through each database one by one to make it ready for backup, but if it could somehow just freeze the IO for a single database at a time, back it up, then go on to the next similar to how MSSQL handles database dumps, that would eliminate the issue of lengthy freezes. At least I think.
-
- Veeam Software
- Posts: 3625
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Windows VSS performance between versions
Your feedback is appreciated! Let's consider your post as +1 vote to have it in one of our future releases. Usually, we add features to our roadmap based on number of similar requests.
Thanks!
Thanks!
Who is online
Users browsing this forum: No registered users and 129 guests