Re: Backup Question

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

I don't know ROBOT well enough to know if it has a similar function, but 
BRMS can be submitted one of two ways, as Carl uses it, where it submits 
to the controlling subsystem and runs the back up.  In this case the 
console does not have access to the system during the save.  The second 
method is the one Larry is asking about where it goes to the console 
monitor, and then during the save you can see status messages and if 
needed gain access to the system.

My strong preference is to use the console monitor.  Yes it does require 
the console to be in the monitor status all the time, but I think the 
best idea is to sign on the console at the HMC.  Start the monitor and 
leave it.  If you need to remotely access the console you can still do 
that, as long as you put it back into the monitor before you sign 
off.    If you just use the command line from the monitor, then when you 
back out using F3 you'll see the monitor as the very last step, and do 
not sign it off.

In short, sign on the HMC to the console, start the monitor and leave 
it.    Most of my customers that do that are good with making sure the 
monitor is started most all the time.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 3/27/2013 7:49 AM, Carl J Novit wrote:
> We use the Advanced Job Scheduler with BRMS to automate our BRMS full
> system save.
> We have a CL which shuts down various jobs, Domino, iSCSI attached
> xSeries, etc., then submits the BRMS full system save.
> Works perfectly.
>
> Thanks,
>
>
>
>
>
> Carl Novit
> Vice President
> Extension: 7708
>
>
>
>
>
> From:lketzes@xxxxxxxxxxx
> To:midrange-l@xxxxxxxxxxxx,
> Date:   03/27/2013 08:35 AM
> Subject:        Backup Question
> Sent by:midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Hello everyone,
>          Wondering if anyone has similar needs and challenges as ours
> regarding backups:
>
> 1) HMC and system are physically remote.
> 2) Computer operator 'technically' has access to HMC, but they prefer a
> totally 'automated' solution for backups, including Full System Backups.
> 3) I'm used to performing a 'Option 21 Backup' once a week, and changes
> the other nights.
> 4) Our backup solution, Robot Save, like BRMS, has a 'Restricted State
> Utility' which allows you to manually sign on the console before a full
> backup is scheduled to allow for unattended backup.  This option does
> necessitate someone to sign on the console locally once per week to ready
> the system for the Full System Backup.  This currently involves an
> operator to open a console session at the HMC, then execute a couple
> commands.  This task is the one that we are trying to 'automate'.
>
>
> Any ideas?
>
>
> thanks, Larry
>
> Larry Ketzes
> Lead Enterprise Infrastructure Engineer
> lketzes@xxxxxxxxxxx
> 302-594-2146