Anandkrishna
1 Nickel

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

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.

0 Kudos
elvinperez
2 Bronze

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

Hello,

Just install the version 7.5.2.

I resolved the issue with this.

Regards,

Elvin...

0 Kudos
jaii50
1 Nickel

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

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

0 Kudos
jstamp
2 Iron

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

Hi Mostafa,

If the client enabler code is set to no, then this means the client somehow has not been granted a license or unable to retrieve a license.

Please run the command nsrlic -v in order to review your current license allocation status.

If the client connection licenses have been exhausted, here is a temp enabler for 5 client connections

d25054-902ea0-765698 .

Please note that you will need to contact licensing to aquire the auth codes and proper licenses as per your entitlement.

Licensing may be contacted at (408)566-2000 or licensing@emc.com

Thanks.

John

0 Kudos
jaii50
1 Nickel

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

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

0 Kudos
jaii50
1 Nickel

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

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

0 Kudos
jstamp
2 Iron

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

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

0 Kudos
jaii50
1 Nickel

Re: Backing up Windows 2008 R2 on NW 7.4.5 - VSS Error

Jump to solution

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

0 Kudos