Simonsen, Larry <[log in to unmask]> wrote:

>since we have no modems on our hp 3000 and all users other than the
>console logon through the network if we take the network down for backup
>we must have an operator on site to do the reply and restore the system.
>if we are going to leave the network running during backup what files
>other than @.net.sys do I need to store for a special recovery backup of
>the networking configuration?  what do others do?

The only files skipped by STORE are files that are in use for writing, not
files that are open. If you look at your list of files you will find that
leaving the network up does not cause a problem with files not storing.
(IIRC, this was a problem under MPE/V where NSCONF.NET would not get
stored if the network was still active, but that is not an issue on
MPE/iX.)

Even so, I would still shut the network down prior to a backup since
nobody is logged on anyway just to refresh all of the internal network
structures, mapping tables, etc. By enabling autoreply on your tape drive
you should be able to automate the entire process, provided your backup
will all fit on one tape. Here is a sample (untested) job that does it.

!job fullback,manager.sys
!inetd.net -k
!continue
!abortjob ftpmon,manager.sys
!nscontrol stop
!netcontrol stop
!file tape=!hpjobname;dev=7
!store /;*tape;directory;show;progress
!netcontrol start;net=lan1
!netcontrol start;net=loop
!nscontrol start
!stream jinetd.net
!stream jftpstrt.net
!eoj

Doug Werth                                     Beechglen Development Inc.
[log in to unmask]                                       Cincinnati, Ohio

The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.