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 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
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 SSO in NBU 5.1
All
I have 18 large Media Servers, all Win2k3, single TL with SSO and 12
drives. I tend to sort out most problems without bringing the whole lot
down.
When I do maintenance on the library, I shutdown all of the NBU Services
first, then power down the library.
Once the library is up, I then re-run device manager to scan for new
hardware, and the drives and library come into play on each Media
Server..... In most cases this can be done remotely. Once the server
sees the library, start the Master and then media servers and check
drive status. In almost all cases, everything has come up fine. Yes a
little pain, but its done in such an Art, it rarely takes that long to
do this task.
The one issue I had a problem with involved performing a scsi reset
while NetBackup was idle due to a drive in a complete mixed state that
could not recover from manually. (cant find the technote, but its a scsi
release command to be done on all affected drive(s)).
Apart from this, its mostly trouble free. If its working, I leave things
well alone. The environment is 5.1 and soon to be moved to 6.x and if
6.x is as better than 5.1, then I look forward to this upgrade to make
Admin Life easier. I agree, getting the right hardware and configuration
in place is a must.
S.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, January 30, 2008 4:23 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1
I agree with Randy, I've had a lot of issues with the Media/SAN Media
Windows servers. I would recommend that if you are pre 6.x, examine your
backup requirements for each server and use teaming (I have also
experienced problems with these) or Gig NICs when you can. Not only will
this solution save you money, but it will also save you administration
headache, regardless of Media server platform, when you do run into
problems.
-Rusty
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Randy
Samora
Sent: Wednesday, January 30, 2008 9:11 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1
NetBackup doesn't "get it" until version 6. I am 100% windows here with
a mixture of 19 Media and SAN Media servers sharing a library with 24
drives. First, stabilize it. Zone your library and make sure that the
only servers that can even see the library are servers that you want to
see the library. Check HBA settings and disable removable storage
service. Until you have the communication paths really stable between
servers and drives, the problems won't ever cease. But once you have it
stable, it typically will stay that way.
However, in version 5.1, whenever I had to do any type of maintenance on
my library causing it to lose connection to NetBackup servers, I had to
reboot all of my NetBackup servers before I could get NetBackup to see
the library again. My SAN Media servers are high profile servers and
rebooting them periodically wasn't a popular activity with our
customers. Microsoft said it wasn't Windows, Symantec said it wasn't
NetBackup and I could never get a straight answer. But 6.0 doesn't have
that problem. I can reboot the library all day long and as soon as it
is back on line, NetBackup is back on line.
Thanks,
Randy
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of X_S
Sent: Wednesday, January 30, 2008 8:02 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1
but would you implement such a large sso environment with Windows
servers? we've shared 20,30,40 drives across many windows servers and
it becomes hell whenever drives go offline and/or is replaced and then
shuffles in the os. we've used persistent binding but this doesn't help
with vtl drives. but sometimes, netbackup just doesn't get it.
+----------------------------------------------------------------------
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from
disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use
it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and
all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
________________________________
Notice to recipient:
The information in this internet e-mail and any attachments is
confidential and may be privileged. It is intended solely for the
addressee. If you are not the intended addressee please notify the
sender immediately by telephone. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to
be taken in reliance on it, is prohibited and may be unlawful.
When addressed to external clients any opinions or advice contained in
this internet e-mail are subject to the terms and conditions expressed
in any applicable governing terms of business or client engagement
letter issued by the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America,
N.A., London Branch and Banc of America Securities Limited are
authorised and regulated by the Financial Services Authority. For all
U.K. corporate disclosures, please refer to
www.bankofamerica.com/ukcompanies
<http://www.bankofamerica.com/ukcompanies>
________________________________
This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England_______________________________________________
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
