Re: [Veritas-bu] LTO3 to LTO4 conversion

[judy_hinchcliffe]

Just change them to be LTO4 tapes.
Every time you run a catalog backup it overwrites what was on the tape.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders
Sent: Thursday, June 03, 2010 2:02 PM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion

When it comes to LTO3 to LTO4 conversion, what about the catalog? I
found where to control what tapes are used for Media 1 and Media 2 (and
reside in the Netbackup pool) but I assume I can leave these on LTO3 for
the time being and just focus on the LTO4 upgrade? When I do want to
move the catalog to LTO4, do I just assign new LTO4 tapes from the
Netbackup pool to be Media 1 and Media 2? Or do I need to copy the
existing catalog from the LTO3 tapes to the LTO4 tapes?


On 05/27/2010 09:33 AM, Nate Sanders wrote:
> Yeah that's what I'm thinking as well. I have a new scratch pool just
> for LTO4 media so that all of the old pools will be disassociated from
> existing policies. As LTO3 tapes expire back to their original pools,
> they won't be used anyways.
>
> On 05/26/2010 06:39 PM, Martin, Jonathan wrote:
>   
>> That's why I was thinking about making a new scratch pool. If you make a new 
>> scratch pool, and "deactivate" the old scratch pool, your LTO3 media should 
>> still return to the old scratch pool when they expire, while barcode rules 
>> move new LTO4 media into the new scratch pool.
>>
>> -Jonathan
>>
>> From: veritas-bu-boun...@mailman.eng.auburn.edu 
>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dean
>> Sent: Wednesday, May 26, 2010 6:07 PM
>> To: Nate Sanders
>> Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>
>> This is an interesting one. I understand the need to keep LTO3 and LTO4 as 
>> the same media type, so you can still restore from LTO3 tapes on LTO4 
>> drives. But how to ensure the expiring LTO3 tapes don't return to scratch 
>> and get reused for new backups?
>>
>> Freezing them is the only way I can think of. It will work. It just means 
>> you'll have to manually unfreeze them at some point in the future so you can 
>> delete them. If you have long-ish retentions on some of these backups (like 
>> 7 years, as we do), it's something that will hang around for a while!
>>
>> It would be nice if there was some way to tell NBU, for a particular tape, 
>> or set of tapes, that they shouldn't be returned to scratch. But I can't 
>> think of any way to do it (other than freezing).
>>
>> Manually flipping the write-protect tab on the tapes is not really an 
>> option, as you'll get lots of backups failing with status 84 (media open 
>> error) when they try to write to the write-protected scratch tapes.
>>
>> I guess freezing is the only option. You can periodically run bpmedialist 
>> over the coming ... years?  and if a tape is both frozen, and expired, 
>> you'll be able to tell that all the images on it have expired. I guess the 
>> best thing to do then would be to physically eject it from the library, then 
>> unfreeze it (I like the term "thaw"), at which point it will go straight 
>> back to the scratch pool. Then you can delete it completely (vmdelete, or 
>> just right click and delete in the GUI).
>>
>> I had an inkling there was a "previous_pool" type parameter you could set 
>> with vmchange, so when a tape expires, it will go back to something other 
>> than the scratch pool, but I can't see any reference to it.
>>
>> If anyone else has a better solution to this little problem, it's something 
>> I'd be interested in too.
>>
>> Cheers
>> Dean
>>
>> On Thu, May 27, 2010 at 4:35 AM, Nate Sanders 
>> mailto:sande...@dmotorworks.com>> wrote:
>> Yeah that is our intent, to keep the media type the same. Changing drive
>> types presents a more challenging rollback and also limits us to the
>> amount of drives we can us during the migration and for restores.
>> Overall using new pools is quicker and easier to migrate with.
>>
>> How do I freeze LTO3 media, outside of having to write protect every
>> tape by hand.
>>
>> On 05/26/2010 01:29 PM, Iverson, Jerald wrote:
>>   
>> 
>>> if you are replacing all drives at once, you may want to keep the media
>>> type the same, so that you can still read the lto3 media in the lto4
>>> drives (such as restoring data). the lto4 drives can also write to the
>>> lto3 media if need be, unless you want to write using encryption.  i've
>>> seen it freeze the lto3 media if it loads it when wanting to write to an
>>> encrypted pool.  if you do keep the drives the same type, then simply
>>> freeze all lto3 media and they shouldn't be able to be written to if
>>> they are "active" or even after all images expire.  they will remain
>>> "frozen" until you unfreeze them, and then you could manually move them
>>> to a media pool that no backup policies use.  you wouldn't need to
>>> change any barcode r

Re: [Veritas-bu] VSP versus VSS

[Spencer O'Donnell]

This is the tool from the Symantec forums and I used it on my Solaris master 
and it worked fine.

 

http://www.symantec.com/connect/downloads/interactive-checkenable-vss-windows-hosts

 

 

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Herbert.George
Sent: Thursday, June 03, 2010 1:22 PM
To: William Brown; Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

If you have a windows machine handy, you could install the media server 
software on it to get the VSP disable tool.  You don't actually have to do 
backups with it.  Of course there are licensing considerations, but that should 
work.

 

Since I don't yet have a 6.5.6 installation, I can only guess that your silent 
install will still work as it has in the past.  But only actually trying it 
will tell.  Maybe someone with 6.5.6 can provide some experience

 

I agree with the previously expressed "VSP is evil!"

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of William Brown
Sent: Thursday, June 03, 2010 5:59 AM
To: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

I was reading that section of the 6.5.6 release notes and I just couldn't quite 
understand it.  It seems to say that as of 6.5.6 Symantec have caused VSP to be 
automatically installed.  Previously we have always disabled it - we do Windows 
installs using silentclient.cmd, and that has an entry you can edit to stop it 
installing VSP.  So it seems to read that as a new feature in 6.5.6 you cannot 
stop it installing VSP?

 

It then goes on to say that at NetBackup 7.0 VSP is not supported

 

Am I reading this right...6.5.6 will install VSP whether you like it or not, 
and so if you want to get back to the 'status quo' at e.g. 6.5.4 of not 
installing it, you must use this new VSP disable tool, or suddenly VSP is going 
to start running on all the 6.5.6 clients, in place of VSS?  There is a table 
on page 50/51 of the 6.5.6 document updates that shows the behaviour of Windows 
- it says "The following table describes the backup behavior based on the 
Windows Open

File Backup setting for the client and whether or not VSS is available on the 
client." - and in none of the cases is VSP run.  I'm guessing that they meant 
to say that the table applies *after the VSP disable tool is run* and that 
makes it really confusing.

 

Does anyone know what actually needs to be done after upgrading to 6.5.6 on 
Windows 2003, to make sure VSP is not going to run?

 

Also...the VSP Disable tool can be run "from a Windows master server or media 
server" - we don't use those, all our Master & Media are UNIX.  So what do we 
do?

 

William D L Brown

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Herbert.George
Sent: 01 June 2010 21:18
To: Spencer O'Donnell; Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

>From a recent case with Symantec support:

 

... in the NB_6.5.6 readme, might be something to consider.

===

NetBackup 6.5.6 automatically installs the Veritas volume snapshot Provider

(VSP) method for Open File Backups. VSP is the default Open File Backup method 
in this release.

NetBackup 6.5.6 includes the VSP disable tool (bpvspdisable.exe) for

administrators to use to disable VSP on clients if it is not needed. The tool 
deletes the VSP cache files from the disk of the client system. All future VSP 
requests on those clients are redirected to use Microsoft native Volume Shadow 
Copy Service (VSS).

The VSP method for Open File Backups is not supported in NetBackup 7.0. Having 
run the VSP disable tool does not affect upgrading to NetBackup 7.0.

The VSP disable tool can be used on the following operating systems:

■ Windows Server 2000

■ Windows Server 2003 with Service Pack 2 (x86 and IA64)

■ Windows XP 32-bit and 64-bit (x86 and IA64)



 

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Spencer 
O'Donnell
Sent: Tuesday, June 01, 2010 1:14 PM
To: Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

May as well convert to VSS now. It is no longer there in 7.0. I swapped all my 
2003 and 2008 clients and things have never work3ed better, no more status code 
156 errors. There is a good vss enabler script on the Symantec Forums. 

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Tuesday, June 01, 2010 11:49 AM
To: pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

On Tue, Jun 1, 2010 at 10:12 AM, pranav batra  
wrote:

 

I have a small question on VSP/VSS.

 

Re: [Veritas-bu] LTO3 to LTO4 conversion

[Nate Sanders]

When it comes to LTO3 to LTO4 conversion, what about the catalog? I
found where to control what tapes are used for Media 1 and Media 2 (and
reside in the Netbackup pool) but I assume I can leave these on LTO3 for
the time being and just focus on the LTO4 upgrade? When I do want to
move the catalog to LTO4, do I just assign new LTO4 tapes from the
Netbackup pool to be Media 1 and Media 2? Or do I need to copy the
existing catalog from the LTO3 tapes to the LTO4 tapes?


On 05/27/2010 09:33 AM, Nate Sanders wrote:
> Yeah that's what I'm thinking as well. I have a new scratch pool just
> for LTO4 media so that all of the old pools will be disassociated from
> existing policies. As LTO3 tapes expire back to their original pools,
> they won't be used anyways.
>
> On 05/26/2010 06:39 PM, Martin, Jonathan wrote:
>   
>> That’s why I was thinking about making a new scratch pool. If you make a new 
>> scratch pool, and “deactivate” the old scratch pool, your LTO3 media should 
>> still return to the old scratch pool when they expire, while barcode rules 
>> move new LTO4 media into the new scratch pool.
>>
>> -Jonathan
>>
>> From: veritas-bu-boun...@mailman.eng.auburn.edu 
>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dean
>> Sent: Wednesday, May 26, 2010 6:07 PM
>> To: Nate Sanders
>> Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>
>> This is an interesting one. I understand the need to keep LTO3 and LTO4 as 
>> the same media type, so you can still restore from LTO3 tapes on LTO4 
>> drives. But how to ensure the expiring LTO3 tapes don't return to scratch 
>> and get reused for new backups?
>>
>> Freezing them is the only way I can think of. It will work. It just means 
>> you'll have to manually unfreeze them at some point in the future so you can 
>> delete them. If you have long-ish retentions on some of these backups (like 
>> 7 years, as we do), it's something that will hang around for a while!
>>
>> It would be nice if there was some way to tell NBU, for a particular tape, 
>> or set of tapes, that they shouldn't be returned to scratch. But I can't 
>> think of any way to do it (other than freezing).
>>
>> Manually flipping the write-protect tab on the tapes is not really an 
>> option, as you'll get lots of backups failing with status 84 (media open 
>> error) when they try to write to the write-protected scratch tapes.
>>
>> I guess freezing is the only option. You can periodically run bpmedialist 
>> over the coming ... years?  and if a tape is both frozen, and expired, 
>> you'll be able to tell that all the images on it have expired. I guess the 
>> best thing to do then would be to physically eject it from the library, then 
>> unfreeze it (I like the term "thaw"), at which point it will go straight 
>> back to the scratch pool. Then you can delete it completely (vmdelete, or 
>> just right click and delete in the GUI).
>>
>> I had an inkling there was a "previous_pool" type parameter you could set 
>> with vmchange, so when a tape expires, it will go back to something other 
>> than the scratch pool, but I can't see any reference to it.
>>
>> If anyone else has a better solution to this little problem, it's something 
>> I'd be interested in too.
>>
>> Cheers
>> Dean
>>
>> On Thu, May 27, 2010 at 4:35 AM, Nate Sanders 
>> mailto:sande...@dmotorworks.com>> wrote:
>> Yeah that is our intent, to keep the media type the same. Changing drive
>> types presents a more challenging rollback and also limits us to the
>> amount of drives we can us during the migration and for restores.
>> Overall using new pools is quicker and easier to migrate with.
>>
>> How do I freeze LTO3 media, outside of having to write protect every
>> tape by hand.
>>
>> On 05/26/2010 01:29 PM, Iverson, Jerald wrote:
>>   
>> 
>>> if you are replacing all drives at once, you may want to keep the media
>>> type the same, so that you can still read the lto3 media in the lto4
>>> drives (such as restoring data). the lto4 drives can also write to the
>>> lto3 media if need be, unless you want to write using encryption.  i've
>>> seen it freeze the lto3 media if it loads it when wanting to write to an
>>> encrypted pool.  if you do keep the drives the same type, then simply
>>> freeze all lto3 media and they shouldn't be able to be written to if
>>> they are "active" or even after all images expire.  they will remain
>>> "frozen" until you unfreeze them, and then you could manually move them
>>> to a media pool that no backup policies use.  you wouldn't need to
>>> change any barcode rules or backup policies.
>>>
>>> jerald
>>>
>>> -Original Message-
>>> From: 
>>> veritas-bu-boun...@mailman.eng.auburn.edu
>>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu]
>>>  On Behalf Of Martin,
>>> Jonathan
>>> Sent: Wednesday, May 26, 2010 1:08 PM
>>> To: Nate Sanders

Re: [Veritas-bu] VSP versus VSS

[Herbert.George]

If you have a windows machine handy, you could install the media server 
software on it to get the VSP disable tool.  You don't actually have to do 
backups with it.  Of course there are licensing considerations, but that should 
work.

 

Since I don't yet have a 6.5.6 installation, I can only guess that your silent 
install will still work as it has in the past.  But only actually trying it 
will tell.  Maybe someone with 6.5.6 can provide some experience

 

I agree with the previously expressed "VSP is evil!"

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of William Brown
Sent: Thursday, June 03, 2010 5:59 AM
To: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

I was reading that section of the 6.5.6 release notes and I just couldn't quite 
understand it.  It seems to say that as of 6.5.6 Symantec have caused VSP to be 
automatically installed.  Previously we have always disabled it - we do Windows 
installs using silentclient.cmd, and that has an entry you can edit to stop it 
installing VSP.  So it seems to read that as a new feature in 6.5.6 you cannot 
stop it installing VSP?

 

It then goes on to say that at NetBackup 7.0 VSP is not supported

 

Am I reading this right...6.5.6 will install VSP whether you like it or not, 
and so if you want to get back to the 'status quo' at e.g. 6.5.4 of not 
installing it, you must use this new VSP disable tool, or suddenly VSP is going 
to start running on all the 6.5.6 clients, in place of VSS?  There is a table 
on page 50/51 of the 6.5.6 document updates that shows the behaviour of Windows 
- it says "The following table describes the backup behavior based on the 
Windows Open

File Backup setting for the client and whether or not VSS is available on the 
client." - and in none of the cases is VSP run.  I'm guessing that they meant 
to say that the table applies *after the VSP disable tool is run* and that 
makes it really confusing.

 

Does anyone know what actually needs to be done after upgrading to 6.5.6 on 
Windows 2003, to make sure VSP is not going to run?

 

Also...the VSP Disable tool can be run "from a Windows master server or media 
server" - we don't use those, all our Master & Media are UNIX.  So what do we 
do?

 

William D L Brown

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Herbert.George
Sent: 01 June 2010 21:18
To: Spencer O'Donnell; Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

>From a recent case with Symantec support:

 

... in the NB_6.5.6 readme, might be something to consider.

===

NetBackup 6.5.6 automatically installs the Veritas volume snapshot Provider

(VSP) method for Open File Backups. VSP is the default Open File Backup method 
in this release.

NetBackup 6.5.6 includes the VSP disable tool (bpvspdisable.exe) for

administrators to use to disable VSP on clients if it is not needed. The tool 
deletes the VSP cache files from the disk of the client system. All future VSP 
requests on those clients are redirected to use Microsoft native Volume Shadow 
Copy Service (VSS).

The VSP method for Open File Backups is not supported in NetBackup 7.0. Having 
run the VSP disable tool does not affect upgrading to NetBackup 7.0.

The VSP disable tool can be used on the following operating systems:

■ Windows Server 2000

■ Windows Server 2003 with Service Pack 2 (x86 and IA64)

■ Windows XP 32-bit and 64-bit (x86 and IA64)



 

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Spencer 
O'Donnell
Sent: Tuesday, June 01, 2010 1:14 PM
To: Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

May as well convert to VSS now. It is no longer there in 7.0. I swapped all my 
2003 and 2008 clients and things have never work3ed better, no more status code 
156 errors. There is a good vss enabler script on the Symantec Forums. 

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Tuesday, June 01, 2010 11:49 AM
To: pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

On Tue, Jun 1, 2010 at 10:12 AM, pranav batra  
wrote:

 

I have a small question on VSP/VSS.

 

As symantec recommends VSS for 2003 clients over VSP then why  it is the 
defauly snap-shot provider option ?


It's historical and is no longer the default in NetBackup 7.0. 
 

Any specific reason for this recommendation as i can't find any tech 
note specifying why VSS:

 

They all just explain that VSS is for 2003 and VSP for 2000.

I agree but why?


Windows 2000 did not have a snapshot servi

[Veritas-bu] Socket write failures on Windows 2000 clients

[Matteson, Ryan]

Howdy,

I have one Windows 2000 server where backups keep failing with status code 24 
(socket write failed). The backups will run fine for a period of time, and then 
randomly fail after a random amount of data has been backed up (I have not seen 
any patterns with the files or amount of data backed up). I've checked various 
things on the host and network switches:

1. Made sure speed/duplex settings match

2. Checked for errors on the switch

3. Reviewed the event log to see if anything is fishy

4. Used the Symantec sas tool to verify the connection is clean

5. Changed cables and switch ports

6. Applied all of service packs and updates to the Windows 2000 host

7. Verified our NIC drivers are current

All of the items listed above didn't help, and I'm still getting 24s randomly 
during the backups. Has anyone encountered any issues with Windows 2000 server 
that could cause 24s to occur? The media, master and client are all running 
Netbackup 6.5.5, and we are running Solaris 10 with the latest patches on our 
servers.

Thanks for any insight,
- Ryan

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] how fo fool nbu client versions

[Herbert.George]

Symantec support will talk to you about troubleshooting issues on older
clients.  However, if it comes down to something that would require a
code change to the older client, that would be a no go.

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

Mail Code: FL-Orlando-9119  

7455 Chancellor Drive

Orlando, FL 32809

Tel: 407-762-5671 (STNet 241)  Mobile: 407-271-0209

 

Live Solid. Bank Solid.

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Wednesday, June 02, 2010 7:21 PM
To: rusty.ma...@sungard.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] how fo fool nbu client versions

 

On Wed, Jun 2, 2010 at 5:21 PM,  wrote:


Heading off topic, but for the benefit of those who had a heart-attack
thinking they were out of support with 5.1 clients as they ARE supported
with NBU 6.x Master/Media servers.


Change ARE to WERE.  All of 5.1 has already reached end of support life
so although the original combination was supported, it isn't any longer.
That means it will very likely work but don't call Symantec if it
doesn't.  We've got another couple of years for 6.x though:
http://seer.entsupport.symantec.com/docs/332616.htm



 

 

Sent by:  

05/30/2010 01:03 AM 

To

veritas-bu@mailman.eng.auburn.edu 

cc


Subject

Re: [Veritas-bu] how fo fool nbu client versions

 



I have tested this on some proprietary servers of my own, and
the 5.1 client works with 7.0, although not supported.  If you are
running any 6.5.x with a 5.1 client, that isn't supported either, so no
harm, no foul.  From what I understand, the code base isn't that
different from 6.5 to 7.0, and that is why it works.   


Actually, the UNIX code base from 6.5 to 7.0 is actually quite different
since 32-bit OS releases were dropped and 64-bit was added.  I asked one
of the developers how much actually had to change for 64-bit and he said
it was a lot more than you would expect.  A lot of very old legacy code
was tossed and replaced with current code. Interestingly enough, I
haven't heard of any 7.0 Unix client issues related to the 64-bit
upgrades.


   .../Ed 
  
  
  
LEGAL DISCLAIMER 
The information transmitted is intended solely for the individual or entity to 
which it is addressed and may contain confidential and/or privileged material. 
Any review, retransmission, dissemination or other use of or taking action in 
reliance upon this information by persons or entities other than the intended 
recipient is prohibited. If you have received this email in error please 
contact the sender and delete the material from any computer. 
  
SunTrust is a federally registered service mark of SunTrust Banks, Inc. Live 
Solid. Bank Solid. is a service mark of SunTrust Banks, Inc. 
[ST:XCL] 
 
 
 
 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Backups failng with 156 when VSS is slected

[Marianne Van Den Berg]

Hi Pranav

 

You are mentioning Lotus Notes - are you trying to backup the Notes
databases with a normal file system backup?

I don't know of any snapshot provider that will be able to actually
snapshot large databases. 

 

You should ideally use the Lotus Notes agent to backup those databases
and then exclude them from normal filesystem backups.

 

Regards

 

M.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of pranav
batra
Sent: 02 June 2010 07:57 PM
To: Veritas
Subject: [Veritas-bu] Backups failng with 156 when VSS is slected

 

Hello Geeks,

 

 

Backups of my two lotus notes clients are failing with 156 when VSS
option with abort backup on error is selected.

 

If i select disable snap shot and continue in case of snap-shot error
what i would loose.

Will my backups be called as complete?

 

Any resolution of this 156 issue?

 

Please help.

 

 



Thanks and Regards
Pranav Batra







Chin music and high voltage T20 action on MSN Sports Sign up now.
 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] VSP versus VSS

[William Brown]

I was reading that section of the 6.5.6 release notes and I just couldn't quite 
understand it.  It seems to say that as of 6.5.6 Symantec have caused VSP to be 
automatically installed.  Previously we have always disabled it - we do Windows 
installs using silentclient.cmd, and that has an entry you can edit to stop it 
installing VSP.  So it seems to read that as a new feature in 6.5.6 you cannot 
stop it installing VSP?

It then goes on to say that at NetBackup 7.0 VSP is not supported

Am I reading this right...6.5.6 will install VSP whether you like it or not, 
and so if you want to get back to the 'status quo' at e.g. 6.5.4 of not 
installing it, you must use this new VSP disable tool, or suddenly VSP is going 
to start running on all the 6.5.6 clients, in place of VSS?  There is a table 
on page 50/51 of the 6.5.6 document updates that shows the behaviour of Windows 
- it says "The following table describes the backup behavior based on the 
Windows Open
File Backup setting for the client and whether or not VSS is available on the 
client." - and in none of the cases is VSP run.  I'm guessing that they meant 
to say that the table applies *after the VSP disable tool is run* and that 
makes it really confusing.

Does anyone know what actually needs to be done after upgrading to 6.5.6 on 
Windows 2003, to make sure VSP is not going to run?

Also...the VSP Disable tool can be run "from a Windows master server or media 
server" - we don't use those, all our Master & Media are UNIX.  So what do we 
do?

William D L Brown

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Herbert.George
Sent: 01 June 2010 21:18
To: Spencer O'Donnell; Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

From a recent case with Symantec support:

... in the NB_6.5.6 readme, might be something to consider.
===
NetBackup 6.5.6 automatically installs the Veritas volume snapshot Provider
(VSP) method for Open File Backups. VSP is the default Open File Backup method 
in this release.
NetBackup 6.5.6 includes the VSP disable tool (bpvspdisable.exe) for
administrators to use to disable VSP on clients if it is not needed. The tool 
deletes the VSP cache files from the disk of the client system. All future VSP 
requests on those clients are redirected to use Microsoft native Volume Shadow 
Copy Service (VSS).
The VSP method for Open File Backups is not supported in NetBackup 7.0. Having 
run the VSP disable tool does not affect upgrading to NetBackup 7.0.
The VSP disable tool can be used on the following operating systems:
■ Windows Server 2000
■ Windows Server 2003 with Service Pack 2 (x86 and IA64)
■ Windows XP 32-bit and 64-bit (x86 and IA64)



George Herbert
Basline Storage Engineer - Backup

SunTrust Banks, Inc.
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Spencer 
O'Donnell
Sent: Tuesday, June 01, 2010 1:14 PM
To: Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

May as well convert to VSS now. It is no longer there in 7.0. I swapped all my 
2003 and 2008 clients and things have never work3ed better, no more status code 
156 errors. There is a good vss enabler script on the Symantec Forums.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Tuesday, June 01, 2010 11:49 AM
To: pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

On Tue, Jun 1, 2010 at 10:12 AM, pranav batra 
mailto:pranav_vent...@hotmail.com>> wrote:

I have a small question on VSP/VSS.

As symantec recommends VSS for 2003 clients over VSP then why  it is the 
defauly snap-shot provider option ?

It's historical and is no longer the default in NetBackup 7.0.

Any specific reason for this recommendation as i can't find any tech note 
specifying why VSS:

They all just explain that VSS is for 2003 and VSP for 2000.
I agree but why?

Windows 2000 did not have a snapshot service provided by the operating system 
so Veritas had to write their own.  Microsoft added it in Windows 2003.

VSS has a HUGE advantage for the backup administrator because snapshots are now 
the responsibility of the server administrator, not the backup administrator.  
If snapshots fail, it's usually because the server administrator doesn't have 
something configured correctly or the admins have neglected to install patches 
to VSS (there are some but some Windows admins seem to install ONLY security 
patches and ignore all reliability/functionality fixes).

What happened two weeks ago:-There are our two cluster server and both got hung 
while getting backed up.
We are still looking for the root cause but couldn't find yet...The thing we 
suspect is that they were using VSP and when we changed snapshot provider to 
VSS( As they are 2003) ,backups and server both running fine from