Re: Restricted State problem during backup -- MIDRANGE-L

We do a little CHKTAP in our backup to make sure that the tape is loaded 
and ready to go.  We also use RCVMSG to verify the volid.  Then we use 
that VOLID to INZTAP back to it's original VOLID.  If the CHKTAP fails we 
send an email and abort the backup.  Of course, this is done prior to any 
other preparations like dropping jobs, etc.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





daparnin@xxxxxxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/28/2004 10:13 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re: Restricted State problem during backup










What about TCP/IP?  If you shut it down too then you might still have a
hard time getting connected.

We also shut down most all subsystems at backup time since we do
save-while-active.  I also end TCP/IP to kill any potential ODBC, IFS, and
FTP connections.  Maybe this is overkill but I'm paranoid.  As a result,
the system is unaccessable for about 30 minutes while the SWA checkpoint 
is
being established.  This did bite me a couple of weeks ago when the tape
drive had a hardware problem and the SWA command got stuck waiting for a
message that the tape device was unavailable.  The only option was for me
to drive in and restart things (over 40 miles!).  Not my idea of a fun
evening.

As for pager messages, we also get them.  We send a page when the backup
starts, when the subsystems have been restarted, and when the saves end.
If you don't get the restart message and can't connect remotely within 30
minutes of when you should have received it then it's time to get in the
car.  Luckily, this is a rare event for us.

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx




  
                      ron_adams@cranevalve   
                      .com                        To:       Midrange 
Systems Technical Discussion 
                      Sent by: <midrange-l@xxxxxxxxxxxx>@SMTP@CTB    
                      midrange-l-bounces@m        cc:       (bcc: David A 
Parnin/Topeka/NISCO/SPCO) 
                      idrange.com                 Subject:  Re: Restricted 
State problem during backup 
  
  
                      09/28/2004 09:37 AM   
                      Please respond to   
                      Midrange Systems   
                      Technical Discussion   
                      <midrange-l@midrange   
                      .com>  
  
  



First, Do you find it really necessary to a nightly restricted state
backup? We do ours once a week, on the weekend.
Second, do you have a console? If not, enable the QREMOTE subsystem and
set it up so only specific device names will work there via the Work
Station Name Entries.
This will enable the operator or anyone else with a specifically named
device, such as (QCON01, or QOPR01 or whatever) to access the system when
it is restricted. You must remember to NOT end this subsystem when you
shutdown everything else.


Ron Adams
Information Technology Group
Crane Valves
9200 New Trails Dr. Suite 200
The Woodlands, TX 77385






Mike Berman <mikeba777@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/28/2004 09:27 AM
Please respond to Midrange Systems Technical Discussion


        To:     Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
        cc:
        Fax to:
        Subject:        Restricted State problem during backup



We do a nightly backup, first we shut down all subsystems, including
QINTER. Thr problem w/ that is if there is a problem w/ the backup, there
is no way for the operator to do anything about it. We have the ACO pager
that will alert messages, but then the job sits there until the morning.


---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.