Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
pcts
Service Provider
Posts: 6
Liked: 3 times
Joined: Nov 15, 2017 6:16 pm
Contact:

Advice for SQL Space Requirements #02386460

Post by pcts » Nov 16, 2017 8:39 pm

Hi all

Having a issue for first time backup of SQL VM which sits on SAN connected to two hyper v hosts in a cluster. Getting a backup error that says insufficient free disk space on production drive c:\clusterstorage\volume4

This is a sql cluster quorum volume only. It is 1.9GB total size with 780MB free.

See Error: https://imgur.com/nGehhf1
Looking for ideas as to what size the volume(s) should be or what free space should they be.

Thanks in advance
PCTS

(Support ID #02386460)

DeadEyedJacks
Veeam ProPartner
Posts: 136
Liked: 23 times
Joined: Oct 12, 2015 2:55 pm
Full Name: DeadEyedJacks
Location: UK
Contact:

Re: Advice for SQL Space Requirements #02386460

Post by DeadEyedJacks » Nov 20, 2017 4:21 pm

Microsoft VSS requirements
For volumes less than 500 megabytes, the minimum is 50 megabytes of free space.
For volumes more than 500 megabytes, the minimum is 320 megabytes of free space.
It is recommended that at least 1 gigabyte of free disk space on each volume if the volume size is more than 1 gigabyte.”

Sounds like you need to comply with the Microsoft recommendation of at least 1GB free space on all volumes for VSS to work

jmmarton
Veeam Software
Posts: 1592
Liked: 208 times
Joined: Nov 17, 2015 2:38 am
Full Name: Joe Marton
Location: Chicago, IL
Contact:

Re: Advice for SQL Space Requirements #02386460

Post by jmmarton » Nov 21, 2017 2:17 pm

It's also possible to redirect shadow copies to another volume with more space.

https://www.veeam.com/kb1794

Joe

pcts
Service Provider
Posts: 6
Liked: 3 times
Joined: Nov 15, 2017 6:16 pm
Contact:

Re: Advice for SQL Space Requirements #02386460

Post by pcts » Nov 23, 2017 9:32 am 1 person likes this post

Hi DeadEyeJacks and jmmarton

Thanks for your insight and guidance. I have increased the size of the quorum drive by 1GB and Veeam is no longer reporting an issue. This resolved the issue.

Thanks again
PCTS.

Post Reply

Who is online

Users browsing this forum: Majestic-12 [Bot] and 3 guests