RE: system save -- MIDRANGE-L

Subject: RE: system save
From: "Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>
Date: Wed, 23 Oct 2002 13:51:41 -0400
Importance: Normal
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Todd,

Could you provide a brief description of how BRMS handles this?  I know
that I have written code to wait at the console, dedicate the system,
save the system, and then bring the system back up.  Is this what BRMS
does, or is it different in methodology?  (I'm sure it's more
sophisticated, but is it different in kind?)

Regards,
Andy Nolen-Parkhouse

> On Behalf Of Todd kidwell
> Subject: RE: system save
>
> Tom,
>
> We use BRMS to run scheduled, unattended full system saves in a
restricted
> state.  Works very nice.
>
> Robot/SAVE allows the same thing.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.