[Veritas-bu] Facing Problem with flood of alerts EC-196 netbackup6.5

2010-08-04 Thread shekhar deshingkar 
Hello,

We have setup of one master server so many media server and client list but
backup jobs are failed with EC-196 with flood of alerts could you explain
any tunning procedure to follow the proper backup scheduled and compltion
within specifice window.
If you have any info on same please pass.

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

Re: [Veritas-bu] Facing Problem with flood of alerts EC-196 netbackup6.5

2010-08-04 Thread Mark Glazerman 
Some reasons why we have suddenly seen high numbers of 196 errors
include...

 

1)  No exclude list on a new client meant that other clients were
sat waiting for access to our disk storage units (limited number of
concurrent jobs to the same storage unit) while this new client sent
huge amounts of useless data to our data domains.  All the jobs queued
will fail when their backup window closes.

2)  Network issues slowed the throughput of our backups to where
clients were still waiting to start when their backup window closed.

3)  If your storage units / devices were unavailable you'd be
getting a different error code although when we were still backing up to
tape we'd get 196's if we ran out of scratch tapes and the jobs were sat
queued waiting for available media to be loaded into the drives.

 

There could be multiple reasons why you're getting this error.  Do you
have your jobs on a time or date schedule ?  Has there been some
schedule creep on other backups which is eating into the window for the
clients now failing with 196's ?

 

Mark Glazerman

Desk: 314-889-8282

Cell: 618-520-3401

P please don't print this e-mail unless you really need to

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of shekhar
deshingkar
Sent: Wednesday, August 04, 2010 10:36 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Facing Problem with flood of alerts EC-196
netbackup6.5

 

Hello,

 

We have setup of one master server so many media server and client list
but backup jobs are failed with EC-196 with flood of alerts could you
explain any tunning procedure to follow the proper backup scheduled and
compltion within specifice window.

If you have any info on same please pass.

 

Thanks,

Shekhar Dehingkar.

 

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

Re: [Veritas-bu] Facing Problem with flood of alerts EC-196 netbackup6.5

2010-08-04 Thread Wayne T Smith 
As you know, the 196 status code means your backup job could not be started
within its backup start window.  It didn't start because it required a
resource that wasn't available (to it) during the start window ... probably
a place to put the backups or limits on number of backup streams/jobs for
the client/policy/storage unit.  So the question becomes ... Why wasn't the
backup storage available? and What can I do about it?

Assuming you have a place to put backups, the task is to determine how to
get as much data as possible there.

There are lots of techniques...

   - Split a machine backup using multiple policies or multi-streaming so
   more than one data streams (jobs) can run at a time.
   - If using tape, use multiplexing to send more than one stream to the
   tape at a time.  This can actually make a tape drive work faster, but does
   use additional cpu and memory resources in your media server.  Also, it can
   slow restores, since when reading the tape for a restore, the data from
   several backup streams must be read in order to process the stream of
   interest.  In my practice, I find the restore problem to be of little
   interest, unless I have a very fast communication path to the client machine
   ... and if so, why did I multiplex?
   - Lengthen the backup window.
   - Spread full backups over time, not just Friday night (or any one or two
   particular times).
   - Spread the start of jobs to minimize overhead and make each job
   duration smaller.
   - Backup less; do you really need everything that is now backed up?
   - Enhance your backup processing (communications and media server
   capability) and storage resources.  Before buying more tape drives,
   determine that current ones are being driven at or near their rated speed,
   and consider backup to disk, probably with a deduplication function in
   NetBackup or the disk storage.


Thinking back over the past decade, when I've seen 196s in a running backup
system, the problem was

   - one or more tape drives offline.
   - one or more backup jobs hung.
   - one or more backup jobs endlessly writing data to the backup system.
   - multiplexing changed to too high
   - multiplexing changed to too low
   - a tape drive stuck at a slow speed
   - one or more clients with badly configured communication ports causing
   very slow backups, stealing time from other backups.
   - a disk storage unit going offline for at least part of a backup window
   - one or more tape drives failing enough to cause enough backup (long
   duration job) restarts to overflow the backup window for some some jobs.
   - changes to clients (more data) or policies (added Follow NFS) or new
   clients with the exclude list not configured.
   - added client compression to various clients, greatly extending the
   duration of backups.

I'm sure there are other scenarios!   Hope this helps.   Cheers, Wayne

On Wed, Aug 4, 2010 at 11:35 AM, shekhar deshingkar
sdeshing...@gmail.comwrote, in part:

 We have setup of one master server so many media server and client list but
 backup jobs are failed with EC-196 with flood of alerts could you explain
 any tunning procedure to follow the proper backup scheduled and compltion
 within specifice window.

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