Networker

Re: [Networker] VSS: intermittent failure because Legato tries to use VSS

2006-08-18 13:46:59
Subject: Re: [Networker] VSS: intermittent failure because Legato tries to use VSS
From: Paul Langford <plangfor AT AB.BLUECROSS DOT CA>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 18 Aug 2006 11:45:14 -0600
Blue Cross is all over.  Each province has one as the rules for coverage and
operation are different in each province.  And each state in the US.

Basic health care (Dr.'s visits, some basic hospital related stuff-mostly
outpatient) is covered by either the government or by provincial plans.
Long term care, elective surgery, hospital stays and the like are either not
covered or are partially covered by the government.

Paul

-----Original Message-----
From: Albert Eddie Contractor AFRPA CIO/IT
[mailto:Eddie.Albert AT AFRPA.PENTAGON.AF DOT MIL]
Sent: August 18, 2006 11:48 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] VSS: intermittent failure because Legato tries
to use VSS


It was recommended to me to wait for 7.3.2 which addresses a number of
fixes. I am guessing my original estimate to be on 7.3.x by October is
accurate.

Best of luck either way...

Off-Topic: Why is Blue Cross in Canada? I thought your insurance was
gov't provided up there? Of course that does not mean an Insurance
company providing service to other countries could not he HQ in CA.
/shrug Just made me curious when I saw your email address... /ALE

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Paul Langford
> Sent: Friday, August 18, 2006 1:14 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] VSS: intermittent failure because 
> Legato tries to use VSS
> 
> We are on 7.2.1 on my backup servers.  The clients are at the 
> same level.
> I've only had to use it for a couple of months, and for a 
> couple of clients.
> Haven't had any issues so far. We are going to 7.3.1 in a month or so.
> 
> Paul
> 
> -----Original Message-----
> From: Albert Eddie Contractor AFRPA CIO/IT 
> [mailto:Eddie.Albert AT AFRPA.PENTAGON.AF DOT MIL]
> Sent: August 18, 2006 10:57 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] VSS: intermittent failure because 
> Legato tries to use VSS
> 
> 
> Maybe this is a 7.2.x FLAW but I have entered this and the 
> system seems to LOSE this setting every once in a while. I 
> don't know how or why, I am (supposedly) the only one 
> changing settings on backup servers and I have never taken 
> changed this but I have had to reset it several times over 
> the past year.
> 
> //SIGNED//
> Eddie Albert, Enterprise Archive Engineer
> 
> > -----Original Message-----
> > From: Legato NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Paul Langford
> > Sent: Friday, August 18, 2006 12:32 PM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: Re: [Networker] VSS: intermittent failure because Legato 
> > tries to use VSS
> > 
> > Turn off the VSS backup.
> > 
> > 1. Open NetWorker Administrator / nwadmin and connect to your 
> > NetWorker Server 2. Edit the client resource that you do 
> not want to 
> > use VSS backups for 3. Click the Miscellaneous tab under the client 
> > resource and type the following into the "save operation" attribute 
> > (without quotes): "VSS:*=off"
> > 
> > Paul L.
> > 
> > -----Original Message-----
> > From: Pascal Rijs [mailto:pascal.rijs AT UNILEVER DOT COM]
> > Sent: August 18, 2006 1:47 AM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] VSS: intermittent failure because 
> Legato tries to 
> > use VSS
> > 
> > 
> > Recently we moved from a W2K 7.2.2 Legato server to a Windows
> > 2003 7.2.2 Legato server. In the last month I've seen 
> Legato making a 
> > mistake twice for trying to backup via VSS while not 
> configured to do 
> > so.
> > 
> > The clients were configured to backup "ALL" savesets and 
> the savegroup 
> > completion report shows the following:
> > 
> > * hostname.fqdn:VSS SYSTEM BOOT:\ 5 retries attempted
> >   hostname.fqdn:VSS SYSTEM BOOT:\: No full backups of this save set 
> > were found in the media database; performing a full backup
> > * hostname.fqdn:VSS SYSTEM BOOT:\ save: Diagnostic: This 
> client is not 
> > licensed for VSS.
> > * hostname.fqdn:VSS SYSTEM BOOT:\ save: VSS SYSTEM BOOT:\ 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.
> > * hostname.fqdn:VSS SYSTEM SERVICES:\ 5 retries attempted
> >   hostname.fqdn:VSS SYSTEM SERVICES:\: No full backups of this save 
> > set were found in the media database; performing a full backup
> > * hostname.fqdn:VSS SYSTEM SERVICES:\ save: Diagnostic: 
> This client is 
> > not licensed for VSS.
> > * hostname.fqdn:VSS SYSTEM SERVICES:\ save: VSS SYSTEM 
> SERVICES:\ 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.
> > * hostname.fqdn:VSS USER DATA:\ 5 retries attempted
> >   hostname.fqdn:VSS USER DATA:\: No full backups of this 
> save set were 
> > found in the media database; performing a full backup
> > * hostname.fqdn:VSS USER DATA:\ save: Diagnostic: This 
> client is not 
> > licensed for VSS.
> > * hostname.fqdn:VSS USER DATA:\ save: VSS USER DATA:\ 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.
> > * hostname.fqdn:VSS OTHER:\ 5 retries attempted
> >   hostname.fqdn:VSS OTHER:\: No full backups of this save set were 
> > found in the media database; performing a full backup
> > * hostname.fqdn:VSS OTHER:\ save: Diagnostic: This client is not 
> > licensed for VSS.
> > * hostname.fqdn:VSS OTHER:\ save: VSS OTHER:\ 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.
> > * hostname.fqdn:VSS SYSTEM FILESET:\ 5 retries attempted
> >   hostname.fqdn:VSS SYSTEM FILESET:\: No full backups of 
> this save set 
> > were found in the media database; performing a full backup
> > * hostname.fqdn:VSS SYSTEM FILESET:\ save: Diagnostic: This 
> client is 
> > not licensed for VSS.
> > * hostname.fqdn:VSS SYSTEM FILESET:\ save: VSS SYSTEM 
> FILESET:\ 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.
> > * hostname.fqdn:VSS ASR DISK:\ 5 retries attempted
> >   hostname.fqdn:VSS ASR DISK:\: No full backups of this 
> save set were 
> > found in the media database; performing a full backup
> > * hostname.fqdn:VSS ASR DISK:\ save: Diagnostic: This client is not 
> > licensed for VSS.
> > * hostname.fqdn:VSS ASR DISK:\ save: VSS ASR DISK:\ 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.
> > 
> > 
> > Restarting the same client would be normal again and backup 
> > successfully.
> > Has anyone seen the same happening and what did you do to resolve 
> > this?
> > 
> > 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 wit 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 wit 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 wit 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 wit 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
wit 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
wit 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