Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5626

July 26th, 2010 12:00

Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

running Networker 7.4.3 on windows 2003, the client windows 2008 R2, networker 7.4 SP5 64bit.

cannot backup the client because of : Error: the client is giving error: unable to set up VSS filesystem  directives

10 Posts

July 27th, 2010 10:00

The save group log displays for each  drive:

1 retry attempted
No full backups of this save set were found in the media database; performing a full backup
43705:(pid 4320): Save Operations value is ignored on this OS platform.
ERROR: VSS failed to get comp=BCD FileGroup list, writer=ASR Writer, error=0x80070008: Not enough storage is available to process this command.
in directives
7154:(pid 4320): Unable to set up VSS filesystem directives. Failed to back up E:\.

Thanks

123 Posts

July 27th, 2010 10:00

Do you have enough free space on C drive?

36 Posts

July 27th, 2010 10:00

Hi

may I know if you tried the steps suggested by John? are you getting the above error, after applying the above steps?

36 Posts

July 27th, 2010 11:00

In the Shadow Copy configuration, there is a volume (hidden partition) with no letter assiged, and with format name such as:

//?/Volume{52283e6f-9607-11de-adea-001cc4798532}

VSS is not able to locate the partition so it's unable to request the snapshot for it.

Un-hide the partition and assign a letter to the volume, then VSS will be able to request snaposhot for that volume.

You may also check the status of the VSS writers using the command "vssadmin list writers" and check if any of the writers listed has an errror.

July 27th, 2010 11:00

Hello Mostafa,

Windows 2008 R2, by default has a reserved partition, and that partition has no drive letter assigned, and that can cause VSS issues, my suggestion is for you to manually, through Disk Manager, assign a letter to that reserved partition.

Let us know.

Thank you.

88 Posts

July 27th, 2010 11:00

.. thanks,

and was the cache cleared also?

87 Posts

July 27th, 2010 11:00

Hello,

Just install the version 7.5.2.

I resolved the issue with this.

Regards,

Elvin...

10 Posts

July 27th, 2010 12:00

Hi,

I labeled that smal reserved partition and this is what I got:

No full backups of this save set were found in the media database; performing a full backup
39078:(pid 3956): SYSTEM error: client `142.x.x.x' is not properly configured on the NetWorker Server

5777:(pid 3956): Cannot open save session with sg12-breast

The only think I noticed different  about this client is the enabler code is set to No. Should I use the code that is on the download page for this networker client

Thanks

10 Posts

July 27th, 2010 13:00

Hi John,

this is Qing Chang, Mostafa's co-worker, since he is going on vacation

for a few weeks, I'd like to join this session and keep working with you

and other guys (you guys are great help so far) to solve the problem

we have.

nsrlic -v shows that we still have one license not being used. But the

2008 R2 box is shown as "Defined Clients" not "Connected clients".

Do we need to do any thing for it to take the one available license?

Thanks,
Qing

10 Posts

July 29th, 2010 07:00

my apology. This topic is marked as answered by accident. It is still

outstanding.

If there is one license available on the server but the client does not

get it, what needs to be done?

Regards,
Qing

88 Posts

July 29th, 2010 13:00

Hi Qing,

Thanks for the update.

Question, since the upgrade of the cleint to NW 7.5.3  was the NW cache cleared?

If not, I reccommend clearing the NW server cache as per the instructions earlier.

This as a result that I suspect that as a result of the upgrade, there may be residual/conflicting record of the client which is preventing NW to become aware that the client has not been granted a license.

The cache may be cleared with the following steps:

- stop nsr services

- rename /nsr/tmp/ folder to /nsr/tmp_old

Now prior to restarting the client, since NW is down, we should take the opportunity to refresh the nsrladb and jobsdb.

For nsrladb, please rename the /nsr/res/nsrladb folder to /nsr/res/nsrladb_old_today'sdate

For jobsdb, please rename the /nsr/res/jobsdb/ to /nsr/res/jobsdb_old_today'sdate

- start nsr services

Test the backup and please let me know the results.

Thanks

10 Posts

August 4th, 2010 09:00

Hi John,

good news, the issue has been resolved.

It is because there is a typo in PTR entry for the client. This

caused a mismatch between the A name and the PTR name

of the client, which Networker does not like at all.

Lesson learned, _again_, check the obvious! I wish networker

could be a bit more explicit when logging this type of error,

instead of just saying the client is not configured properly:-)

Thank you all so much for accompanying us in this journey!

Qing

No Events found!

Top