This post is more than 5 years old
19 Posts
0
803
What is actually upgraded by initiating the upgrade_repv1_to_repv2 -start command?
What gets upgraded by running the following: /nas/sbin/upgrade_repv1_to_repv2 -start
Is underlying replicator code upgraded? Or only converts current replicator v1 sessions to v2? How disruptive can this be on production systems?
Message was edited by: SatEnthu
chrisv2
18 Posts
0
September 14th, 2010 06:00
Hello,
During the script all Celerra Replicator V1 sessions are converted to V2. There should be no impact to your production file systems.Please keep in mind the script is intended for Celerra Certified Engineers or Field Support Specialist (FSS) level or who have equivalent experience and are responsible for upgrading customers from Replicator V1 to Replication V2.They will be able to work with you to ensure the proper procedure is followed.
Here are the basic steps.........
The upgrade script:
While configuring V2 sessions, the script uses the V1 restart checkpoint as a common base and performs a differential copy instead of a full copy.
After the upgrade script completes, the user can configure new Replicator V2 sessions.
How it works
cxCpyIzSVS12414
43 Posts
1
September 13th, 2010 18:00
Upgrades all Replication V1 file system and VDM sessions to V2, not iSCSI replication.
The document "Using Celerra Replicator V2" has information on your query.
Basic steps are to Query for all V1 sessions first, do Verification check [e.g., ensures existence of restart checkpoints, consistent
databases, minimum 5.6.38 code versions, all CS and DMs reachable, that no fs_copy operations are running, that no Replication
sessions are inactive, failed over, or suspended], verify nodes are reachable, abort the V1 sessions, deploy v2 and license, starts
upgrade process, configures DART interconnects, starts Replication V2, cleans up RepV1 restart checkpoints.......
Does this answer your query..
MotoMando
19 Posts
0
September 14th, 2010 06:00
Unfortunately, the "Using Celerra Replicator V2" (300-004-188) document does not mention the "upgrade_repv1_to_repv2" command or script. Fortunately, it is only a conversion of production replication from v1 to v2. There is no actual s/w upgrade involved. - Per EMC Support.