Title: Message
I previously
hadfour LTO2 drives in each of two librariesdo to a bad GBIC in a
switch, and several subsequent events, one drive wasn't visable, so my backup
server was only seeing 7 drives.
Last night, I
replaced the 8 portSun FC switches with a couple of Brocade
Title: Message
Hello Paul
Did you go thru the sgbuild process to rebuild the sg
entries.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
KeatingSent: Monday, January 23, 2006 9:30 AMTo:
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] anyone using
LTO3 with
[EMAIL PROTECTED] wrote on 01/23/2006
07:18:06 AM:
Netbackup version 5.1.4. Solaris 9 master/media server.
Our windows file server (win2003) backup has
just started taking a
very long time for the shadow copy components. Normally a 10
minute
backup is now taking over 5 hours. The backup of
Title: Message
Yep...sure did.
Thanks
though.
-Original Message-From: Len Boyle
[mailto:[EMAIL PROTECTED] Sent: January 23, 2006 10:59
AMTo: Paul Keating;
veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] anyone
using LTO3 with Solaris 8?
Hello Paul
Are you certain that you have the exact correct device strings?
I think if you do a
prtconf -vD | grep -A 1 inquiry-product-id
(Provided you have GNU grep)
You will see the product strings of all the devices, including the LTO-3.
Check that they match *exactly* what you have in st.conf.
I
Did you get the latest mappings.txt?
Here is the NB 6.0 version...
http://seer.support.veritas.com/docs/281082.htm
I think the wizard uses mappings.txt...
an updated st driver might do the trick
also patch 108725-22
for s2.8
Karl
Paul Keating
[EMAIL PROTECTED]
Sent by: [EMAIL
Hello All:
We are in the process of deploying a new library in our production NetBackup
environment. The current environment consists of a single NBU Master/Media
server (Windows 2000 NBU v5.1 MP4) ADIC Scalar 100 (DAS, with two LTO1
tape devices).
We will be migrating to an STK L700 with four
Gotcha.
Looks like I was following two different docs, and tripped myself up.
The initial doc reccommended going to /usr/openv/volmgr/bin/, making a
temp dir, and running ../sg.build from the temp dir, then running
../driver/sg.install...seems osmewhere along the way I ran the
sg.install
Title: Message
will changing the
storage unit in an incremental schedule in a policy be sufficient change
tocause the incrementals to backup everything on the
machine?
(need to change some
STUs in a schedule and don't want"fulls"to run
tonight)
I don't think so,
since if you use the
Only issue is when
autodiscovering via the wizard, under limitations, the LTO3 drives are
showing up as Yes, See limitations, and limitations says unable to
determine drive type.
That is definitely the mappings, make sure you have the very latest
downloaded.
William D L Brown
Title: Message
thanks.
-Original Message-From: Ambrose, Monte
[mailto:[EMAIL PROTECTED] Sent: January 23, 2006 3:42
PMTo: Paul Keating;
veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] policy
change.
Paul
It will not cause an
incremental to
Nope,
this will exclude *.zyz from /a/b/c/any_dir/*.zyz but not recursively
down from there.
I
think you're going to be stuck with a rather ugly:
/a/b/c/*/*.zyz
/a/b/c/*/*/*.zyz
/a/b/c/*/*/*/*.zyz
and so
forth...
Perhaps you could break the policy into two different ones, with two
Dont
forget, you may be able to use the inclusion list and have fewer keystrokes.
Of course this depends on how your directory structure is laid out. HTH
Thanks,
Rockey J. Reed
Lead Solutions Specialist
Consulting Services
Symantec Corporation
www.symantec.com
I am having a similar issue. I have a windows 2000 master and a pair of sun
480's with 8 LTO2 drives shared between them. I get External Event caused
rewind error and the tapes get frozen or the drives go down. I didn't have the
problem unti lI upgraded to 5.1 MP4. I have gone over the entire
14 matches
Mail list logo
