Hi Phil
Alot of this is unix stuff - so not too sure if it will all work here,
however I think I have made some progress.
I am able to configure server001 now, although unable to configure sso as I
have backups running and it wants to restart the Services once completed.
Did not want to do this yet.
when I go to configure storage devices for the 2nd server, it detects 1
robot and 4 drives, which is great.
When I click next, it shows the ESL Library has a cross against it. there is
also limitations. when I click on this and goto properties, it tells me
""General auto-detection anomaly. This could be caused by a bad or missing
driver for the device."
If I continue, drives are in a standalone state.
Any ideas.
Thanks
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: <mailto:Simon.Weaver at Astrium-eads.net> Simon.Weaver at
Astrium-eads.net
-----Original Message-----
From: Weber, Philip [mailto:Philip.Weber at egg.com]
Sent: 06 June 2006 12:13
To: WEAVER, Simon; veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Netbackup Device Configuration problems :-(
I've occasionally found it necessary to delete everything NetBackup knows
about the attached robots and drives, and re-scan from scratch, using the
steps below. Seems a bit drastic, but it does the job and the configuration
ends up clean.
Re-map Drives and Robots into NetBackup
For example, after moving drives or PCI cards around in media servers you
will need to go through this process to ensure all the paths match, between
the OS, robotic tools and Net Backup :
1. Do the necessary to get the OS up to date, i.e. remove /dev/rmt
entries and reconfigure reboot.
2. Check how many drives can be seen using sgscan tape. Depending, it
may not be necessary to reinstall the sg driver.
3. Re-install the (Veritas) sg driver.
1. rem_drv sg
2. rm /kernel/drv/sg.conf
3. /usr/openv/volmgr/bin/driver/sg.install
4. Check all drives can now be seen using sgscan tape.
4. On each media server, delete all drive definitions from the Media
Manager.
1. List Net Backup drive numbers using tpconfig -d
2. Delete each using tpconfig -delete -drive {n} e.g. tpconfig -delete
-drive 0.
5. ON each media server, delete all robot definitions from the Media
Manager.
1. List Net Backup robot numbers using tpconfig -d
2. Delete each using tpconfig -delete -robot {n} e.g. tpconfig -delete
-robot 0. 0 for gorilla, baboon, 1 for lemur, gibbon, grivet.
6. At this point vmglob -listall -java on any media server should
return nothing, indicating that the Global Device Database has been
synchronised after everything has been deleted. If not, try to delete
remaining entries manually using vmglob -delete -drive -name <DriveName>,
etc. - from the master server.
7. Get Net Backup to scan for all attached devices using tpautoconf -a.
Or use the GUI "Configure Storage Devices" wizard.
8. At this point tpconfig -d will show all devices with default names
e.g. DLT70001.
9. stopltid
10. ltid -v
11. Use the tpreq command to test mount as many tapes as possible, then
tpunmount to unmount them.
regards, Phil
Phil Weber
Egg plc, Senior UNIX Technologist
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu [
<mailto:veritas-bu-bounces at mailman.eng.auburn.edu>
mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon
Sent: 06 June 2006 06:18
To: 'veritas-bu at mailman.eng.auburn.edu'
Subject: [Veritas-bu] Netbackup Device Configuration problems :-(
Guys
After now removing all storage units for my old media servers that were
totally destroyed, I have installed NBU on the newly named media servers and
attempted to run the device configuration utility from my Master.
I have attempted to scan both new hosts but each one comes up with the
following message....
The error message reported is "Could not get device configuration. Cannot
discover devices. see the troubleshooting guide for details (44)." I
received an OK box.
When clicking this, the Device Configuration Wizard asks "Device discovery
failed on host Server001 do you wish to proceed - I say NO. Saying YES
brings up the 1st message and the device configuration fails to continue as
it cannot see the robot.
This occurs whether I scan a single host, multiple hosts or ALL 3 hosts
(Master as well).
Under Media & Device Management, Devices, Robots and hosts I can see entries
for SERVER001 and 002 - I wonder if someone has tried to configure the
devices, and its failed somewhere along the lines and now NetBackup cannot
understand what is happening?
Currently doing a backup of my SAN devices over LAN for now.....
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: Simon.Weaver at Astrium-eads.net
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate
or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England << File: ATT765405.txt >>
_____
Egg is a trading name of the Egg group of companies which includes:
Egg plc (reg no
2448340), Egg Financial Intermediation Ltd
(reg no 3828289), and Egg Banking plc (reg
no 2999842). Egg Banking plc and Egg
Financial Intermediation Ltd are authorised
and regulated by the Financial Services
Authority (FSA) and are entered in the FSA
register under numbers 205621 and 309551
respectively. These members of the Egg group
are registered in England and Wales.
Registered office: 1 Waterhouse Square, 138-
142 Holborn, London EC1N 2NA.
This e-mail is confidential and for use by
the addressee only. If you are not the
intended recipient of this e-mail and have
received it in error, please return the
message to the sender by replying to it and
then delete it from your mailbox. Internet e-
mails are not necessarily secure. The Egg
group of companies do not accept
responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to
avoid the transmission of viruses, it is the
responsibility of the recipient to ensure
that the onward transmission, opening or use
of this message and any attachments will not
adversely affect its systems or data. No
responsibility is accepted by the Egg group
of companies in this regard and the
recipient should carry out such virus and
other checks as it considers appropriate.
This communication does not create or modify
any contract.
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060606/0d26efe2/attachment.html
|
