Re: P7 V7R3 to P9 V7R3 migration recommendations / suggestions -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: Re: P7 V7R3 to P9 V7R3 migration recommendations / suggestions
From: Holger Scherer <hs@xxxxxxx>
Date: Fri, 2 Nov 2018 00:14:55 +0100
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Paul,
besides the (usual) tip to NOT use BRMS, we mostly do migrations
using High availability software. Create SAVE21 of the sources
(without BRMS), load them to the target. Then setup a mirror,
wait until mirror is synced, then do a switchover within some minutes.

Depending on the software vendor you might get a cheap 4 week licensing
option for only a switchover. And if you test the software, you
might want to keep it ;-)

-h

Am 01.11.2018 um 19:42 schrieb Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>:

3) Any other migration or recovery suggestions from the group?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: P7 V7R3 to P9 V7R3 migration recommendations / suggestions , 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.