VSS on host & VM
We have a 2012 server.
Since a fe wdays we have a problem that everyday around twelve the system can't be reached. LAter on it can.
I saw that on that time VSS dit his thing. I changed the time to 06.00 and 19.00 and today there was no problem. So it seems to have to do with VSS. There were also errors in the event viewer concerning VSS.
I investigated further and saw that the VM host and the VM both had VSS enabled and even on the same time.
Can anyone tell me if this could be the problem ?
I changed the settings, but like to know more about it.
Should anyone do both VSS on VM host and VM ?
Like to hear from you.
Thanks,
Ben.
Since a fe wdays we have a problem that everyday around twelve the system can't be reached. LAter on it can.
I saw that on that time VSS dit his thing. I changed the time to 06.00 and 19.00 and today there was no problem. So it seems to have to do with VSS. There were also errors in the event viewer concerning VSS.
I investigated further and saw that the VM host and the VM both had VSS enabled and even on the same time.
Can anyone tell me if this could be the problem ?
I changed the settings, but like to know more about it.
Should anyone do both VSS on VM host and VM ?
Like to hear from you.
Thanks,
Ben.
ryan_johnston
Are there any errors in the event logs related to VSS? Also, if you run vssadmin /listwriters are any of them in "Failed" state?
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for BMConsultancy's comment #a39313632
for the following reason:
I didn't hear anything anymore.
Accepted answer: 0 points for BMConsultancy's comment #a39313632
for the following reason:
I didn't hear anything anymore.
"I guess and agree that ; VSS on the host is probably not advisable. It might hold up the host enough for it to become unavailable.
So'Il take that to be the solution. "
So'Il take that to be the solution. "
Hardware might be insufficient or VSS settings to broad (aka to much set to store as shadow). What are current VSS settings?
The reason for not recommending VSS on a VM Host is that VM might be large and the VSS function might not be able to ever kick in or "capture" the proper files.
The reason for not recommending VSS on a VM Host is that VM might be large and the VSS function might not be able to ever kick in or "capture" the proper files.
ASKER
Being on a holiday and having KPN as my provider the problems started ...
Dutch customers in France didn't have internet, Phone, sms, and so on for about a week.
So I was cut of from the electronic highway.
That's why there was a big silence.
The reason for not recommending VSS on a VM Host is that VM might be large and the VSS function might not be able to ever kick in or "capture" the proper files.
Gives me enough info to understand what could be the problem,so I like to see that as the solution.
Thanks and sorry for the late response.
Ben.
Dutch customers in France didn't have internet, Phone, sms, and so on for about a week.
So I was cut of from the electronic highway.
That's why there was a big silence.
The reason for not recommending VSS on a VM Host is that VM might be large and the VSS function might not be able to ever kick in or "capture" the proper files.
Gives me enough info to understand what could be the problem,so I like to see that as the solution.
Thanks and sorry for the late response.
Ben.
Sure, it's a common problem. Check this other article:
https://www.experts-exchange.com/questions/27379889/Volume-Shadow-Copy-High-CPU-Usage-Windows-Server-2008-R2.html
VSS can be very CPU and disk intensive. Intensive enough to drop users and make the whole host and guest VMs unavailable. If you also have many snapshots saved it will take longer and will take up even more time. Taken to the extreme... well you are probably there right now.
You had the host and the vm guest take vss snapshots and that is very demanding specially if vm files are large and both host and guest vss snapshots occur at the same time...
https://www.experts-exchange.com/questions/27379889/Volume-Shadow-Copy-High-CPU-Usage-Windows-Server-2008-R2.html
VSS can be very CPU and disk intensive. Intensive enough to drop users and make the whole host and guest VMs unavailable. If you also have many snapshots saved it will take longer and will take up even more time. Taken to the extreme... well you are probably there right now.
You had the host and the vm guest take vss snapshots and that is very demanding specially if vm files are large and both host and guest vss snapshots occur at the same time...