RE: Data protector backup / control issue --> RE: [IUG] Legato backup /control issues

["Lynch, Michael" <lynch at middlebury dot edu>]

We have had the same problem of control not restarting after the backup api command.  It has also happened to us on only two occasions.  Similar to your process, we issue the api command to stop control, then tar all the Innovative directories and files to disk, then issue the api command to restart control.

Later, Backup Exec runs to copy those tar'ed files to tape, ignoring the live Innovative files.

Mike Lynch
Systems Librarian
Middlebury College
Middlebury, VT

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org]On Behalf Of Krueger, Cynthia M
Sent: Thu, October 26, 2006 6:07 PM
To: IUG INNOPAC List
Subject: Data protector backup / control issue --> RE: [IUG] Legato
backup /control issues


Interesting, we are having a similar problem but with Data Protector,
not Legato.

We use the III backup api commands to stop the control program just
prior to the procedure which runs Data Protector.  Then we use the III
backup api commands to restart the control program after the Data
Protector procedure has finished.

Twice now since we have been live, we discover that the Control Program
is in a "defunct" state and must be re-started.  Attempts to do so using
the iii backup api commands fail.  A call to Help Desk results in their
not being able to restart the program.  The first time this happened,
Help Desk instructed us to shutdown Millennium and reboot the system.
Of course, this did get everything running again.
This last time the situation occurred, just this Tuesday morning, Help
Desk was able to get the Control Program to re-start after killing the
Parent process and restarting that process first.  We didn't have to
reboot the system.

We have this same setup on our test server and have yet to experience
any problems with the control program on the test server.

Still III and our own staff have no reason why the Control program
should go into a "defunct" state or when it went into this state.  We
are suspecting backup process since it's the only process during the
night that stops the control program and restarts it.  We are putting in
measures to show system status periodically so we can determine that the
situation starts during the backup process.

Is anyone using Data Protector (HPs) and having a problem like this?

The backup api commands are very straightforward.
We can pull the data protector portion out and just run the backup api
portion.
Looks like they are independent of each other.
We could run the backup api commands by themselves and not run the data
protector process and Millennium would think we had a good backup as far
as I can see.  Unless I'm missing something.  ;-)
 
Cynthia Krueger
Technology Resources - TXState at San Marcos
Alkek Library
ck01 at txstate dot edu  
512.245.2271  
512.245.1316 (fax)

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Lisa de Carbonel
Sent: Tuesday, Octomits."ber 17, 2006 1:01 PM
To: innopac at innopacusers dot org
Subject: [IUG] Legato backup / control issues

We have had a recurring issue with Legato backup and are wondering if
anyone else has had a similar experience, hopefully with a satisfactory
resolution.  Our server is in a central campus center and the staff
there run the Legato backup.  As our backup is scheduled to run
overnight it is part of my daily routine to check on it first thing in 
the morning,  7 days a week.   We can go months with no problems but 
when the backup fails (as it has 4 times in the past 2 weeks), it leaves
us with control locked which necessitates a call to the Help Desk.  The
problem is further exacerbated when there are reattempts made to run
Legato -- usually once staff are already at work -- leaving us in limbo
wondering when control will stop again, and if it will come back up
again without another call to the Help Desk. 

Thus far Innovative has identified an issue with the Legato software,
but the campus staff running the backups hasn't demonstrated much
concern about correcting the problem, or an awareness of how disruptive 
it is to run the backup once people are at work.   The most forthcoming 
they've been is to say that 'they had a problem with the server, but 
it's fixed now.'    We're pretty much stuck in the middle, wondering if 
there's anything we can do...  is there?

Thanks in advance,

Lisa de Carbonel

-- 

Lisa de Carbonel
Systems Editor
School of Law, Library
UC Berkeley


--
This message was distributed through the Innovative Users Group INNOPAC
list Public replies:  INNOPAC at innopacusers dot org Update your subscription
options: http://innopacusers.org/mailman/listinfo/innopac

--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC at innopacusers dot org
Update your subscription options: http://innopacusers.org/mailman/listinfo/innopac