RE: BRMS system save strategy -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: BRMS system save strategy
From: Rob Berendt <rob@xxxxxxxxx>
Date: Tue, 25 Oct 2016 15:43:50 -0400
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/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The BRMS exits make perfect sense.

We tend to not save the network storage spaces anyway. Kind of figure a
disaster would give me an excuse to rebuild the guested lpars with a
better balancing. Maybe more NWSD's with fewer NWSSTG spaces on each of
them or whatever I feel the performance balance might be. When an lpar
creep grows you'll build it one way versus one you rebuild.

However, when I do my old ssd to newer ssd migration I will probably save
the storage spaces to make the unload/reload of the system as a whole much
faster.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: BRMS system save strategy , Steinmetz, Paul

This mailing list archive is Copyright 1997-2026 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.