[Veritas-bu] unsubscribe

[Liddle, Stuart]

_
Stuart W. Liddle
Amgen Corp.
(805) 447-6062
fax: (805) 447-6725
[EMAIL PROTECTED]

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Help in using command line.

[Liddle, Stuart]

This is something that I am really surprised that Symantec/Veritas has not 
picked up on.

There needs to be a way of migrating from one backup platform to another.  For 
example, when migrating from one NetBackup master server to a new one there's 
really no good method for moving your old policies  clients to the new 
environment.  It's even more difficult to migrate from a completely different 
backup environment (like TSM or Legato) to NetBackup.

It sure would be nice to have a script to automatically put together the 
NetBackup policies from a flat file containing all of the information 
containing stuff like client names, paths, backup policy type, policy name, 
schedule names, etc and then generate the commands to create the policies in 
NetBackup.

Hey Symantec.are you listening?

--stuart liddle


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 2:09 PM
To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Help in using command line.

Anything that can be done in the NB GUI can be done via command line, usually 
faster (with the possible exception of cold building a policy and schedule 
set).  Netbackup is very extensible via command-line.  If it doesn't do what 
you want out of the box, you can probably script it.

That said, your request is a bit broad.  I have 250 custom scripts written for 
Netbackup and just burying you in them wouldn't make sense (plus at least half 
are specific to my environment).  I'd suggest starting with the command line 
reference guide here:

http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/279299.pdf
http://entsearch.symantec.com/search?p=Rsrid=S10%2d1lbc=symantecw=command%20line%20referenceurl=http%3a%2f%2fftp%2esupport%2everitas%2ecom%2fpub%2fsupport%2fproducts%2fNetBackup%5fEnterprise%5fServer%2f279299%2epdfrk=1uid=55146446sid=2ts=customrsc=vA22G2AUThIvfJNVed=edn%5f15143method=andaf=cat2%5fnetbackupproducts%3a15143%20cat1%3anetbackupproducts%20isort=scorefilter=entity%5fid%3a15143
..and just read it.  It's boring to read cover to cover but it's a great way to 
see all what's possible.

You also might just search the history of this mail list, I know many code 
snippets have been posted.

Good Luck.

I'll forward the pdf from my Veritas Vision presention on writing your own 
tools directly.  It was written when v4.5 was the top version but a lot of it 
is still applicable.

-M



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 1:45 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Help in using command line.
Hi
My company planning to migrate backup strategy from TSM to Netbackup. I am good 
in writing script in TSM but very bad in Netbackup. Do any body have command 
line examples or script i can use ?

THX

Anil Maurya
DCO  Backup/Recovery  team
Email : [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] How to backup 30TB of data

[Liddle, Stuart]

One wordNDMP.  Forget about doing it in a reasonable amount of time using 
CIFS.

Also, define reasonable time?

--stuart

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of King5899
Sent: Tuesday, September 25, 2007 2:46 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] How to backup 30TB of data


I have a new customer coming in that has 30 TB of SAN that they want to put 
behind 2 Windows servers acting as a clustered NAS Gateway.(Not my idea). The 
directory structure includes tens of millions of small images spread across 10 
of millions of directories. Currently they backup their windows servers at a 
rate of about 25 GB an hour, however the data could pass over the fiber network 
to the fiber tape drives. I am entertaining SAN snapshots, and backing up the 
snapshots from the backup server, but not sure if that is the best solution.

How would I possibly back this up in a reasonable time?

Any help would be appreciated.

MJK

+--
|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

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Script to label expired tapes in a VTL

[Liddle, Stuart]

I think I'm beginning to understand my confusion to some of the earlier 
comments and now see from the conversations that are taking place that the way 
we are using our VTL's is vastly different from the way that most of the 
respondents to this thread are using theirs.

Correct me if I'm wrong, but most of you have been describing the method for 
using your VTL's as one of what I'll call self-contained VTL's and that there 
is no real connection to the physical tapes.  In other words, in order to get 
data from the virtual tapes you have to use Vault or some other method of 
duplication to get the data off-site.  So, the tapes are always in the VTL and 
are re-cycled just as physical tapes are in a physical tape library.  Hence the 
need to delete and/or re-label.

We abandoned that method in favor of having our VTL's manage a partition of the 
physical tape library and have a direct link to the physical tapes.  In other 
words, a barcode in the virtual library is the same as a barcode on a physical 
tape.

So, for us, when a tape is full or we want to eject it and send it offsite, it 
gets cloned to physical tape and it's no longer visible to NetBackup in the 
virtual library.  But, we have set up our VTL to use a shadow pool where the 
virtual tape is still available until the VTL needs the space.  In some 
instances, the data can be available for up to 10 days.

If we need a tape for a restore, we just import it read-only from the shadow 
pool and inventory the virtual library in NetBackup and off we go.  When we are 
done, we just eject it from the virtual library and since it's already in sync 
with the physical tape, nothing more is required.

Now, this might sound messy from the standpoint that you don't know where the 
physical tape really is according to NetBackupas far as it knows, it's just 
not in the library and since you didn't use Vault, it's whereabouts are 
unknown.  In our experience this doesn't matter because we have a separate app 
to track our off-site tapes.

So, the whole discussion about re-labeling the virtual tapes is just an 
interesting discussion to me because we don't do that method.

--stuart

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston
Sent: Monday, September 24, 2007 12:15 PM
To: Paul Keating; Clem Kruger; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Script to label expired tapes in a VTL

The problem is not de-dupe; the problem is thin provisioning and 
oversubscription.  There are a lot of VTLs that allow both (with or w/o 
de-dupe), and if you define more tapes than you actually have disk, you will 
have this problem.  I'll concede that oversubscription is a natural state in a 
de-dupe VTL, as you define probably 20 times more tapes than you have real 
storage for.

The problem I see you're describing is this:
1. You define more tapes than you really have capacity for (again, this is 
normal in the de-dupe world)
2. You have a bunch that are partially full
3. You have a bunch that are in scratch, but have not been relabeled.
4. You may even have some that are brand new tapes that haven't been used at 
all.
5. You're out of real free space
6. Since NBU prefers to append rather than use a new tape, it will grab the #2 
tapes before the #3 tapes.  Had it grabbed the #3 tapes, it would have cleared 
the space they're taking up and you wouldn't have the problem, but that's not 
how NBU (or any other backup s/w) works.

Here's a thought.  Isn't there a way to tell NBU to mark tapes 
full/frozen/something after a backup?  If you did that, additional backups 
wouldn't append to those tapes, and you wouldn't have to worry about labeling.  
Would that work?

Of course, this whole labeling thing really isn't that big of a deal.  A simple 
shell script could handle it easy enough.

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies

-Original Message-
From: Paul Keating [mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 9:34 AM
To: Curtis Preston; Clem Kruger; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Script to label expired tapes in a VTL

Not entirely true, Curtis.

When your virutal tape expires, the VTL has no way of knowing this
untill the tape is written to again.
Depending on the VTL, this may be too late.

I've got about 2TB of free space on my VTL, and about 1000 scratch VTs
(2800 total).

After a couple of weeks of Netbackup using and expiring VTs, The VTs are
going back to Scratch, but untill they're re-written, the pointers in
the repository still exist, therefore the VTL thinks the space is still
in useso if you're using a de-duping VTL (or DSU to a de-duping FS)
and you're only doing real time freeing of space  (ie, re-labelling a
VT only when you re-write it, or letting NBU delete images from the DSU
only as the DSU approaches a high disk utilization threshold), then your
target will need to do 

Re: [Veritas-bu] Script to label expired tapes in a VTL

[Liddle, Stuart]

Curtis,

Yes, that is correct.  I am remembering all of the PAIN associated with having 
NetBackup Vault make copies to physical tape.  It went something like this:

1) do the backup to VTL
2) vault images from VTL to physical tape
3) keep track of the stuff that has been vaulted and then expire images
4) once all images on a tape have been expired, then do a bpexpdate 
-deassignempty on a virtual tape (which, by the way, Symantec told us there 
was a rare, but fatal bug with this method).
5) try to keep Vault running ahead of the backups so that there would be enough 
virtual tapes available to use for backups
6) rerun failed vault jobs to allow for proper image expiration
7) repeat steps 1 through 6 several times

Agghhh the pain!!!

-Original Message-
From: Curtis Preston [mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 3:56 PM
To: Liddle, Stuart; Paul Keating; Clem Kruger; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: Re: [Veritas-bu] Script to label expired tapes in a VTL

I think you nailed it, Stu.  I remember your previous posts on this topic, and 
that you said you went to this method because the NBU Vault method wasn't 
duping the tapes fast enough for you.  As I recall, it was because your backups 
had millions of files in them, and this was slowing down your dupe process.  
You went to the tape-out functionality of your VTL because it made the copies 
faster (significantly so), and were willing to live with any downsides because 
it made the copies possible.

You are correct.  Most people do not use their VTLs this way.  Part of the 
reason is a good amount of FUD put out by the backup vendors.  Another reason 
is that it does come with some major downsides.  In your case, you had to 
choose which downsides were worse, and in your case, the downside of not 
getting the copies done at all was unacceptable, so you decided to deal with 
the downsides of the other method.

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies

-Original Message-
From: Liddle, Stuart [mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 4:55 PM
To: Curtis Preston; Paul Keating; Clem Kruger; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: Re: [Veritas-bu] Script to label expired tapes in a VTL

I think I'm beginning to understand my confusion to some of the earlier 
comments and now see from the conversations that are taking place that the way 
we are using our VTL's is vastly different from the way that most of the 
respondents to this thread are using theirs.

Correct me if I'm wrong, but most of you have been describing the method for 
using your VTL's as one of what I'll call self-contained VTL's and that there 
is no real connection to the physical tapes.  In other words, in order to get 
data from the virtual tapes you have to use Vault or some other method of 
duplication to get the data off-site.  So, the tapes are always in the VTL and 
are re-cycled just as physical tapes are in a physical tape library.  Hence the 
need to delete and/or re-label.

We abandoned that method in favor of having our VTL's manage a partition of the 
physical tape library and have a direct link to the physical tapes.  In other 
words, a barcode in the virtual library is the same as a barcode on a physical 
tape.

So, for us, when a tape is full or we want to eject it and send it offsite, it 
gets cloned to physical tape and it's no longer visible to NetBackup in the 
virtual library.  But, we have set up our VTL to use a shadow pool where the 
virtual tape is still available until the VTL needs the space.  In some 
instances, the data can be available for up to 10 days.

If we need a tape for a restore, we just import it read-only from the shadow 
pool and inventory the virtual library in NetBackup and off we go.  When we are 
done, we just eject it from the virtual library and since it's already in sync 
with the physical tape, nothing more is required.

Now, this might sound messy from the standpoint that you don't know where the 
physical tape really is according to NetBackupas far as it knows, it's just 
not in the library and since you didn't use Vault, it's whereabouts are 
unknown.  In our experience this doesn't matter because we have a separate app 
to track our off-site tapes.

So, the whole discussion about re-labeling the virtual tapes is just an 
interesting discussion to me because we don't do that method.

--stuart

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston
Sent: Monday, September 24, 2007 12:15 PM
To: Paul Keating; Clem Kruger; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Script to label expired tapes in a VTL

The problem is not de-dupe; the problem is thin provisioning and 
oversubscription.  There are a lot of VTLs that allow both (with or w/o 
de-dupe), and if you define more tapes than you actually have disk, you will 
have this problem.  I'll

Re: [Veritas-bu] Script to label expired tapes in a VTL

[Liddle, Stuart]

Clem,

You have made a rather curious comment.  You don't have to delete the tape to 
get the space returned.  (My experience is with the NetApp VTL.)  There are 
settings on the VTL that you can set to allow for how long you keep a virtual 
tape in the shadow pool once it has been cloned to physical tape.

If you are not cloning to physical tape and are just keeping images on virtual 
tape, then you would not be deleting the tapes, you would be expiring 
images...just like Curtis said about the DSU.

That's one of the nice features of the NetApp VTL.  If you have the disk space, 
as long as you have cloned to physical tape it will keep the virtual tapes 
around until the VTL needs to free up space for newer backups.  It does this 
for you automatically!

--stuart


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clem Kruger
Sent: Saturday, September 22, 2007 2:33 AM
To: Curtis Preston; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Script to label expired tapes in a VTL


Hi Curtis,



You have to delete the tape to get your space returned. This is the real pain 
and cost



Clem.



-Original Message-
From: Curtis Preston [mailto:[EMAIL PROTECTED]mailto:%5bmailto:[EMAIL 
PROTECTED]
Sent: 22 September 2007 11:15 AM
To: Clem Kruger; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Script to label expired tapes in a VTL



And you don't get the space back on a DSU until you expire the image.

So what?  I also argue that what Steve is asking for isn't necessary.

(I think he's MAKING it necessary by oversubscribing, but that's not the

VTL's fault.)



Oversubscription aside, once his tapes are expired, the space taken up

by those tapes is immediately available for reuse.  The next time the

tape gets written to, it will delete all pointers to the space taken up

by that tape.



As to the VTL vs disk debate, I still think you should bring in all disk

devices and let them duke it out before excluding an entire category of

them.  You're going to exclude a lot of really good products if you just

no VTLs.



Remember that saying I don't want a VTL but I do want de-dupe means

that you're going to use NAS.  While that will meet a whole lot of needs

for a whole lot of people, there's also some really big backups that

need a lot more than you can push over IP.  For those backups, you're

going to want a block transfer protocol (i.e. SCSI), and for that,

you're currently going to be buying a VTL.  (Unless you're just going to

buy a non-deduped disk in which case I'd say you're REALLY wasting your

money.)



---

W. Curtis Preston

Backup Blog @ www.backupcentral.com

VP Data Protection, GlassHouse Technologies

-Original Message-

From: [EMAIL PROTECTED]

[mailto:[EMAIL PROTECTED] On Behalf Of Clem

Kruger

Sent: Saturday, September 22, 2007 4:24 AM

To: VERITAS-BU@mailman.eng.auburn.edu

Subject: Re: [Veritas-bu] Script to label expired tapes in a VTL



Hi Steve,



This is the downer on VTL's. You do not get your tape space back

automatically. It is for these reasons I recommend that one never go

VTL's. NetBackup 6.0 and 6.5 allow disk to disk backups; the images are

easily replicated to an offsite facility.



The time for all tape has come and gone. The de-duplication facility

in 6.5 makes life even easier. Why VTL's (which does SCSI emulation)

when you and use disk which is faster and has more protection?



Clem.



-Original Message-

From: [EMAIL PROTECTED]

[mailto:[EMAIL PROTECTED] On Behalf Of swaltner

Sent: 21 September 2007 17:32 PM

To: VERITAS-BU@mailman.eng.auburn.edu

Subject: [Veritas-bu] Script to label expired tapes in a VTL





We deployed a VTL last month, which has been working very nicely. This

is in a NetBackup 5.1 environment with the VTL attached to our Solaris

based master server as well as to our NAS server for local NDMP backups.

One thing I'd like to do is over-subscribe on the back-end storage, but

before I do that I'd like to automate the process of freeing up the disk

space used in the VTL when a NetBackup tape is expired. Just curious if

anyone has already written such a beast and would like to share with me

as a starting point.



If not, I suspect I'll use the following logic:



- Every day (at noon??), query the robots defined in the VTL and keep a

record of tapes that are allocated.

- When a tape goes from allocated to non-allocated from one day to the

next, use a command like the following to erase the tape's contents:

bplabel -erase -o -d dlt -m VTL123



This would write a small label at the beginning of the virtual tape,

causing the VTL to drop all the other data that had been stored on the

tape.



Any reason this wouldn't work? Any gotchas with writing this script that

I should look out for?



Steve



+--

|This was sent by [EMAIL PROTECTED] via Backup Central.

|Forward SPAM 

Re: [Veritas-bu] Full Media

[Liddle, Stuart]

The bpmedialist command will only tell you part of the story.  It won't tell 
you whether or not the FULL tape is actually in the library or not.

The best way is to run the available media report which is found at:
/usr/openv/netbackup/bin/goodies/available_media.
Not only does the report tell you which media are full, but it will also tell 
which full ones are still in the library.  So, run the report out of cron and 
save the output to a file and just grep for FULL and TLD (or whichever library 
type you have).

--Stuart

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz
Sent: Thursday, September 20, 2007 7:04 AM
To: Martin, Jonathan
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Full Media

Yes,

/usr/openv/netbackup/bin/admincmd/bpmedialist | grep -B1 FULL

On Thu, 20 Sep 2007, Martin, Jonathan wrote:

 Is there a media full flag I can parse via the command line?  I'm
 working on a script for a remote site who only wants to remove full
 media from the box.  I can guestimate based on how much data is on the
 media but when NBU gets to the end of a media, does it flag it anywhere?

 Thanks,

 -Jonathan

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup upgrade 6 or 6.5

[Liddle, Stuart]

Yes, but if you want to back up Exchange 2007, then you will want to use 
NetBackup 6.5.  NetBackup 6.0 does not have support for Exchange 2007.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 9:11 AM
To: [EMAIL PROTECTED]
Cc: veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED]
Subject: Re: [Veritas-bu] Netbackup upgrade 6 or 6.5


I would recommend upgrading to 6.0MP4 first, and get that working.
Let 6.5 stabilize for awhile before making that plunge.  6.5 was just released.


=
Carl Stehman
IT Distributed Services Team
Pepco Holdings, Inc.
202-331-6619
Pager 301-765-2703
[EMAIL PROTECTED]

Dave Markham [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]

09/20/2007 11:19 AM
Please respond to
[EMAIL PROTECTED]


To

veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu

cc



Subject

[Veritas-bu] Netbackup upgrade 6 or 6.5










Has anyone got 6.5 yet? We are running NBU 5.0 MP7 on a predomintatly
solaris platform. We are due to upgrade h/w and s/w and i was wondering
was it worth going for 6.0 which seems to be used quite a bit by people
now, or do we go to new 6.5 ?

Also we have around 20 servers including a 2 node Sun Cluster ( attached
to T3 arrays ) running oracle10g. Is there anything special which can be
done with 6.5 or is it just worth still doing filesystem backups direct
to Tape

Thanks
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



This Email message and any attachment may contain information that is 
proprietary, legally privileged, confidential and/or subject to copyright 
belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is 
intended solely for the use of the person(s) to which it is addressed. If you 
are not an intended recipient, or the employee or agent responsible for 
delivery of this Email to the intended recipient(s), you are hereby notified 
that any dissemination, distribution or copying of this Email is strictly 
prohibited. If you have received this message in error, please immediately 
notify the sender and permanently delete this Email and any copies. PHI 
policies expressly prohibit employees from making defamatory or offensive 
statements and infringing any copyright or any other legal right by Email 
communication. PHI will not accept any liability in respect of such 
communications.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Script to see skipped files

[Liddle, Stuart]

Dave wrote the following in response to this thread:

 

If unix

 

bperror -backstat -hoursago 24 -U | grep ^  1 | awk '{print $2'} | sort -u
| while read CLIENT; 

do bperror -problems -hoursago 24 -client $CLIENT -columns 200 -U; 

done

 

 

Dave

 

 

You could also use the following:

 

bperror -all -problems -backstat -hoursago 24 | awk ' $19 == 1 {print $6,
$19, $12, $14, $16}' | awk '{print $3}' | sort -u | xargs -i bperror
-problems -hoursago 24 -client {} -columns 200 -U

 

OR

 

 

For an individual jobid:  cat /usr/openv/netbackup/db/jobs/trylogs/jobid.t
| grep ^LOG

 

 

 

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lawler,
Michael C.
Sent: Thursday, September 13, 2007 6:11 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Script to see skipped files

 

 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NDMP Multiplexing?

[Liddle, Stuart]

NONDMP is never multiplexed...only one stream to a tape drive at a time.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin,
Jonathan
Sent: Thursday, August 30, 2007 11:14 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] NDMP Multiplexing?

I read the previous doc from this forum on Multistreaming NDMP /
Manually adding NEW_STREAM s but can you multiplex NDMP?

Thanks,

-Jonathan

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Maximum number of policies

[Liddle, Stuart]

Yeswe have a policy naming convention:

SiteCode-BusinessUnit-ServiceTier-Dataset-Component

For example, we might have a policy called:

usto-core-std-exchange-app

Which is a backup policy for the Exchange servers.  It's a Standard tier
backup, meaning it get's daily backups retained for 1 week (on site) and
weekly backups retained for 30 days (sent off-site).

Another policy:

usto-dev-val-gnltst-db

is a backup of the gnltst database that is done as a Value tier backup
which is done weekly and retained for 6 weeks (off-site).  (All database
backups are done from snapshots.  We don't use bpstart/bpend scripts to do
the cold backupsthe DBA's have scripts to shut down and snapshot the
databases.)

The premium tier backups are daily fulls and all copies are sent off-site.










-Original Message-
From: Curtis Preston [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 23, 2007 11:01 PM
To: Justin Piszcz; Liddle, Stuart
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Maximum number of policies

If you have a policy naming convention (and you'd better for that many
policies), configuring things like exclude lists is no more difficult with
70 than with 7.  I'd actually argue that it's the other way around.

I blogged about this a while back, and was surprised at the positive support
I got:

http://www.backupcentral.com/content/view/51/47/

For exclude lists, I use a script anyway, as I like to push out a standard
from the master, so 10 policies, 1 policies, whatever. ;)

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Piszcz
Sent: Monday, July 23, 2007 4:03 PM
To: Liddle, Stuart
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Maximum number of policies

For example utilize include/exclude lists on the lists or find _some_ way 
to group the clients together, no?

On Mon, 23 Jul 2007, Justin Piszcz wrote:

 I retract my statement.  Some environments could have a good use for that 
 many polices I suppose..

 On Mon, 23 Jul 2007, Liddle, Stuart wrote:

 AhI see.
 
 So, Justin, you have some special insight about everyone's backup
 environment and business requirements that allows you to come up with a
 blanket statement like that?
 
 
 
 -Original Message-
 From: Justin Piszcz [mailto:[EMAIL PROTECTED]
 Sent: Monday, July 23, 2007 1:52 PM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
 Veritas-bu@mailman.eng.auburn.edu
 Subject: Re: [Veritas-bu] Maximum number of policies
 
 Whoever has that many polices has some mental issues.
 
 On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote:
 
 I thought this pic would be appropriate for us ...
 
 
 
 
 
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Liddle,
 Stuart
 Sent: Monday, July 23, 2007 2:48 PM
 To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada';
 Veritas-bu@mailman.eng.auburn.edu
 Subject: Re: [Veritas-bu] Maximum number of policies
 
 
 
 yes just over 1100 policiesit's not quite 1 client per policy as
 Curtis Preston suggests.  What we have done is to have a policy for a
given
 dataset.  For example, we have two exchange policies one has 13 exchange
 servers in it and the other has 10.  The reason we have two is because
they
 are in different datacenters and we have a media server in each
datacenter.
 
 
 
 Most of our policies actually do have only one client per policy, but
 because we are creating policies by dataset, we will have some that have
 more than one client.
 
 
 
 --stuart
 
 
 
 
 
 From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED]
 Sent: Sunday, July 22, 2007 11:20 PM
 To: 'Liddle, Stuart'; 'Edson Noboru Yamada';
 Veritas-bu@mailman.eng.auburn.edu
 Subject: RE: [Veritas-bu] Maximum number of policies
 
 
 
 1,100 policies!!
 
 
 
 
 
 Regards
 
 Simon Weaver
 3rd Line Technical Support
 Windows Domain Administrator
 
 EADS Astrium Limited, B23AA IM (DCS)
 Anchorage Road, Portsmouth, PO3 5PU
 
 Email: [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]

 -Original Message-
 From: Liddle, Stuart [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 20, 2007 2:59 PM
 To: WEAVER, Simon (external); 'Edson Noboru Yamada';
 Veritas-bu@mailman.eng.auburn.edu
 Subject: RE: [Veritas-bu] Maximum number of policies

 Hi,
 
 

 we are running NB 5.1 MP6 with around 1100 policies and over 1600
 clients.  We have been having problems with the scheduler not starting
 things when they are supposed to start.  The one thing that is very
 important is to have the proper settings in the /etc/system file for
shared
 memory.  If you don't have this set correctly

Re: [Veritas-bu] Maximum number of policies

[Liddle, Stuart]

Yeahwe realize that NB 6.x is a total re-write of the scheduler...we
can't wait to upgrade.  But we have to wait for all of the clients that we
backup to upgrade to 5.1 before we can upgrade the master/media servers to
6.x.

 

We are really looking forward to that problem being fixed.

 

--stuart

 

  _  

From: Dominik Pietrzykowski [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 23, 2007 3:47 AM
To: WEAVER, Simon (external); 'Liddle, Stuart'; 'Edson Noboru Yamada';
Veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Maximum number of policies

 

 

Just to add to Stuart's comment, NB6 reads policies according to refresh
rate and when policies change. These are done by nbpem.

You can also refresh manually, via command or restart of NB (not the best
way to do this)

 

Some handy hints:

 

- For those who do not know there is a setting for policy refresh on the
master, default is 10min I think ? (host properties/master/global attr)

 

- Manual refresh can be done via : nbpemreq -updatepolicies

 

- This touch file stops nbpem doing refreshes unless you issue the nbpemreq
command : /usr/openv/netbackup/bin/PolicyStrategy

 

 

 

 

  _  

From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] 
Sent: Monday, 23 July 2007 4:20 PM
To: 'Liddle, Stuart'; 'Edson Noboru Yamada';
Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Maximum number of policies

 

1,100 policies!!

 

 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email:  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

-Original Message-
From: Liddle, Stuart [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 20, 2007 2:59 PM
To: WEAVER, Simon (external); 'Edson Noboru Yamada';
Veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Maximum number of policies

Hi,

 

we are running NB 5.1 MP6 with around 1100 policies and over 1600 clients.
We have been having problems with the scheduler not starting things when
they are supposed to start.  The one thing that is very important is to have
the proper settings in the /etc/system file for shared memory.  If you don't
have this set correctly, you WILL have problems with the scheduler.

 

We had a case open with Symantec/Veritas about this and basically we were
told that it would be best to upgrade to 6.x because the scheduler has been
completely re-written and is much more efficient.  We hope to upgrade to 6.5
later this year.  In the mean time we have to figure out creative ways to
deal with the problems of the scheduler getting bogged down.

 

I believe that you should not have problems with only 100 policies if you
have your memory settings correct in /etc/system.

 

good luck.

 

--stuart

 


  _  


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER,
Simon (external)
Sent: Friday, July 20, 2007 6:42 AM
To: 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Maximum number of policies

 

Hi

Well I know of a site that had 120 policies, but never reported an issue.
Although its alot, I am not personally aware of any recommendation that
states what the limit should be.

 

Are you sure the frequency is right and the policy is enabled correctly ?

 

If at all possible, can you consolidate any of your existing policies and
merge them ?

 

 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email:  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru
Yamada
Sent: Friday, July 20, 2007 11:43 AM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Maximum number of policies


Hi

I have an NBU 5.1 installation with one master server (Solaris 9) and 6
media servers (RHEL4, Windows 2003).

I´ve just created the 101st policy. The problem I´m running into is that
apparently the scheduler is simply ignoring 
the backup window configured (it was supposed to start at 8pm but the job
only is added to the queue around 2am).

My question is: NBU 5.1 may have some kind of 100 policies limitation? Has
anyone here with more than 100 policies/classes in place? 

Thank you


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

Re: [Veritas-bu] Maximum number of policies

[Liddle, Stuart]

yes just over 1100 policiesit's not quite 1 client per policy as Curtis
Preston suggests.  What we have done is to have a policy for a given
dataset.  For example, we have two exchange policies one has 13 exchange
servers in it and the other has 10.  The reason we have two is because they
are in different datacenters and we have a media server in each datacenter.

 

Most of our policies actually do have only one client per policy, but
because we are creating policies by dataset, we will have some that have
more than one client.

 

--stuart

 

  _  

From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 22, 2007 11:20 PM
To: 'Liddle, Stuart'; 'Edson Noboru Yamada';
Veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Maximum number of policies

 

1,100 policies!!

 

 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email:  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

-Original Message-
From: Liddle, Stuart [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 20, 2007 2:59 PM
To: WEAVER, Simon (external); 'Edson Noboru Yamada';
Veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Maximum number of policies

Hi,

 

we are running NB 5.1 MP6 with around 1100 policies and over 1600 clients.
We have been having problems with the scheduler not starting things when
they are supposed to start.  The one thing that is very important is to have
the proper settings in the /etc/system file for shared memory.  If you don't
have this set correctly, you WILL have problems with the scheduler.

 

We had a case open with Symantec/Veritas about this and basically we were
told that it would be best to upgrade to 6.x because the scheduler has been
completely re-written and is much more efficient.  We hope to upgrade to 6.5
later this year.  In the mean time we have to figure out creative ways to
deal with the problems of the scheduler getting bogged down.

 

I believe that you should not have problems with only 100 policies if you
have your memory settings correct in /etc/system.

 

good luck.

 

--stuart

 


  _  


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER,
Simon (external)
Sent: Friday, July 20, 2007 6:42 AM
To: 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Maximum number of policies

 

Hi

Well I know of a site that had 120 policies, but never reported an issue.
Although its alot, I am not personally aware of any recommendation that
states what the limit should be.

 

Are you sure the frequency is right and the policy is enabled correctly ?

 

If at all possible, can you consolidate any of your existing policies and
merge them ?

 

 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email:  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru
Yamada
Sent: Friday, July 20, 2007 11:43 AM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Maximum number of policies


Hi

I have an NBU 5.1 installation with one master server (Solaris 9) and 6
media servers (RHEL4, Windows 2003).

I´ve just created the 101st policy. The problem I´m running into is that
apparently the scheduler is simply ignoring 
the backup window configured (it was supposed to start at 8pm but the job
only is added to the queue around 2am).

My question is: NBU 5.1 may have some kind of 100 policies limitation? Has
anyone here with more than 100 policies/classes in place? 

Thank you


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

 

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

Re: [Veritas-bu] Maximum number of policies

[Liddle, Stuart]

Hi,

 

we are running NB 5.1 MP6 with around 1100 policies and over 1600 clients.
We have been having problems with the scheduler not starting things when
they are supposed to start.  The one thing that is very important is to have
the proper settings in the /etc/system file for shared memory.  If you don't
have this set correctly, you WILL have problems with the scheduler.

 

We had a case open with Symantec/Veritas about this and basically we were
told that it would be best to upgrade to 6.x because the scheduler has been
completely re-written and is much more efficient.  We hope to upgrade to 6.5
later this year.  In the mean time we have to figure out creative ways to
deal with the problems of the scheduler getting bogged down.

 

I believe that you should not have problems with only 100 policies if you
have your memory settings correct in /etc/system.

 

good luck.

 

--stuart

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER,
Simon (external)
Sent: Friday, July 20, 2007 6:42 AM
To: 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Maximum number of policies

 

Hi

Well I know of a site that had 120 policies, but never reported an issue.
Although its alot, I am not personally aware of any recommendation that
states what the limit should be.

 

Are you sure the frequency is right and the policy is enabled correctly ?

 

If at all possible, can you consolidate any of your existing policies and
merge them ?

 

 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email:  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru
Yamada
Sent: Friday, July 20, 2007 11:43 AM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Maximum number of policies


Hi

I have an NBU 5.1 installation with one master server (Solaris 9) and 6
media servers (RHEL4, Windows 2003).

I´ve just created the 101st policy. The problem I´m running into is that
apparently the scheduler is simply ignoring 
the backup window configured (it was supposed to start at 8pm but the job
only is added to the queue around 2am).

My question is: NBU 5.1 may have some kind of 100 policies limitation? Has
anyone here with more than 100 policies/classes in place? 

Thank you

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

Re: [Veritas-bu] bpdbjobs -all_columns

[Liddle, Stuart]

OK...I find this useful:

 

cat bin/jobsac

#!/bin/sh

# use bpdbjobs -all_columns to capture the following:

#jobid, status, policy, schedule, client, path

#

 

# handle the command line argument

case $# in

 0) BACKUPSERVER=`hostname`

;;

 

 1) echo $1

BACKUPSERVER=$1

;;

 

 *) BACKUPSERVER=`hostname`

;;

esac

echo BACKUPSERVER= ${BACKUPSERVER}

 

/usr/openv/netbackup/bin/admincmd/bpdbjobs -all_columns -M ${BACKUPSERVER}|
cut -d, -f1-34 | awk -F, '{print $1, $4, $5, $6, $7, $33}'

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Piszcz
Sent: Friday, July 20, 2007 3:21 AM
To: Clooney, David
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] bpdbjobs -all_columns

 

 

 

On Fri, 20 Jul 2007, Clooney, David wrote:

 

 Hi All

 

 

 

 Does anyone have some perl code, that they wouldn't mind sharing, that

 chops up  bpdbjobs -report -all_columns, with filelist count , number of

 tries etc,?

 

 

After field 31 its difficult to calculate if anyone has something like 

this I would be interested as well.

 

Justin.

___

Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu

http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Backup Exchange 2007

[Liddle, Stuart]

Here's what we have heard:

 

NetBackup 6.5 GA does support Exchange 2007 in the same manner as 5.1 is
currently supporting the older version of Exchange servers - on a basis of
backing up the databases.  

 

When 6.5 MP1 is released, NetBackup will support single mailbox recovery
(new), however, this also has implications on how the backups occur and
could cause the backups to take longer. 

 

 

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sekhon
Simrat S.
Sent: Friday, July 13, 2007 6:11 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Backup Exchange 2007

 

Guys, how is everybody backing up Exchange 2007? I understand that that
NB6.5 will have the capability. 

Any suggestions will be appreciated.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] same job keeps hanging.

[Liddle, Stuart]

So, are you trying to back up a filesystem with lots and lots of small
files?  If so, remember that NetBackup will try to enumerate all of the
files that you are trying to back up.  We had a similar situation where we
were trying to back up a filesystem with 3.5 million files in 50,000
directories.  It took hours to do a filelist of all of thatconsequently,
it timed out. 

 

 

Symantec told us the best solution for that particular directory was NDMP
(since the timeouts are much longer).

 

 

OR...I suppose you could up the timeout value to more than 3600 seconds and
see what happens.

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron Mills
Sent: Monday, July 09, 2007 9:58 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] same job keeps hanging.

 

Hi all,

 

I'm hoping someone's seen this before. I'm running 5.1MP6 w/ AIT3 - I've got
a ~126GB backup that kicks off weekly, but hangs within a few hours every
time - the error I get is always media manager terminated by parent
process but the logs don't seem to show anything odd. No other backups hang
like this. This is also the only job that runs on the server itself.

 

bptm gives me:

 

03:28:45.470 [4999] 2 io_ioctl: command (1)MTFSF 1 from (bptm.c.8307) on
drive index 1

03:28:45.530 [4999] 2 io_close: closing
/usr/openv/netbackup/db/media/tpreq/AK6503, from bptm.c.8310

03:28:45.530 [4999] 2 catch_signal: EXITING with status 82

 

so I check bpbrm:

 

02:05:33.882 [4992] 2 bpbrm spawn_child: /usr/openv/netbackup/bin/bptm
bptm -w -c foo.bar.com -den 17 -rt 6 -rn 0 -stunit Spectra2 -cl inbound -bt
1183968330 -b foo.bar.com _1183968330 -st 0 -cj 1 -p inbound -hostname
foo.bar.com -ru root -rclnt foo.bar.com -rclnthostname foo.bar.com -rl 5 -rp
8035200 -sl ftpif -ct 0 -maxfrag 1048576 -tir -v -Z -mediasvr foo.bar.com
-jobid 117926 -jobgrpid 117926 -masterversion 51 -shm

02:05:33.884 [4992] 2 bpbrm write_continue_backup: wrote CONTINUE BACKUP
on COMM_SOCK 4

02:05:33.884 [4992] 2 bpbrm main: wrote /na270/pub/inbound on COMM_SOCK

02:05:33.884 [4992] 2 bpbrm main: wrote /na270/pub/ftp on COMM_SOCK

02:05:33.884 [4992] 2 bpbrm main: wrote CONTINUE on COMM_SOCK

02:05:33.885 [4992] 2 bpbrm main: ESTIMATE -1 -1 nbu0 foo.bar.com
_1183968330

02:09:44.763 [4992] 2 bpbrm mm_sig: received ready signal from media
manager

02:09:44.763 [4992] 2 bpbrm readline: retrying partial read from fgets ::

03:27:22.261 [4992] 2 bpbrm sighandler: signal 14 caught by bpbrm

03:27:22.272 [4992] 2 bpbrm sighandler: bpbrm timeout after 3600 seconds

03:27:22.287 [4992] 2 clear_held_signals: clearing signal mask stack,
mask_stack_depth = 0

03:27:22.287 [4992] 2 bpbrm kill_child_process: start

03:27:22.287 [4992] 2 bpbrm wait_for_child: start

03:28:48.546 [4992] 2 bpbrm wait_for_child: child exit_status = 82
signal_status = 0

03:28:48.557 [4992] 2 inform_client_of_status: INF - Server status = 41

 

but I can't seem to figure out why there was a timeout. I checked all the
related logs - bpbkar just shows file writing stopping at 2:42am - like the
process just hangs there, no errors though. Looking right now, the bpbrm and
bpbkar processes for this backup are still running, but nothing is
happening. The job shows as active and everything is queueing up behind it.
I've also adjusted the CLIENT_READ_TIMEOUT in /usr/openv/netbackup/bp.conf
to no avail.

 

Can anyone point me in the right direction as to what I'm missing? I'm
guessing there's something I'm not seeing in one of the logs.

 

-Aaron

 

Aaron Mills

Systems Administrator

Return Path, Inc.

http://www.returnpath.net

[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 

 

 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] calculating backup success rate

[Liddle, Stuart]

use a reporting tool like Bocada.  It will do that for you.  And, if a
backup fails 3 tmes and then succeeds, it's considered successful.  (I would
want to know what happened on those 3 failed attempts so that I could take
some corrective action though).

 

--stuart

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hindle, Greg
Sent: Monday, June 04, 2007 5:57 AM
To: NB List Mail
Subject: [Veritas-bu] calculating backup success rate

 

How does everyone track this? Do you count just total successfully backups
vs. the number of attempts? And how do you handle a backup that failed 3
times but ran good on the forth?

 

Greg 

 This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for
the
addressee.  If you are not the intended recipient, do not use the
information
in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Newbie to Netbackup using VTL

[Liddle, Stuart]

OKso now I have to disagree with Curtis on his disagreement

We tried using Vault with both preserving of Multiplexing and doing
de-multiplexing on the vault copies.  In both cases, we did not get very
good throughput.  Most of my time was spent trying to balance the amount of
space on the VTL's that had not yet been vaulted.  We also found that when
you have an image consisting of lots of small files, it will be slower than
if you have a few very large files (like database files).  

When stuff did get vaulted, we had to bpexpdate the images on the VTL's to
free up space for the ever-increasing amount of backups coming in.
Symantec/Veritas had people helping us with this issue for weeks before we
finally gave up and went with the Direct Tape Copy cloning method built
into the NetApp VTL's (good stuff).

We were having a terrible time with trying to get Vault to keep ahead of the
data coming in for backups to the VTL'sand that was before we had fully
migrated all of our legacy backup systems to our new environment.  We had to
have scripts to keep track of what we could bpexpdate off of the VTL to make
room for backups.

Yes, we realize that NetBackup does not really know about the true
location of the tapes that we clone using the Direct Tape Copy method.  And
we had to partition our physical tape library to accommodate this approach.
But this was a small price to pay for the problems we encountered using
Vault.  And, I would happily deal with this  rather than have to worry about
whether or not an older backup was successfully Vauted or not or if I have
enough space on my VTL.

Right now our monitoring of the VTL's consists of checking on available
tapes and assigning new ones when they get low.  We have a script that eject
full tapes from the VTL's hourly and active tapes once a day.  The eject is
what triggers the cloning to physical tape.  There are some other issues
that we've had to deal with on the VTL's, but all are minor compared to what
we used to have.

And, yes, it's also true that it might be inefficient in the tape use
because of the way the VTL allocates space for the virtual tapeagain, a
small price to pay.

Still doing upwards of 200TB/week  approaching 1 Petabyte/month.

--stuart

-Original Message-
From: Curtis Preston [mailto:[EMAIL PROTECTED] 
Sent: Sunday, May 13, 2007 10:58 PM
To: Liddle, Stuart; [EMAIL PROTECTED];
VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Newbie to Netbackup using VTL

Stuart Liddle said:
NODon't use Vault to duplicate from VTL to physical tape!!!

Looks like it's my week to disagree with you, Stuart. 
(Sorry.  I love ya' man!)

We tried this, and in NB 5.1 MP6, Vault is a HOG!!  We were not able to
Keep the drives spinning fast enough using Vault.  The best speeds we
saw going to physical tape using vault was maybe 30MB/sec.  Usually we
got 
around 10MB/sec or lesswhich is definitely not a good thing.

I've been able to get Vault to go MUCH faster than that. I would say
there are keys to doing it right.  The biggest one I see is that you
should either use multiplexing or not.  Don't mpx to tape (or virtual
tape) and then de-mpx when you copy.  VTL will suck just as bad as
regular tape when you do that.  So either preserve mpx when you dupe, or
don't mpx to your VTL (better).  Another key is having enough I/O
bandwidth in the media server to pull it off.

What we ended up doing was using the built-in feature of our NetApp VTL
to
do the cloning of the virtual tape to physical tape.  Now we are
getting
much better performance of around 50 - 60 MB/sec.

Glad it got better. ;)

The problem is that Vault has way too much overhead in doing the
copying of
the data.

Again, I have to disagree.

With the built in cloning function of the VTL, you just connect the two
firehoses together and the data gets written from virtual tape to
physical
tape.

There are also limitations to this approach.  While it removes the I/O
from the media server, you get a lot of wasted media if you eject your
copies every day.  In addition, the backup software has no knowledge of
the copy process, so if it fails, you're on your own for monitoring it,
etc. (It's not that I don't recommend this approach, I just wanted to
say that it does have limitations, perhaps the chief of which is that
Symantec will disavow any support on any issues you have.  Yuck.)

---
W. Curtis Preston
Author of O'Reilly's Backup  Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Newbie to Netbackup using VTL

[Liddle, Stuart]

NODon't use Vault to duplicate from VTL to physical tape!!!

We tried this, and in NB 5.1 MP6, Vault is a HOG!!  We were not able to keep
the drives spinning fast enough using Vault.  The best speeds we saw going
to physical tape using vault was maybe 30MB/sec.  Usually we got around
10MB/sec or lesswhich is definitely not a good thing.

What we ended up doing was using the built-in feature of our NetApp VTL to
do the cloning of the virtual tape to physical tape.  Now we are getting
much better performance of around 50 - 60 MB/sec.

The problem is that Vault has way too much overhead in doing the copying of
the data.  It's kind of like this:

-- you have one firehose coming in (data from the VTL)
-- you have another firehose going out (data to the physical tape drive)
-- then you have to empty the incoming firehose into a bucket and look at it
and then pour that bucket into the other hose going out.

With the built in cloning function of the VTL, you just connect the two
firehoses together and the data gets written from virtual tape to physical
tape.

--stuart (backing up over 200TB per week to VTL) liddle

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Blaine
Robison
Sent: Friday, May 11, 2007 8:05 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Newbie to Netbackup using VTL

I understand that VTL able to create multiple tape libraries and tape
drives.

Yes this is correct. There is a limit depending on the manufacturer.

 If i'm cloning data that already backup in VTL to the actual tape library,
 what is the common practice? script? netbackup? 

Common practice is to use vault.
You can create a script using bpduplicate.

 Let's say if i have 100 clients and i do not use multiplexing and instead
 creating 100 virtual tape drives, does it mean that i need 100 LTO3 tape
when
 i do cloning? Will the activity monitor display backup failure from VTL to
 the normal tape library?

If you are limiting retentions to 1 retention per tape and you have 100
retention periods then yes.

If you have only 10 retention periods, you will utilize your tapes more
efficiently when you clone. 

Yes, It will look just like a tape library to tape Library duplicate
failure.

--- dy018 [EMAIL PROTECTED] wrote:

 
 Hi everyone,
 
 I'm new using VTL with netbackup.
 
 I was hoping anyone here already implemented such a setup in their current
 environment and hope share your general setup plan? I'm now planing for
such
 a setup and only have experience using normal tape libraries.
 
 I understand that VTL able to create multiple tape libraries and tape
drives.
 If i'm cloning data that already backup in VTL to the actual tape library,
 what is the common practice? script? netbackup? 
 
 Let's say if i have 100 clients and i do not use multiplexing and instead
 creating 100 virtual tape drives, does it mean that i need 100 LTO3 tape
when
 i do cloning? Will the activity monitor display backup failure from VTL to
 the normal tape library?
 
 Any help is much appreciated. Thank you in advance
 
 
 
 
 
 ___
 Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 


Blaine Robison
Solaris Ceritfied System Administrator 
Solaris Certified Network Administrator
Veritas Certified Professional
972-853-2459
214-578-5391


   

Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Taking the plunge to upgrade from 5.1 MP4 to 6.0 MP4

[Liddle, Stuart]

yeahwait for 6.5, that's what we are doing

 

--stuart

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Wigington
Sent: Thursday, May 10, 2007 10:55 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Taking the plunge to upgrade from 5.1 MP4 to 6.0 MP4

 

Can anyone give advise on upgrading from NBU5.1 MP 4 to NBU6.0 MP4? 

TIA,
Mike Wig

 

  _  

Ahhh...imagining that irresistible new car smell?
Check out new
http://us.rd.yahoo.com/evt=48245/*http:/autos.yahoo.com/new_cars.html;_ylc=
X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-  cars
at Yahoo! Autos. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Taking the plunge to upgrade from 5.1 MP4 to 6.0 MP4

[Liddle, Stuart]

We have an environment that is under strict change control and if we are
going to upgrade we are going to wait just a bit longer for the version that
has more features in it.  Why go for 6.0 now, when you might want to do the
upgrade to 6.5 in just a few months?

 

--stuart

 

  _  

From: Jeff Lightner [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 11:12 AM
To: Liddle, Stuart; Mike Wigington; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Taking the plunge to upgrade from 5.1 MP4 to 6.0
MP4

 

Why?   I was under the impression 6.0 MP4 was fairly stable.  

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Liddle,
Stuart
Sent: Thursday, May 10, 2007 2:00 PM
To: Mike Wigington; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Taking the plunge to upgrade from 5.1 MP4 to 6.0
MP4

 

yeahwait for 6.5, that's what we are doing

 

--stuart

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Wigington
Sent: Thursday, May 10, 2007 10:55 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Taking the plunge to upgrade from 5.1 MP4 to 6.0 MP4

 

Can anyone give advise on upgrading from NBU5.1 MP 4 to NBU6.0 MP4? 

TIA,
Mike Wig

 

  _  

Ahhh...imagining that irresistible new car smell?
Check out new
http://us.rd.yahoo.com/evt=48245/*http:/autos.yahoo.com/new_cars.html;_ylc=
X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-  cars
at Yahoo! Autos. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NBU Aptare - Real World Benefits

[Liddle, Stuart]

Greg,

I can tell you that we run the command:

bppllist -allpolicies -U

and put the resulting output into a file which we then put into a revision
control system (we use subversion).

Plus we have a Change Control system where our users request changes to the
backups like adding/removing systems, path changes, etc.  These work orders
are then referenced when we check in a change to the policy list.

--stuart

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hindle, Greg
Sent: Tuesday, March 20, 2007 11:28 AM
To: David Rock; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NBU  Aptare - Real World Benefits

 David,
How do you track policy changes?


Greg 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Rock
Sent: Tuesday, March 20, 2007 2:10 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NBU  Aptare - Real World Benefits

* Ed Wilts [EMAIL PROTECTED] [2007-03-19 22:23]:
 
 These are benefits from StorageConsole that we get all the time - some

 exclusively from StorageConsole and some in combination with our own 
 tools.  I'm pretty sure that there are features that we're not using 
 yet (some just because they're not as applicable to our environment as

 they could be to others and perhaps some just because I haven't 
 mastered it all (like automated reporting)).

I can mirror most of this, plus add a few more.  One of the more recent
additions is tracking of policy changes.  We are just starting to use
this as an audit control of what changes are made in a given policy.  It
makes for a good balance check against our change management process.

We have also saved many hours of our operations staff's time by giving
them a single screen to monitor off-hours rather than have seven
distinct NBU Activity Montiors running to track job status.  The
consolidated views simplify and help target what we react to.

My favorite report is probably the Backup Duration SLA report.  It gives
a simple view of what backups are taking a long time to complete,
allowing us to target those systems as potential items to optimize.

--
David Rock
[EMAIL PROTECTED]
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for
the addressee.  If you are not the intended recipient, do not use the
information in this e-mail in any way, delete this e-mail and notify the
sender. CEG-IP1

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Data de-duplication solutions

[Liddle, Stuart]

We are currently in the process of testing out Direct Tape Copy on the
NetApp NearStore VTL's.

The results we are seeing is that we are getting better than 50MB/sec with
LTO-3 drives writing to LTO-2 tapes.  We can attach up to 3 drives per 2GB
fiber-channel port.  We figure we can do about 4TB/day per drive or up to
12TB/day for one NearStore VTL.

Compare that to the very poor performance of the vault/duplication process
which we have found to be on the order of roughly 11MB/sec or about 1TB per
day per LTO-3 drive.

We are still testing and have not yet made the switch over to this, but
right now it looks very promising.  If we do make the switch we will not use
vault for anything except for maybe container management.

--stuart

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of T H
Sent: Wednesday, October 18, 2006 6:10 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Data de-duplication solutions

Hi everyone,

I have seen subjects on data de-duplication here. For those using such type
of solutions such as data domain, pure disk etc:

- What are your experiences? 
- Do you lose any throughtput while using such solutions and any worries
with data corruption? 
- The bulk of our backup data is Oracle so does the solution you have work
with Oracle? 
- Can one use the solution with existing NetBackup agents (no interest in
deploying new client SW for 1000's of servers)?
- Do you replicate the data offsite and how is that working for you?

Any feedback is highly appreciated.

Thanks,
Tambaa



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Data de-duplication solutions

[Liddle, Stuart]

Yeahthere's a way to scan the physical library and the VTL will create a
set of virtual tapes with the same barcodes as the physical
tapesNetBackup will basically not know the difference and will treat
them the same.

I believe that you can always get the data off of the physical tapes if the
Nearstore dies.  The problem would be if you had not gotten all of the data
transferred from the VTL to the physical tapes before the VTL gets hit with
some kind of failure.

The physical tapes would be used for off-siting.  There is a shadow copy
feature that will keep stuff on the VTL until the disk space is needed for
new backups.  So, if you have enough disk you can keep stuff online for
restores if needed.

If you are getting 30MB/sec to tape with vault/duplication, you're lucky.
I've found that it is highly dependent upon the image size and the makeup of
the image itself.  If you have a number of small images, you will lower the
throughput of vault.  Also, if you have a large image that is made up of a
number of small files, you will also impact the throughput.  The best case
is a large image made up of large files.

Think of it this wayit's like having a couple of fire-hoses for the data
flow.  One is coming into the media server from the VTL and the other is
out-bound to the physical tape drives.  Vault/duplication does not allow you
to simply connect the fire-hoses.  It has to empty the in-coming one and put
that data into buckets then empty those buckets into the out-going
fire-hose.  Ohand while it is filling the buckets, it's doing an audit
to ensure that you have the right number (counting the image fragments,
etc).  The nearstore VTL will actually connect the fire-hoses and you get
line-speeds because it's doing the copy at a block-level to the physical
tapes.

As for the performance into the VTL, we don't really care, because there's
no shoe-shining with virtual drives.   But we have seen very fast transfer
rates in and out depending upon the data source and the connection to the
media server.  Like 30MB/sec or faster for single streams.  And if you add
up the throughput of multiple streams for a given source, it's even faster
than that.

-stuart

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating
Sent: Thursday, October 19, 2006 10:09 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Data de-duplication solutions

So the Nearstore sees the physical tape library and directly copies fromthe
virtual tape cartridges, on a 1:1 basis to the physical carts?
How does the info get passed back to netbackup so Netbackup's catalogknows
what is on the physical tapes?
ie. if your Nearstore sc*ews the pooch, can you get your data off
thephysical tapes without importing them all?
Are your Nearstore vols replicated to a DR site? Or do you use
tapeexclusively for offsite DR?
For the record, I've been averaging well over 30MB/s tape to tape, usingLTO3
drives with LTO2 carts.
What kind of throughput are you getting into the nearstore during
yourbackups?
We're evaluating RFP responses for VTL at the moment...
Paul


-- 

 -Original Message- From:
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf  Of Liddle,
Stuart Sent: October 19, 2006 12:58 PM To: T H;
veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Data
de-duplication solutions   We are currently in the process of testing out
Direct Tape Copy on the NetApp NearStore VTL's.  The results we are
seeing is that we are getting better than  50MB/sec with LTO-3 drives
writing to LTO-2 tapes.  We can attach up to 3  drives per 2GB
fiber-channel port.  We figure we can do about 4TB/day per  drive or up to
12TB/day for one NearStore VTL.  Compare that to the very poor performance
of the  vault/duplication process which we have found to be on the order
of roughly 11MB/sec or  about 1TB per day per LTO-3 drive.  We are still
testing and have not yet made the switch over to  this, but right now it
looks very promising.  If we do make the switch  we will not use vault for
anything except for maybe container management. 
--stuart

La version française suit le texte anglais.


This email may contain privileged and/or confidential information, and the
Bank ofCanada does not waive any related rights. Any distribution, use, or
copying of thisemail or the information it contains by other than the
intended recipient isunauthorized. If you received this email in error
please delete it immediately fromyour system and notify the sender promptly
by email that you have done so. 


Le présent courriel peut contenir de l'information privilégiée ou
confidentielle.La Banque du Canada ne renonce pas aux droits qui s'y
rapportent. Toute

Re: [Veritas-bu] Viewing vault duplication performance.

[Liddle, Stuart]

I think the iostat command for linux is differentBUT...You can look at
the bptm log files on your media server and get information about the
duplication speeds.

look for successfully wrote and successfully read in the bptm logs to
get write and read speeds for the duplication process.

You can also get similar information on the master server with the bperror
command...but it might be easier to get it from the media server bptm logs.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darren
Dunham
Sent: Wednesday, October 11, 2006 1:01 PM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Viewing vault duplication performance.

 Is this linux specific?

In the sense that I can't use 'iostat' to check the speed, yes.  I think
windows would have the same issue as well.

In the sense that NetBackup isn't reporting on the speed, then I imagine
it's common to all platforms.

 I don't have a linux box handy to check, but I'd imagine iostat would do
 exactly that.
 
 On solaris, I use iostat with the -xnp args and follow it with the
 interval time and number of intervals.

Yes.  Solaris iostat shows tape devices.  Apparently Linux iostat does
not (at least I have not been able to make it do so).  

Now that my duplication is complete, I can hand-calculate the average
throughput for the entire operation.  But that's not available to me
during the process to see how it's going

-- 
Darren Dunham   [EMAIL PROTECTED]
Senior Technical Consultant TAOShttp://www.taos.com/
Got some Dr Pepper?   San Francisco, CA bay area
  This line left intentionally blank to confuse you. 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] bpclient

[Liddle, Stuart]

Tairone,



I think that you want to use the command bpplclients 



NOT bpclient.



The bpclient command is for something
entirely different.



--stuart











From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tairone N. Magalhaes
Sent: Wednesday, October 04, 2006
12:36 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] bpclient







Hi to all,











I'm newat the list andtoNetBackup also. I begun
working with it about two months ago.





My name is Tairone Nunes Magalhaes, and I live in Brazil. I'm
working at Telemar.











I cannot listall the clients that I can see with the administration
console GUI usingthe command 











 bpclient -All











Neither putting the master server name, as follows:











 bpclient -All -M masterbkp











Onliabout 1/6 of the clients are being listed. Can anyone tell me
why is it happening and what can I do for listing all the clients.





Thanks in advance,











Tairone








___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] How do we duplicate skipped images in vaulting

[Liddle, Stuart]

All that needs to be done here is to
ensure that your selection criteria for the vault profile is set to a time that
will go back far enough to include any missed images.



We have this situation occur from time to
time and because I have specified in the vault selection criteria to go back 14
days, the next time the vault profile is run, it picks up anything that might
have gotten missed from the previous session.



--stuart











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Veritas Netbackup
Sent: Tuesday, September 26, 2006
12:45 PM
To: Mansell, Richard
Cc:
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] How do
we duplicate skipped images in vaulting





Hey Richard,

One of the reports generated during the
eject phase also lists images that have not been duplicated.

Thats what I'm looking for, I can maybe atleast reduce the recovery point by
firing an off-schedule backup...!

Regards,
BIJU KRISHNAN



On 9/25/06, Mansell,
Richard [EMAIL PROTECTED]
wrote:



We run with the Vault permanentlyset
to level 5logging. Info for failed images is then captured in the
sessions directory in the log for that particular vault stream. You can tell
from the activity monitor which duplicating session failed as it will say something
like 10 of 12 images duplicated. You then look in that sessionlog for the
specific problem. e.g.



03:19:23 INF - Beginning duplicate on
server ccobkp01 of client ccovcs01.
03:19:25 INF - Beginning duplication on server ccobkp01 of client ccovcs01,
creating copy 2 on destination media id GC9012
03:38:14 INF - host ccobkp01 backupid ccovcs01_1157711364 write failed, media
write error (84).



or 



05:27:39 INF - Duplicating policy SQLLog
schedule SQLLog backup id ccobwpci01_1157990414 copy 1 created on 09/12/2006
04:00:14 on source path E:\
05:27:39 INF - Backupid ccobwpci01_1157990414 copy 2 already exists
05:27:39 INF - Duplicate of backup id ccobwpci01_1157990414 failed, the entity
already exists (226).



One of the reports generated during the
eject phase also lists images that have not been duplicated.



Regards



Richard









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Veritas Netbackup
Sent: Sunday, 24 September 2006
7:14 am
To: David Rock; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] How do
we duplicate skipped images in vaulting

Yes thats true,

The problem is that I have just enough VTL space to hold data for
3 days. We engage 8 Gen3 drives 3-3-2 for the vaults {3 at at time}. We are in
the process of changing the polcies to implement daily vaulting, but would take
some time. For now it happens that we are not able to overlap one of the vaults
in the 3 day period. Thus we end up loosing some images.

How can quickly get a list of skipped images during the vault.
There shd be some way to extract this list from the files in the
/usr/openv/netbackup/vault/sessions/ directory. I could then
probably manually duplicate them.

Any suggestions are welcome since I have run out of ideas.


Regards,
PP BIJU KRISHNAN

















**
This electronic email and any files transmitted with it are intended 
solely for the use of the individual or entity to whom they are addressed. 

The views expressed in this message are those of the individual 
sender and may not necessarily reflect the views of the Christchurch
City Council.

If you are not the correct recipient of this email please advise the
sender and delete.

Christchurch
City Council
http://www.ccc.govt.nz
**




___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu

http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu












___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] LTO3 throughput on Vault/Duplication jobs

[Liddle, Stuart]

Title: Message








I think we are licensed per TB on the VTL.not
per drive. 



Our rationale in doing the multiplexing to
the VTL was to increase throughput to the VTL for backups. We CAN
increase the number of virtual drives instead and then do single streams to the
VTL and avoid the de-multiplexing during the duplication step.



However, we are seeing lightning-fast read
speeds off of the VTL regardless of the fact that it is multiplexed (around
130MB/sec).



So, Im still concerned about the
speed with which we write out to the physical tapes..not sure where the
bottleneck isbut there definitely is a bottleneck.











From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating
Sent: Tuesday, September 19, 2006
8:49 AM
To:
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] LTO3
throughput on Vault/Duplication jobs







My thought's exactly JR.











I'm thinking folks either have VTLs
where they are licensing from the vendor on a per virtual drive
basis, OR, they are licensing Netbackup on a (old) per drive, rather than (new)
per TB of usable disk basis, so want to avoid the licensing cost of adding more
virtual drives..that was on of my primary criteria in selecting a VTLI
want to be able to create as many virtual drives as I want.











I currently have 20 physical drives, and
run various multiplex levels for different STUs, depending on the type of
backup, in order to maintain sufficient data flow to stream the drives, but
when the VTL comes into play, I want MPX=1, so I'll be configuring upwards of
20 virtual drives per media server.











Paul















-- 



-Original Message-
From: Dyck, Jonathan
[mailto:[EMAIL PROTECTED] 
Sent: September 19, 2006 10:09 AM
To: Paul Keating; Liddle, Stuart;
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] LTO3
throughput on Vault/Duplication jobs





Agreed. Coming from an environment
where we are afraid of multiplexing everything due to those image's
importability (or lack thereof), the fact that we cannot demux quick enough has
us handcuffed a little.











Just a question, what's the rationale on
mpx'ing to your VTL's?











Cheers,





Jon












___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] LTO3 throughput on Vault/Duplication jobs

[Liddle, Stuart]

Title: Message








OK.we have MPX=6 for the VTL, so it
looks like we would be getting about maybe 21MB/sec according to what you are
saying..right?











From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating
Sent: Tuesday, September 19, 2006
10:38 AM
To:
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] LTO3
throughput on Vault/Duplication jobs













Stuart, 











Yeah, you're right, you're reading off
of the VTL at 130MB/s, but if you're reading from a multiplexed (virtual)tape,
and your MPX=10, and you're DEmultiplexing during the dupe, then only 1/10th,
or 10% , or ~13MB/s of that data is relevant to the image you're writing to
tape, so your throughput to the tape would be ~ 13MB/s











Make sense?











In essense, if you have MPX=10 on your
VTL, you need to read the data from VTL 10 times faster than you're writing to
tape.











if you preserve multiplexing
or if you use MPX=1 (off), then your VTL read and tape write should be
symmetrical.











with VTL and virtual drives,
you can create 10 virtual drives and set MPX=1, or create 1 virtual drive with
MPX=10, and get the same overall performancewithout the duplication hassle.

















Paul



-- 



-Original Message-
From: Liddle, Stuart [mailto:[EMAIL PROTECTED]

Sent: September 19, 2006 12:27 PM
To: Paul Keating;
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] LTO3
throughput on Vault/Duplication jobs

I think we are licensed per TB on the
VTL.not per drive. 



Our rationale in doing the multiplexing to
the VTL was to increase throughput to the VTL for backups. We CAN
increase the number of virtual drives instead and then do single streams to the
VTL and avoid the de-multiplexing during the duplication step.



However, we are seeing lightning-fast read
speeds off of the VTL regardless of the fact that it is multiplexed (around
130MB/sec).



So, Im still concerned about the
speed with which we write out to the physical tapes..not sure where the
bottleneck isbut there definitely is a bottleneck.








___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] LTO3 minimums

[Liddle, Stuart]

True, but that only gives you the speed
that it is reading..how do you get the write speed? 



For us, we are reading from a VTL and
writing to LTO-3 drives in an ADIC i2000 tape library. I want to see what
my write speed is. 



Im getting excellent read
throughput from the VTL (averaging about 115MB/sec).but it looks like my
average throughput on the output side is maybe around 11MB/sec. When I
look at my gross throughput to physical tape, it looks like vault is only
pushing out about 1TB/day (roughly 11MB/sec)!



Any suggestions?















From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Shyam Hazari
Sent: Monday, September 18, 2006
10:51 AM
To: Andrew Sydelko
Cc: [EMAIL PROTECTED];
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] LTO3
minimums







Also you can use bperror to get duplicate throughput.











bperror -all|grep successfully read (duplicate) backup id

-Shyam











On 9/18/06, Andrew
Sydelko [EMAIL PROTECTED]
wrote: 

On Mon, 18 Sep 2006 11:58:38 -0500 (CDT)
Joe Royer [EMAIL PROTECTED]
 wrote:

 Forgive me if this has been asked before, I'm a bit behind on reading
 the list.

 How do you keep your LTO3 drives spinning fast enough?

 I have a meeting with an idiot manager who refuses to believe that we 
 can't stream fast enough to use LTO3 without damaging the tape and/or
 drive.I have limited DSSU space.I have been in
environments in the
 past where shoeshining was normal and so was the 20% failure rate and I 
 don't want to go back.It is my understanding that most people
aren't
 spinning LTO3 fast enough and are living with higher failure rates.

Keep in mind that LTO3 drives are able to stream at several different rates, so
even if you can't get the full bandwidth that the drive can write at, as long
as it's greater than 20MB/sec, you're not harming the drive. 

 The only thing I can think of is to send everything to DSSU first (TSM
 anyone?), but NBU sucks at telling you the throughput there so I'm not
 sure I trust that anyway.Any tricks for getting throughput numbers
out 
 of NetBackup (5.1) DSSU duplicates are very welcome.

If you look at the All Log Entries report, you should be able to
see the bandwidth of your duplicates. These entries come from
/usr/openv/netbackup/logs/bptm/log.date or /usr/openv/netbackup/db/error/daily_messages.log.


 My backup master with a 6-drive internal RAID-10 can barely hit 27MB/s
 reliably doing OS backups, but my DSSU is on SATA SAN drives and hard
 to measure.

We've been very happy with the 3-ware controllers and SATA disks. Getting more
than 80MB/sec out of them at times. 

--andy.

--
Andrew Sydelko
Engineering Computer Network
Purdue University
___
Veritas-bu maillist-
Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu










___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] LTO3 throughput on Vault/Duplication jobs

[Liddle, Stuart]

ALL,



we have an issue with LTO-3 drive
performance. 



Our environment is set up as
follows: 

q a single
master server running Solaris

q 4 Linux media
servers

q 4 Windows
media servers

q ADIC i-2000
tape library with 16 LTO-3 drives that are shared on a SAN to all of the media
servers with SSO

q five NetApp VTLs
that have multiple virtual libraries on each one. Each media server is
connected to two virtual libraries (also over the SAN)



We do all of our backups to the VTLs
and are using Vault to make duplicate copies to the physical tapes. We
are multiplexing to the VTLs and then de-multiplexing to the physical
tapes.



We are currently seeing only about
11MB/sec going out to the physical tapes. However, our read performance
on the dups is averaging about 80  100+ MB/sec from the VTLs.



Is anyone else doing something like this
and are you getting better throughput to your physical tapes using Vault?



Symantec told us today that doing a
single-stream to the physical LTO-3 drives was only going to do about 8 or
9MB/sec and we should Preserve Multiplexing for the output in
order to get better throughput to the physical tapes.



Does this sound right? Its
sounding kind of fishy to me. We have our buffers set as follows:



NUMBER_DATA_BUFFERS: 128



SIZE_DATA_BUFFERS: 262144







thanks



--stuart






___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Catalog Archiving

[Liddle, Stuart]

Title: Message



Patrick,

If your catalog image database is growing and you want to decrease 
the amount of space it is taking, then you CAN do the Catalog Archiving, but 
there are other steps that you might want to take first.

First off, if you have retentions that are really long (like over 
90 days), you might want to reduce them. 

Of course, this presumes that you can get buy-off from your client 
base as to how long they want to be able to go back for doing a restore. 


If you have data to support the fact that a high percentage of 
restores are only done within, say, 30 days of a backup and it drops off sharply 
after that, then you can build a case for shorter retentions. We used to 
have some DBA's that requested infinite retentions of backups.that's 
ridiculous.

If you absolutely need to have long retentions, then send a 
catalog backup offsite with the backup tapes, give them a 1 year retention and 
be done with it. If you need to restore from those tapes after 1 year, you 
will have the catalog tape to use OR you can import the tapes in 
question.

Now, if that still does not shrink your image database size down 
to a manageable level, you can use the Catalog Archiving method. I tested 
it, it's messy and I came up with a procedure to do it. The Veritas 
documentation is not very clear on how it is done. If you are interested I 
can send you a copy of the documentation that I put together for doing 
it.

--stuart


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, 
SimonSent: Thursday, August 31, 2006 4:38 AMTo: 'Whelan, 
Patrick'; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] 
Catalog Archiving

Can I see the documentation? I cannot recall what NBU 
you are on / platform


Regards
Simon Weaver3rd Line Technical SupportWindows 
Domain Administrator 
EADS Astrium 
Limited, B23AA IM (DCS)Anchorage Road, Portsmouth, PO3 
5PU
Email: 
[EMAIL PROTECTED]

  
  -Original Message-From: Whelan, Patrick 
  [mailto:[EMAIL PROTECTED] Sent: 31 August 2006 
  12:19To: veritas-bu@mailman.eng.auburn.eduSubject: 
  [Veritas-bu] Catalog Archiving
  All,
  Is anyone using Catalog 
  Archiving? If so how is it working for you? I have read the documentation, but 
  it is not clear what the process is if you need to do a restore of files that 
  have archived. Can you enlighten me?
  Regards,
  Patrick Whelan
  NetBackup 
  Specialist
  Architect  
  Engineering
  +44 20 7863 5243
  Of all the things I've lost, I 
  miss my mind the most! - Unknown
  There are only 10 kinds of people 
  on earth - those who understand binary
  and those who 
  don't.
  *The 
  message is intended for the named addressee only and may not be disclosed to 
  or used by anyone else, nor may it be copied in any way. The contents 
  of this message and its attachments are confidential and may also be subject 
  to legal privilege. If you are not the named addressee and/or have received 
  this message in error, please advise us by e-mailing [EMAIL PROTECTED] and 
  delete the message and any attachments without retaining any copies. 
  Internet communications are not secure and COLT does not accept 
  responsibility for this message, its contents nor responsibility for any 
  viruses. No contracts can be created or varied on behalf of COLT 
  Telecommunications, its subsidiaries or affiliates ("COLT") and any other 
  party by email Communications unless expressly agreed in writing with such 
  other party. Please note that incoming emails will be automatically 
  scanned to eliminate potential viruses and unsolicited promotional emails. For 
  more information refer to www.colt.net or contact us on +44(0)20 7390 
3900.

  
  
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 Astrium Limited.Nothing in this email shall bind Astrium 
  Limited in any contract or obligation.Astrium Limited, Registered 
  in England and Wales No. 2449259Registered 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

Re: [Veritas-bu] VTL images to tape

[Liddle, Stuart]

Title: Message



Actually, the story I heard from Symantec/Veritas about the VTL 
support under 6.x is that it will allow for automatic expiration of the VTL 
images once they have been successfully duplicated to physical tape. 
That's similar to the currentoption in vault for images coming from a 
DSSU. 

We are currently using a script to expire our VTL images once we 
have them dup'd.

--stuart


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Paul 
KeatingSent: Tuesday, August 22, 2006 10:03 AMTo: 
veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] VTL images 
to tape

Well 
that's unfortunate.

I 
guess there's something key, missing in tape emulation 
department.

Paul

-- 

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Hindle, 
  GregSent: August 22, 2006 12:55 PMTo: Paul Keating; 
  veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] VTL 
  images to tape
  
  Yes using as tape. All that works fine. But getting the 
  images from the VTL to tape is more challenging. I think netbackup 6.5 has 
  full support for VTL's and then I assume that the vaulting option will fully 
  support VTL to tape copying then. I was told that 6.5 is due out by the end of 
  this year.
  
  Greg 
  
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] How do we expire media with duped images??

[Liddle, Stuart]

OKtry this:
A useful tip for expiring images is to 
look at the output from
 bpimagelist 
-l

If you look at: http://support.veritas.com/docs/193085
It will give a full description 
of the rather messy outpuf from this 
command.
Anyway, I put together an 
awk snippet to get just the 
information 
out that I needed:
($1 == "IMAGE"){print $6, "Primary: 
"$28, "Copies: "$21,"Frags: "$22, "KB: "$19, $7, $11, $14}

use it 
as follows:
bpimagelist -l -hoursago 999 | awk '($1 == "IMAGE"){print $6, "Primary: "$28, "Copies: "$21,"Frags: "$22, 
"KB: "$19, $7, $11, $14}'
direct 
this to a file and then examine the output.
Now you can use this output 
to look for whatever you want based upon the following:
Primary: 1 Copies: 1 -- an image that 
has not yet been dup'd
Primary: 1 Copies: 2 -- an image that 
has been dup'd, but the primary image is still copy 1
Primary: 2 Copies: 2 -- an image that 
has been dup'd with the primary image as copy 2
Primary: 2 Copies: 1 -- an image that 
has been dup'd, primary image is copy 2,  copy 1 has been expired there are 
other variations on this, but you get the idea

I look for something like "Primary: 2 
Copies: 2" and then use the backupid (first field of my awk output) to expire 
copy 1 like this:
bpexpdate -backupid backupid -d 
0 -copy 1 -force
The "-copy 1" part is importantif 
you leave this out it will expire all of the imagesprobably not a good 
idea.
The last column in the awk output is 
the timestamp which may be useful if you decide that you want to leave the copy 
1 image around for a set amount of time.
(Remember this can be converted 
tohuman-readable format by using the command:
bpdbm -ctime 
timestamp).

When you expire all of the images on a 
tape (virtual or otherwise)
you have to follow it up with this 
command:

bpexpdate -deassignempty

This will then set the status of the 
tape(s) to Available.


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Veritas 
NetbackupSent: Saturday, August 05, 2006 4:36 AMTo: 
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] How do we 
expire media with duped images??
Hi All,We use a VTL for backups and vault the data onto 
tapes. We have 4 vault policies.We would like a set of comands or 
scripts which can help us 1. get a list of images which have been duped, 
and expire them.2. find media ids on VTL corresponding to the 
duped images. Sort and extract uniq ids.3. Check each media as to 
whether they are unocupied and free them for further use.Is there a 
better way to do this..? Any help is appreciated.This is required since 
our growth has exeeded our infra, and hence we need to immediately release media 
after the images get vaulted.Regards,PP BIJU 
KRISHNAN
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Command for Catalog Backup Size

[Liddle, Stuart]

Another method is to use the bpsyncinfo commad which will give you
information about the paths being backed up by your catalog backup.  You can
then use that to do du -sk on those paths
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of smpt
Sent: Thursday, August 03, 2006 11:20 PM
To: praveen sundriyal; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Command for Catalog Backup Size

The easiest way is to find the size of /usr/openv/netbackup/db. This dir is
the 99.5% of the catalog size


  ---Original Message---
  From: praveen sundriyal [EMAIL PROTECTED]
  Subject: [Veritas-bu] Command for Catalog Backup Size
  Sent: 04 Aug '06 05:59
  
  Hi ,
  
  I am using veritas netbackup 4.5 on unix . we have 2 master servers   
 around 25 media servers.I want to calculate my current catalog size is  
 there any command or script which tell me the exact catalog size per 
 media  server.
  
  Any suggestions would be greatly helpful.
  
  thanks,
  
  (*praveen*).
  
  ___
  Veritas-bu maillist  -  [LINK:
  [EMAIL PROTECTED]
  Veritas-bu@mailman.eng.auburn.edu
  [LINK: http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu]
  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Anyone using VTL

[Liddle, Stuart]

Yes, we are.  We currently have about 133TB of space using the NetApp
VTL600's. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Juan Pablo
Almeida
Sent: Tuesday, August 01, 2006 9:13 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Anyone using VTL

Hi,

What do you think about VTL?
Are you using VTL? what model?

EMC DL710 or NetApp VTL600?
What about Storagetek?

Thanks in advance.

Juan

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Anyone using VTL

[Liddle, Stuart]

Juan,

It's Stuart (Liddle is my last name)

Yes, we are satisfied with the equipment

Nonot using compression (tape optimization) on the VTL, because we are
doing compression when we go to physical tape.  

I have not run any numbers on the performance, but overall just by looking
at the job throughput, it looks good.

We backup anywhere from 3 - 4 TB per day on a weekday right now and up to
16TB on Saturday or Sunday.

We will be growing this substantially as we are migrating all of our current
legacy environments to our new centralized system over the next several
months.  Total of about 70 - 80 TB per week.

We chose NetApp because the design team that was responsible for our new
environment decided that it was a good product AND because we have a lot of
NetApp equipment already.



-Original Message-
From: Juan Pablo Almeida [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 01, 2006 9:47 AM
To: Liddle, Stuart
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Anyone using VTL

Hi Liddle,

Are you satisfied with this equipment?
Are you using compression enabled? What performance are you
obtaining? 
How many TB are you writing daily?
Why do you choose Netapp?

We are looking for a VTL solution, but in Brazil is very difficul to
find who are using this kind of product to know the feedback.

Thanks,

Juan


 Yes, we are.  We currently have about 133TB of space using the NetApp 
 VTL600's.
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Juan 
 Pablo Almeida
 Sent: Tuesday, August 01, 2006 9:13 AM
 To: veritas-bu@mailman.eng.auburn.edu
 Subject: [Veritas-bu] Anyone using VTL
 
 Hi,
 
   What do you think about VTL?
   Are you using VTL? what model?
 
   EMC DL710 or NetApp VTL600?
   What about Storagetek?
 
 Thanks in advance.
 
 Juan
 
 ___
 Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 
 E-mail classificado pelo Identificador de Spam Inteligente Terra.
 Para alterar a categoria classificada, visite
 http://mail.terra.com.br/protected_email/imail/imail.cgi?+_u=juan.alme
 ida_l=1,1154449650.943126.18040.curepipe.hst.terra.com.br,2167,Des15,
 Des15
 
 Esta mensagem foi verificada pelo E-mail Protegido Terra.
 Scan engine: McAfee VirusScan / Atualizado em 01/08/2006 / Versão: 
 4.4.00/4819 Proteja o seu e-mail Terra: http://mail.terra.com.br/

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Multiplexing

[Liddle, Stuart]

 Simon,

I won't argue that what you are seeing works for you.  It will work, it's
just not optimal.  

When you optimize your backup performance through the heavy use of
multiplexing, you will sacrifice performance on restores.  If you can live
with that, then finego ahead and do it.

However, you can get better performance on restores by restoring from a tape
that has not been multiplexed.  Try it sometime.  This part of the equation,
by the way,  has absolutely nothing to do with the speed of your backbone.

--stuart

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 31, 2006 12:26 AM
To: 'Liddle, Stuart'; 'Mansell, Richard'; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Multiplexing


Stuart
I will believe what I have seen, and the restores for the 2 SAN Media
Servers are absolutely well within limits of restoring data. We run an
extremely fast backbone, so I have no problems with the configuration in
place.


Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]



-Original Message-
From: Liddle, Stuart [mailto:[EMAIL PROTECTED]
Sent: 31 July 2006 07:59
To: WEAVER, Simon; 'Mansell, Richard'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Multiplexing


Simon,

Finebelieve what you wantbut the numbers don't lie.  

If you ever try any testing of this you will see that  restores are
significantly faster when you do them from non-multiplexed tapes.

--stuart

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 30, 2006 10:45 PM
To: 'Liddle, Stuart'; 'Mansell, Richard'; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Multiplexing


Stuart
Completely disagree - we get the best of both worlds and restores have never
been any real issue for us, even large amounts of data across multiple
tapes.

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]



-Original Message-
From: Liddle, Stuart [mailto:[EMAIL PROTECTED]
Sent: 28 July 2006 19:37
To: WEAVER, Simon; 'Mansell, Richard'; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Multiplexing


That's good for backup speeds, but it sucks for restores.  Unless all of
your clients have really slow network connections, having a high
multiplexing value is not really a good idea.

You might want to consider dropping the multiplexing down to something like
6.  

Our configuration uses VTL's to our first backup copy and then I use vault
to put it to physical tape.  I multiplex to the VTL and single-stream to the
physical tapes.  Once it is on the physical tape, we have a script that will
bpexpdate the copy 1 image on the VTL (this is not an automatic option in
NetBackup until version 6.x).

When you do a restore from a physical tape, you have a single-stream copy
and not one that is multiplexedthis makes for a faster restore.

--stuart 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER,
Simon
Sent: Thursday, July 27, 2006 11:22 PM
To: 'Mansell, Richard'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Multiplexing


Richard
Yes I use multiplexing a lot

NBU 5.1 Master MP2 + 2 SAN Media Servers

4 drives in a robot - using SSO

1 Storage Unit set to multiplex 25 jobs per drive (Master)
2 SAN Storage Units set to use 2 drives, multiplex 8 per drive

Seems to work - get a lot of jobs done - around 300 per night if that helps.

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]



-Original Message-
From: Mansell, Richard [mailto:[EMAIL PROTECTED]
Sent: 27 July 2006 22:31
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Multiplexing



We are struggling to get all of the backups run during the backup window and
one of the obvious solutions is to start using multiplexing as the tape
drives are not being driven at any where near their maximum throughput.
There has been a rather nasty multiplexing problem fixed in 6.0 MP3 but I
would be interested to do a straw poll of how many people are using
multiplexing and if possible any issues encountered.

I would appreciate it if you would respond (off list) as to whether you use
multiplexing or not (any version of NetBackup). I will summarise the results
and post back to the list.

Regards

Richard


**
This electronic email and any files transmitted with it are intended 
solely for the use of the individual or entity to whom they are addressed. 

The views expressed in this message are those of the individual 
sender and may not necessarily reflect

[Veritas-bu] Expiring copy 1 images

[Liddle, Stuart]

 When you expire all of the images on a tape (virtual or otherwise) you have
to follow it up with this command:

bpexpdate -deassignempty

This will then set the status of the tape(s) to Available.

A useful tip for expiring images is to look at the output from  bpimagelist
-l

If you look at:  http://support.veritas.com/docs/193085

It will give a full description of the rather messy outpuf from this
command.  Anyway, I put together an awk snippet to get just the information
out that I needed:

bpimagelist -l -hoursago 999 | awk '($1  == IMAGE){print $6, Primary:
$28, Copies: $21,Frags: $22, KB: $19, $7, $11, $14}'

Now you can use this output to look for whatever you want based upon the
following 

Primary: 1 Copies: 1 -- an image that has not yet been dup'd
Primary: 1 Copies: 2 -- an image that has been dup'd, but the
primary image is still copy 1
Primary: 2 Copies: 2 -- an image that has been dup'd with the
primary image as copy 2
Primary: 2 Copies: 1 -- an image that has been dup'd, primary image
is copy 2,  copy 1 has been expired 
there are other variations on this, but you get the idea

I look for something like Primary: 2 Copies: 2 and then use the backupid
(first field of my awk output) to expire copy 1 like this:

bpexpdate -backupid backupid -d 0 -copy 1 -force

The -copy 1 part is importantif you leave this out it will expire all
of the imagesprobably not a good idea.

The last column in the awk output is the timestamp which may be useful if
you decide that you want to leave the copy 1 image around for a set amount
of time.  (Remember this can be converted to human-readable format by using
the command:  bpdbm -ctime timestamp   ).


--stuart

_ 
Stuart W. Liddle 
Amgen Corp. 
[EMAIL PROTECTED] 






-Original Message-
From: smpt [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 29, 2006 1:04 AM
To: Liddle, Stuart; WEAVER, Simon; 'Mansell, Richard';
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Multiplexing

Can you share your script?

I'm using the same technique but there is a problem with tape expiration.
When you expire all images of one tape the tape doesn't expire. 
You have to search for assigned tapes that they don't have media and then
you have to use the bpexpdate - jusmedia command to expire the tape.

smpt


  ---Original Message---
  From: Liddle, Stuart [EMAIL PROTECTED]
  Subject: Re: [Veritas-bu] Multiplexing
  Sent: 28 Jul '06 20:36
  
  That's good for backup speeds, but it sucks for restores.  Unless all 
 of  your clients have really slow network connections, having a high  
 multiplexing value is not really a good idea.
  
  You might want to consider dropping the multiplexing down to 
 something like  6.
  
  Our configuration uses VTL's to our first backup copy and then I use 
 vault  to put it to physical tape.  I multiplex to the VTL and 
 single-stream to the  physical tapes.  Once it is on the physical 
 tape, we have a script that will  bpexpdate the copy 1 image on the 
 VTL (this is not an automatic option in  NetBackup until version 6.x).
  
  When you do a restore from a physical tape, you have a single-stream 
 copy  and not one that is multiplexedthis makes for a faster restore.
  
  --stuart
  
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
 WEAVER,  Simon
  Sent: Thursday, July 27, 2006 11:22 PM
  To: 'Mansell, Richard'; veritas-bu@mailman.eng.auburn.edu
  Subject: Re: [Veritas-bu] Multiplexing
  
  
  Richard
  Yes I use multiplexing a lot
  
  NBU 5.1 Master MP2 + 2 SAN Media Servers
  
  4 drives in a robot - using SSO
  
  1 Storage Unit set to multiplex 25 jobs per drive (Master)
  2 SAN Storage Units set to use 2 drives, multiplex 8 per drive
  
  Seems to work - get a lot of jobs done - around 300 per night if that
helps.
  
  Regards
  
  Simon Weaver
  3rd Line Technical Support
  Windows Domain Administrator
  
  EADS Astrium Limited, B23AA IM (DCS)
  Anchorage Road, Portsmouth, PO3 5PU
  
  Email: [EMAIL PROTECTED]
  
  
  
  -Original Message-
  From: Mansell, Richard [mailto:[EMAIL PROTECTED]
  Sent: 27 July 2006 22:31
  To: veritas-bu@mailman.eng.auburn.edu
  Subject: [Veritas-bu] Multiplexing
  
  
  
  We are struggling to get all of the backups run during the backup 
 window and  one of the obvious solutions is to start using 
 multiplexing as the tape  drives are not being driven at any where near
their maximum throughput.
  There has been a rather nasty multiplexing problem fixed in 6.0 MP3 
 but I  would be interested to do a straw poll of how many people are 
 using  multiplexing and if possible any issues encountered.
  
  I would appreciate it if you would respond (off list) as to whether 
 you use  multiplexing or not (any version of NetBackup). I will 
 summarise the results  and post back to the list.
  
  Regards
  
  Richard

Re: [Veritas-bu] VSP question

[Liddle, Stuart]

Title: Message



Just turn off VSP.it's a big pain and causes more problems 
than it solves.


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, 
SimonSent: Tuesday, July 18, 2006 11:08 PMTo: 'Hindle, 
Greg'; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] VSP 
question

Greg
If VSP is turned off and you start getting files NOT backed up, 
then it means its an open file, and NetBackup was unable to perform a backup of 
that file or files.

If VSP is turned on, and it comes across the SAME files it could 
not backup, but this time it DOES back them up, then it means VSP is 
working.

NetBackup does a good job of most file types, whether they are in 
use or not. VSP / VSS (Win2k3 only) has the ability to allow open files to be 
backed up.

Of course, this is not the case if you have SQL / Oracle / 
Exchange as you will require an agent for 
this.

Does this help?


Regards
Simon Weaver3rd Line Technical SupportWindows 
Domain Administrator 
EADS Astrium 
Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 
5PU
Email: 
[EMAIL PROTECTED]

  
  -Original Message-From: Hindle, Greg 
  [mailto:[EMAIL PROTECTED] Sent: 18 July 2006 
  18:32To: veritas-bu@mailman.eng.auburn.eduSubject: 
  [Veritas-bu] VSP question
  Nb 5.0 mp6 Solaris 9 
  If VSP is turned off / disabled for a 
  client, will netbackup still back up open files and open registry keys? A co 
  worker is telling me that with VSP off open files will still be backed up. And 
  the way to tell is to run a backup with VSP turned off and see if the backups 
  completes with a 0. If it does then the files are getting backed up (meaning 
  nothing is getting skipped). I am thinking no here. That open files and 
  registry keys will be skipped if VSP is turned off for a 
client.
  Greg  This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for the
addressee.  If you are not the intended recipient, do not use the information
in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2


  
  
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. 2449259Registered 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

Re: [Veritas-bu] Vault Catalog?

[Liddle, Stuart]

yes.and it works quite well.


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Barber, 
Layne (Contractor)Sent: Thursday, July 13, 2006 11:00 
AMTo: veritas-bu@mailman.eng.auburn.eduSubject: 
[Veritas-bu] Vault Catalog?

Is it possible to 
setup a vault to only do a catalog backup and eject it w/o it doing anything 
else? (vaulting other backups etc.)

Thank You,

Layne Barber
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Emc VTL and netbackup question

[Liddle, Stuart]

Title: Message



I would add that, yes, it would be a good idea to keep images on 
the VTL for possible restores. However, if you need the space, then you 
should remove those images from the VTL as soon as they have been successfully 
duped. Our practice is to make two physical tape copies, one for on-site 
and the other for off-site for DR purposes. That way we have a physical 
tape on-site with the backup image for quick restore so that we don't have to do 
any recalls from offsite.


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Paul 
KeatingSent: Monday, July 10, 2006 1:14 PMTo: 
veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Emc VTL 
and netbackup question

I 
would change the retention in your netbackup policies to be inline with how long 
you want the data kept on the VTL.
When 
you duplicate/vault you can specify how long you want the data kept on the 
"tape" copy, independantly..then the VTL copy will expire itself after the 
amount of time you've specified in the original policy.

you 
don't really want to expire the VTL copy as soon as it's duplicated to 
tape.in theory, the best practice would be to dupe it to tape as soon as 
possible, but keep it on the disk/VTL as long as you can (as long as you have 
sufficient space to do "tonight's" backup) that way your restores come from disk 
as much as posisble.

Paul


-- 

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Hindle, 
  GregSent: July 10, 2006 3:54 PMTo: 
  veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Emc VTL and 
  netbackup question
  Nb 5.0 mp6 Solaris 9 EMC CDL VTL 
  Ok here is the situation. We are testing this Emc 
  CDL VTL. We backup data to the VTL and now need to get the data on the VTL 
  copied to physical tape and then expire the image on the VTL. We were trying 
  to use vault to perform the copy but unfortunately it will not expire the 
  images on the VTL because it thinks the VTL are tapes. I understand that it 
  will work if it was a DSU and we were copying the data to tape but since in 
  the eyes of netbackup this is a tape to tape copy it is not designed to expire 
  tape copies. This I just confirmed with Symantec. SO I think I need a script 
  that will run copy and expire commands. Is anyone else using the EMC CDL VTL 
  and has run into this same problem? Does any have a script that will perform 
  this function?
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] CLI or GUI

[Liddle, Stuart]

I don't really agree about the bit about building new policies.

I can use:

bppolicynew policyname -sameas existingpolicy 

Much quicker than the GUI, thank you.

As for building policies from scratch, we have a script for doing that and,
again, much quicker than the GUI.

I will agree about getting backup speeds from the GUIthat's one of the
best views.

--stuart

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, June 30, 2006 10:31 AM
To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] CLI or GUI

I make all sorts of jokes about the evils of the GUI but I do use it for two
things consistently.

1. Building new policies - it's just so much easier than the cmd line.
2. The activity monitor - the cmd-line version is static views only.

After that, I find the command-line to be much more precise.  Restores
aren't this click-wait-click-wait stuff, it's just a one-liner  off it
goes.  Device monitoring is clunky (at least in 5.x  down - I haven't
installed 6.0 yet). 

Yup - love that command line.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Keith W
Sent: Friday, June 30, 2006 10:20 AM
To: Veritas List
Subject: [Veritas-bu] CLI or GUI

Reading the mails coming through this thread, I get the impression that most
folks use the CLI more than the java gui, is this true and why? Just a
curious semi-newbie question.

+---+
+   Keith   +
+---+

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] removing old vault sessions

[Liddle, Stuart]

I have set up vault to run 
several times per week. Some of the vault runs do not produce any results 
(that is, there are no images to vault). However, it will still create a 
vault session in the 
/usr/openv/netbackup/vault/vaultname 
directory

This leaves several 
sidnumber directories, only some of which will have useful data in 
them.

Is there a problem with 
deleting the unused session directories? Is there any way through 
NetBackup to have these removed automatically?

--stuart

_ Stuart W. Liddle Amgen Corp. [EMAIL PROTECTED] 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu