A failure occurred querying the Writer status.
Since some weeks I have been experiencing this horrible error. I have consulted the Symantec Support pages, but I can find no 'permanent' solution for the environment I am using. Rebooting the server every day is not an option, this is the fileserver that people access remotely almost nearly 24/7. It also doesn't seem to work, the first one or two backups after a reboot work but then it just goes back into the error listen in this threads topic.
There is also a suggestion about freeing more space on C:\, I think there is enough (see below).
My backup server is Windows Server 2008 R2 Standard. It's fully up to date up with the most recent Windows Updates. This is a physical server.
The server I am having trouble with is Windows Server 2012 Standard. It's fully up to date up with the most recent Windows Updates. This is also a physical server.
It has a C:\ drive with 125GB free of 150GB
It has a D:\ drive with 1.6TB free of 1.6TB
It has an E:\ drive with 2.2TB free of 5.5TB
I have attached a screenshot showing the amount of times this server won't backup properly because of the above error. The worst thing about it is because I am backup up such an immense amoutn of data it takes about 25-30 hours to do a full backup. But it doesn't go into error until it's completely done! How can it POSSIBLY give a Writer error status at the very end of the backup process!!
How is that even possible? The writer error is about failing to make a snapshot, why does it not INSTANTLY see that theres a problem and goes into error, why do I have to wait for 30 hours in anticipation to see if the backup software does why I purchased it.
I have 53 servers to backup which takes me over four days, if my fileserver goes into error my entire backup schedule for that week goes out the window. This is becoming increasingly annoying.I don't want to have to come in on weekends because the backup software andomly decides it doesn't want to work.
I'd like to add that my Exchange server also experiences this problem, except not that often. It's just as annoying though as you can understand that if my fileserver gets used 24/7 the Exchange server can't exactly get a daily reboot either. It's even more of a pita to reboot.
All my other servers never have any problems, physical or virtual. Hyper-V or V-Sphere. It just works.
Please advise. Thanks