It's not strange that you ran into this issue, it's strange that you
just now ran into it. By default, Networker tries to use VSS whether you
have a license or not on a Windows 2003 client.
Under the "Save operations:" configuration on the client, put
"VSS:*=off", and that will disable it from trying VSS.
----
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com | Phone: 914-460-4039
aim: matthewbhuff | Fax: 914-460-4139
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Werth, Dave
Sent: Wednesday, November 28, 2007 1:06 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] VSS issue
As noted in a message last week I moved our Networker Server to new
hardware on Friday. Other than the expected loose ends it mostly worked
as planned. BTW, I took Thierry Faidherbe's advice and just copied the
./res, ./mm & ./index directories across rather than the special backup.
The worst problem was that the guy who set up the hardware had left the
particular SCSI interface I needed to use disabled in the BIOS and it
took me 2.5 hours of troubleshooting to figure that out.
The current setup is Networker Server 7.2.Build.494 on Windows 2003
Server. Most clients are also Networker 7.2 or 7.1.
So, yesterday I come in and discover that backups from a client (that
happened to be the old Networker Server) had failed with the message:
xxx is a VSS SYSTEM save set name and is invalid for use with this save
operation; VSS is either disabled or a VSS license was not obtained.
???! We're not using VSS anywhere so what's going on? Ok, I figured it
was something to do with the old server interacting strangely with the
new one so I uninstalled and reinstalled the Networker software. I come
in this morning and discover that this client backed up ok but the
problem had migrated to another client. The client that has the problem
now is alphabetically just before the one that had the problem yesterday
and it is running the Networker 7.3 client because it's a 64 bit SQL
Server system (on W2K3) but I doubt that either of those things has
anything to do with it.
I have checked with EMC support but didn't find anything that appeared
to apply to this situation. Again, we are not using VSS in any way so I
don't understand why I'm having the problem.
So if I uninstall/reinstall the client on the new system with the
problem will it just migrate to another client? Is there some way to
clear up this problem before I go through all of the clients? Any
advice would be appreciated.
Thanks, Dave.
David Werth
Garmin AT, Inc
Salem, Oregon
dave.werth<at>garmin.com
-------------------------
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient. If you are not the intended
recipient, please be aware that any disclosure, copying, distribution or
use of this e-mail or any attachment is prohibited. If you have
received this e-mail in error, please contact the sender and delete all
copies.
Thank you for your cooperation
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
