Unsolved
This post is more than 5 years old
4 Posts
0
1010
February 16th, 2011 02:00
NetWorkerServer 7.6 Unix,NetWorker Client V7.6 (Windows7),Backup failled with VSS failure message
Hello,
running NetWorker Server 7.6, Unix as NW server, Windows7 as client I got the following failure:
I did not find the reason in Knowledge base. Any Ideas?
Thanks
Peter D.
No Events found!
masonb
445 Posts
0
February 16th, 2011 02:00
Peter,
See Support Solution esg108377, it’s for Windows 2008 but I still think its relevant.
Regards
Bill Mason
David_Hampson_90e289
2 Intern
•
243 Posts
0
February 16th, 2011 03:00
Peter
The error message states not enough space availale - can you advise what free space you have on C:\?
Besserwessi
4 Posts
0
February 16th, 2011 03:00
I saw this article but I do not know what
1. Open the disk management on the Windows 2008 client and check which drive don't have a drive letter assigned.
2. Assign the disk with a drive letter.
3. Once you assign the drive letter, open command prompt.
4. On the command prompt type "vssadmin create shadow" and the volume name, for example (F:\).
5. This command will create the new shadow copy for the new drive.
6. Check the Drive properties and click on "Shadow Copies" tab.
7. On "Shadow Copies" tab it will list the shadow copies created for that drive.
8. Run a full backup for the client machine windows 2008 using NetWorker.
means. The NW Client has 3 partitions, one have assigned the drive letter c: and this partition is the only one to save. Two more partions – one is the recovery partition, the other is a small partition with system tools – need no backup. These two partitions have no assigned drive letter.
vssadmin List Shadows shows me that there are already shadow copies for the C.\ drive.
So I’m pretty sure, that drive letter C:\ is correctly configured belonging VSS.
Peter D.
Besserwessi
4 Posts
0
February 16th, 2011 04:00
Hi David,
as you see there should be enough free disk space on drive c:\
Peter D.
David_Hampson_90e289
2 Intern
•
243 Posts
0
February 16th, 2011 04:00
The link to the image does not work but I believe you. I would suggest changing the saveset to C:\ and trying to back that up and seeing if you get the same error - if so that would at least eliminate the recovery partition from the issue.
Besserwessi
4 Posts
0
February 16th, 2011 04:00
ok. I will changed saveset to c:\temp.
Peter