0n Wed, Jan 13, 2010 at 11:23:25AM -0500, David McWilliams wrote:
>Tpconfig worked flawlessly. Robtest moved a tape from s1 to d1 fine, but is
>giving SCSI errors when trying to move back. Devfsadm seemed ok. I'm
>starting to suspect a physical tape library problem, which is of c
> Wow ... backing up a TSM system with NBU. I hope you do a lot of testing.
> TSM does a lot of stuff in the background. I'd make sure TSM is shutdown,
> not just the data volumes and your backup includes everything that is TSM,
> especially the database.
Actually we will only back up the data v
I know this has been an NBU SAN whatever discussion, but ...
Wow ... backing up a TSM system with NBU. I hope you do a lot of testing.
TSM does a lot of stuff in the background. I'd make sure TSM is shutdown,
not just the data volumes and your backup includes everything that is TSM,
especially t
David,
Did you remember to stop and restart the daemons after making the changes?
If this is not the master or stand alone server you should stop and restart
them on the master and the media server. It should remind you when you run
tpconfig (at the start) but it should be:
/usr/openv/volmgr
1. Quit jnbSA and re-open it.
2. Does vmoprcmd -d ds show the drives on the media server?
3. Is the 'robotic controller host' set correctly?
4. If not, stopltid, run tpconfig, set it.
5. Then manually/hand re-configure the drives to be drives in the robot.
On Wed, 13 Jan 2010, David McWilliams w
I guess I didn't... the move worked
The Device Monitor still doesn't see the drives, although "media and device
management' does.
Sláinte,
David
"Build a man a fire he'll be warm for a day, set a man on fire and he'll be
warm for the rest of his life" - Terry Pratchett
Checkout my photos - htt
Did you rewind and offline the tape OR wait 3 min before you tried to
unload?
mt -f /dev/device rewoffl
then move it
On Wed, 13 Jan 2010, David McWilliams wrote:
Tpconfig worked flawlessly. Robtest moved a tape from s1 to d1 fine, but is
giving SCSI errors when trying to move back. Devfsadm
Tpconfig worked flawlessly. Robtest moved a tape from s1 to d1 fine, but is
giving SCSI errors when trying to move back. Devfsadm seemed ok. I'm
starting to suspect a physical tape library problem, which is of course, not
maintained and really old.
Sláinte,
David
"Build a man a fire he'll be war
I also never had any luck with the wizard.
I always set add the drives by hand, seems to work better.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jeff Cleverley
Sent: Wednesday, January 13, 2010 10:20 AM
To: David McWilliams
David,
I never had any luck with the wizard creating drives in a library. I always
used tpconfig and set it up that way. It sounds like everything else is
working. You should be able to add the drives to the library using
tpconfig.
Jeff
On Wed, Jan 13, 2010 at 8:40 AM, David McWilliams wrote:
Hi,
Can you see the devices?
cat /proc/scsi/scsi
Try a quick re-configure?
/usr/openv/volmgr/bin/tpautoconf -a
Are the drives OK?
Can you run robtest and run "s d" and see the drives?
Justin.
On Wed, 13 Jan 2010, David McWilliams wrote:
I was asked to assist with a NetBackup 3.4 problem to
I was asked to assist with a NetBackup 3.4 problem today. Basically
ltid will not stay up. Further investigation shows that the software
no longer had and device config info. When I try running the config
wizard, it does see the drives, but not in a library, only as
standalone. NetBackup sees the l
Absolutely, but I was giving one example for 1 tape :-)
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Wednesday, January 13, 2010 11:28 AM
To: WEAVER, Simon (external)
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] I inherited a mess.
Hi,
Hi,
> NOTE: It can take up to 4 hours to do a full import of a single tape.
> HTH
> Simon
Yes, and many more hours if you have multiplexed backup streams which span
multiple tapes.
Justin.
On Wed, 13 Jan 2010, WEAVER, Simon (external) wrote:
> Netbackup should be more than happy to talk to th
Dear NetBackup milisers,
I have a problem when doing the BMR backup for my Windows client.
Here is the detailed status that contains the error message:
=== BEGIN ===
Jan 3, 2010 3:30:00 PM - requesting resource veritas-hcart2-robot-tld-2
Jan 3, 2010 3:30:00
Thomas
FT Server is only required if you want to backup SAN Clients (ie: Standard
NetBackup clients, configured to talk over the SAN directly).
This is covered in the Admin Guide for Shared Storage - Google it, it can be
downloaded :)
Simon
-Original Message-
From: veritas-bu-boun...@m
Netbackup should be more than happy to talk to the stand alone drive.
Then it is a case of importing the tape (or tapes) that is needed for
the restore. if you have an inventory of what was on the media, then you
should be ok.
NOTE: It can take up to 4 hours to do a full import of a single tape.
Just
I have a SAN Media Server, using SSO to a tape library, its own
dedicated STU.
Now this backup job can be configured over the LAN or directly accessing
the Tape Drive.
LAN speeds are half than what they are accessing the tape drive over the
Fabric.
It could be the terminology, as SAN Client
As you said this catalog is outdated for more than 3 years probably the
NetBackup used was version 5.x or 4.x. Other information is about name server,
the new server has a different name, which indicates that you made a new
installation not a upgrade.
The best to do is import the tap
<< we now only need a SAN Media Server license for the server so it can send
its data over the SAN directly to tape.>>
Absolutely correct. Also, if those TSM files are large, you will get good
performance. All you need to plan is that at the time your 30 minute slot
comes round, the shared ta
2010/1/12 William Brown :
> Don't confuse the confusing names Symantec uses!
>
> A SAN Media Server backs up it's own disks (only) and sends the data over the
> SAN to SAN-attached tape drives (commonly)
>
> A normal Media Server (licence is double the list price) also send data to
> storage just
21 matches
Mail list logo