Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1

But it worked :-) From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: Thursday, January 31, 2008 10:14 AM To: Clooney, David; WEAVER, Simon (external); [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Whats Best Practice for SSO

Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1

remember its a soft SCSI release and not a hardware release. From: Clooney, David Sent: 31 January 2008 10:13 To: 'WEAVER, Simon (external)'; [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1

Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1

vmoprcmd -crawlreleasebyname drive_name From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: 30 January 2008 16:54 To: [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for

[Veritas-bu] Another bpstart, oracle and streams question

Guys im running Netbackup 6.0mp4 and a number of oracle SSO media servers backing themselves up. Solaris9/10 This has been mentioned before many times im sure and i found a thread on it called 'Yet another bpstart/bpend questions' but i dont have a copy of it to reply to. Basically as im

Re: [Veritas-bu] Another bpstart, oracle and streams question

The short answer is: don't even try if you have multiple disks. You *may* be able to get away with it now using the parent/child job functionality that got added in 6.0 but we haven't tested this, having given up on a long time ago after a multi-year battle. Sure, you can get it work most of

Re: [Veritas-bu] Another bpstart, oracle and streams question

Curious about this thread - so far as I know we're not doing anything special for backing up voting disk and OCR for Oracle RAC (unless the DBAs somehow set this up via RMAN to the policies we created in NBU). Is this something we should be doing? From:

[Veritas-bu] Netbackup 6.5.1 with VCB 1.1

Hi all, I am currently implementing NBU 6.5.1 with VCB 1.1. Am using Netapps FAS2020 iSCSI LUNs. However on running the backup in NBU 6.5.1 with VCB 1.1, I always get snapshot error. We always get error code 156. Error Message: FTL - snapshot creation failed, status 156 Although I can see

Re: [Veritas-bu] cron script doing global search to backup specificfiles

I don't have an environment that I can test this on right now but you might try excluding everthing then including back in the *.pst files afterward, ie: $cat /usr/openv/netbackup/exclude_list.policyname / $cat /usr/openv/netbackup/include_list.policyname *.pst ...might work... Otherwise you

[Veritas-bu] Max Fragment Size for Disk and LTO4 Based Storage Units

So I just got a SpectraLogic T950 tape library, and after some initial teething pains it's up and running and it's wicked fast, but being an impatient little monkey of a NetBackup administrator I'm wondering if I could make it wicked faster. My primary backups go to DataDomain restorers and then

Re: [Veritas-bu] Max Fragment Size for Disk and LTO4 Based Storage Units

On Jan 31, 2008 6:21 PM, JAJA (Jamie Jamison) [EMAIL PROTECTED] wrote: So I just got a SpectraLogic T950 tape library, and after some initial teething pains it's up and running and it's wicked fast, but being an impatient little monkey of a NetBackup administrator I'm wondering if I could

Re: [Veritas-bu] Netbackup 6.5.1 with VCB 1.1

Hi Daniel. A snapshot creation error (status 156) can be caused by a number of issues. These include: *** Backup Proxy has not been provided access (via iSCSI in your case) to the VMware Datastore(s). If this is the case the snapshot creation would fail pretty much as you are describing. This

[Veritas-bu] NBU Catalog on NAS

Hi Guys, Anyone know if NBU catalog is store on a NAS storage instead of SAN or localdisk? We can cases where the catalog is on the NAS as we encounter status 233 and this don't happen if we using SAN. Any experience to share?