Carl McNamee <[log in to unmask]> ponders thusly:

> I've been wondering to myself lately "What are the consequences of not
> taking down the network during our full backup?"  Having the network up
> would be a big help with some of the automation I'm doing.
>
> Thought?  Comments?  Criticism?

We run a completely unattended operations during the off-shift hours
(basically 5 PM to 8 AM the next morning).  We have an ODBC application that
runs 24 x 7.  Never having been able to get any zero-down-time backup to
work, we finally decided to stop the ODBC listener, copy the pertinent data
bases to a backup group, restart the listener, and then proceed with the
backup.  This gives us a clean point from which to recover, if (when) we
need to.  Of course, prior to this we logoff all sessions and stop all jobs,
and set the limits down so that no more can be started until the backup is
finished; however, the "network" is up insofar as the ODBC still works.  We
do have Telnet devices connecting using JINETD, but that job is stopped
while the backup runs (because the Telnet devices log on to the system); but
we probably could leave it up (if we needed to, say for Samba processes)
because the limit will stop HELLO's from working.

Jim Phillips                           Information Systems Manager
Email: [log in to unmask]     Therm-O-Link, Inc.
Phone: 330-527-2124                         P. O. Box 285
Fax:   330-527-2123                           10513 Freedom Street
Web:   http://www.tolwire.com          Garrettsville, OH  44231

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *