Unsolved

This post is more than 5 years old

1 Message

526

January 28th, 2006 11:00

Cluster virtual node backups fail after upgrade to 7.2.1 with

Hello. We just upgraded from 7.1.3 to 7.2.1. Regular (non-clustered) server clients back up fine after the upgrade, as do physical cluster node clients. However, the virtual servers clients on all clusters now fail when their save sets are set to "All".

The log contains lines similar to this for all cluster virtual nodes:

* cluster5:All nsrexec: authtype nsrexec
* cluster5:All savefs: Diagnostic: This client is not licensed for VSS.
* cluster5:All savefs: cannot retrieve client resources
* cluster5:All No 'NSR client' resource for client cluster5
savefs cluster5: failed.

The "VSS" error was occuring before the upgrade to 7.2.1 and did not cause a problem before.

After doing some experimenting, I found that if I changed the virtual server client "Save set:" from "All" to "R:" (or some other disk on the virtual node), the backup did not fail.

The problem seems to have something to do with now using "Save set: All" on the virtual nodes. The documentation on pages 574/575 of the NetWorker 7.2 manual shows that "All" is legitimate to use on virtual server clients.

The physical cluster host nodes work fine with "Save Sets: All".

Has anyone else ever seen this problem? Any ideas why "All" savesets would not work on virtual server clients after upgrading to 7.2.1, but specific disk savesets such as "R:" and "S:" works OK?

Thanks for any help!
-Bob Longo

4 Operator

 • 

14.4K Posts

January 28th, 2006 11:00

Try running networker.cluster script again on both physical nodes which are in cluster (or on how many they are).

If that doesn't help, delete cluster client definition and recreate it again (due to "cannot retrieve client resources" messages).

1 Message

January 31st, 2006 00:00

If the cause of this problem is VSS license .
Try to disable VSS by
"Client setup"--> "Miscellaneous" -->"Save operation"
then enter value "VSS:*=off".

refer to windows administrator guide 7.2 pages 130

37 Posts

February 2nd, 2006 01:00

Hello,

you can also try with adding remote user with enough privileges and password under remote tab on client.
By default SYSTEM account is used and I have similar problems with virtual node. After I entered remote user and password (just for test put in administrator rights user) and it started working. I Don't know why or what was the reason but you can try.

Regards,

Ojo

18 Posts

March 20th, 2006 12:00

I am having the exact same issue running 7.2.1 in a windows environment. I deleted and recreated the clients, made sure that system@servername was in the remote access tab on the virtual node, it still does not work. I have 4 cluster backups that are failing, any help would be appreciated.

Top