RE: Using BRMS for SWA and save to save file?

Thanks Scott, John, and Pete! I was thinking that SWA might be the best
solution, then I remembered Rob's recent post on "poorly implemented"
SWA (objects not saved, who needs a checkpoint, etc.).

The daily save signs off all interactive users (part of the backup
policy) but the system is not in a restricted state. Most of the time
the only objects not saved are three data queues used by the ERP
package. An ENDSBS to the dedicated subsystem monitoring the queues
would fix them as well.

Our production people are good about working with us and the backup
window, but recently they've had more trucks scheduled to ship and
encroaching on our window.

Totally agree with disk utilization and potential slowdowns using
virtual tape or SAVFs. Will look to continue saving directly to tape.

I'll give the SWA sections a good read!

Thanks,
Loyd

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ingvaldson, Scott
Sent: Tuesday, September 01, 2009 10:57 AM
To: Midrange Systems Technical Discussion
Subject: RE: Using BRMS for SWA and save to save file?

But most likely SWA will get you all the uptime you need. The "right"
way to implement SWA is the way that makes sense for your business, but
since you already have two hours of daily downtime taking 15 minutes
(more likely 5) to establish the sync point should not be too difficult.