Veritas-bu

RES: RES: [Veritas-bu] NetBackup DataCenter and L100 tape library

2005-01-01 19:57:37
Subject: RES: RES: [Veritas-bu] NetBackup DataCenter and L100 tape library
From: david.trostli AT veritas-software.com DOT br (David Trostli)
Date: Sat, 1 Jan 2005 22:57:37 -0200
to figure out what's the cause of the problem you will have to look at bptm
log and syslog file

David

-----Mensagem original-----
De: Tim Hoke [mailto:thoke AT northpeak DOT org]
Enviada em: sabado, 1 de janeiro de 2005 01:04
Para: David Trostli
Cc: kevin haritmonds; veritas-bu AT mailman.eng.auburn DOT edu
Assunto: Re: RES: [Veritas-bu] NetBackup DataCenter and L100 tape
library


If the drive types weren't the same as the media, then the mounting never
would have occurred and the jobs would have failed with a status 96.

On Fri, 31 Dec 2004, David Trostli wrote:

> Make sure drive type is the same as the media
>
> Regards,
>
> David
>
> -----Mensagem original-----
> De: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]Em nome de Tim Hoke
> Enviada em: sexta-feira, 31 de dezembro de 2004 13:59
> Para: kevin haritmonds
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Assunto: Re: [Veritas-bu] NetBackup DataCenter and L100 tape library
>
>
> Kevin,
>
> I've got a couple of questions for you.
>
> First, were the tapes frozen?
> You can check the tapes with either available_media or bpmedialist.
>
> Second, were the drives downed?
>
> You can check the drives with vmoprcmd -d (GUI's device monitor
> equivalent).
>
> As someone else pointed out, the bptm log and syslog will be most useful
> in the initial troubleshooting.
>
> Check bptm if the tapes were frozen.  Check syslog if they were downed.
>
> When you ran the Wizard, was NBU able to determine which drive
> (/dev/rmt/X) was associated with each robot drive number (Drive 1-4)?  If
> not and you drag-and-dropped them into place, it's possible the drives are
> out of order and NBU is mounting the tapes in the "wrong" drives.
>
> Run /usr/openv/volmgr/bin/scan and see if the robot reports the drive
> serial numbers.  If so, then NBU should have been able to figure out which
> drive goes with with number.
>
> HTH
> -Tim
>
> On Fri, 31 Dec 2004, kevin haritmonds wrote:
>
> > Hi, I'm facing a problem in Veritas NetBackup DataCenter 4.5 server,
> > installed on Solaris 9 platform (using SunBlade 2000 machine),
> > connected to Sun StorEdge L100 Tape Library with 4 drives HP LTO-2 and
> > 96 tape slots. This is the first time we want to use the L100 library.
> > After we installed NetBackup DataCenter 4.5 from CD, we did the setup
> > using Wizards: Configure Storage Devices, Configure Volumes, Configure
> > Backup Catalog, and Create a simple Backup Policy "test1" which only
> > backup server's /etc/ directory (which is localhost) to volume pool
> > "Test1". We assigned two tapes (A00002 and A00003) to volume pool
> > "Test1". Every time we run the policy manually, it always failed with
> > following detailed status:
> > "12/31/2004 14:40:44 - started process bptm (pid=2852)
> > 12/31/2004 14:40:45 - started process bpbrm (pid=2849)
> > 12/31/2004 14:40:45 - connecting
> > 12/31/2004 14:40:45 - connected; connect time: 0:00:00
> > 12/31/2004 14:40:45 - mounting A00003
> > 12/31/2004 14:41:29 - mounted; mount time: 0:00:44
> > 12/31/2004 14:41:29 - positioning A00003 to file 1
> > 12/31/2004 14:41:36 - positioned; position time: 0:00:07
> > 12/31/2004 14:41:36 - begin writing
> > 12/31/2004 14:41:43 - mounting A00002
> > 12/31/2004 14:42:36 - mounted; mount time: 0:00:53
> > 12/31/2004 14:42:36 - positioning A00002 to file 1
> > 12/31/2004 14:42:43 - positioned; position time: 0:00:07
> > 12/31/2004 14:42:50 - Error bptm (pid=2852) Media Manager pool Test1
> > has no more unassigned media in robotic device TLD(0)
> > 12/31/2004 14:42:50 - Error bpbrm (pid=2849) from client baksrv: ERR -
> > bpbkar exiting because backup is aborting
> > 12/31/2004 14:42:54 - end writing; write time: 0:01:18
> > 12/31/2004 14:42:54 - Error bpsched (pid=2832) suspending further
> > backup attempts for client baksrv, policy test1, schedule Full_ETC
> > because it exceeded the configured number of tries
> > 12/31/2004 14:42:54 - Error bpsched (pid=2832) backup of client baksrv
> > exited with status 96 (unable to allocate new media for backup,
> > storage unit has none available)
> > unable to allocate new media for backup, storage unit has none available
> (96)"
> >
> > It looks like the drive wants to write to the tape, but suddenly the
> > tape was ejected a few seconds later and another tape mounted until
> > all media on the pool consumed. This happens every time. FYI the /etc/
> > directory's size is only 7.5 MB. We are using LTO-2 200/400GB tapes.
> > We haven't done any backup using the L100 library.
> >
> > Here's the output of "tpconfig -dl":
> > # /opt/openv/volmgr/bin/tpconfig -dl
> > Currently defined drives and robots are:
> >
> >        Drive Name              HPUltrium2-SCSI0
> >        Index                   0
> >        NonRewindDrivePath      /dev/rmt/0cbn
> >        Type                    hcart2
> >        Status                  UP
> >        Shared Access           No
> >        TLD(0) Definition       DRIVE=4
> >
> >        Drive Name              HPUltrium2-SCSI1
> >        Index                   1
> >        NonRewindDrivePath      /dev/rmt/1cbn
> >        Type                    hcart2
> >        Status                  UP
> >        Shared Access           No
> >        TLD(0) Definition       DRIVE=5
> >
> >        Drive Name              HPUltrium2-SCSI2
> >        Index                   2
> >        NonRewindDrivePath      /dev/rmt/2cbn
> >        Type                    hcart2
> >        Status                  UP
> >        Shared Access           No
> >        TLD(0) Definition       DRIVE=1
> >
> >        Drive Name              HPUltrium2-SCSI3
> >        Index                   3
> >        NonRewindDrivePath      /dev/rmt/3cbn
> >        Type                    hcart2
> >        Status                  UP
> >        Shared Access           No
> >        TLD(0) Definition       DRIVE=2
> >
> > Currently defined robotics are:
> >  TLD(0)     robotic path = /dev/sg/c3t0l0,
> >             volume database host = baksrv
> >
> > I have upgraded the software from NetBackup DataCenter 4.5FP_3GA to
> > 4.5FP_6, but still no luck. Can anyone help me out? Thank you, any
> > help would be very much appreciated.
> >
> > Best regards,
> > Kevin Haritmonds
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>





<Prev in Thread] Current Thread [Next in Thread>