SatEnthu
1 Copper

What is actually upgraded by initiating the upgrade_repv1_to_repv2 -start command?

Jump to solution

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

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
chrisv2
1 Copper

Re: What is actually upgraded by initiating the upgrade_repv1_to_repv2 -start command?

Jump to solution

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:

  • Offers the ability to run pre-upgrade checks prior to actual upgrade (-check option)
  • Aborts all V1 replication sessions
  • Turns off the V1 replication license
  • Configures authentication and interconnects
  • Turns on the V2 replication license
  • Configures V2 replications to correspond to V1 configured sessions.

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

  • All types of replications, local, loopback and remote will be upgraded.
  • File system and VDM replications will be upgraded.
  • The upgrade script can be run on either the source or destination Control Station of a configured Replicator V1 session.
  • Only V1 replications in a configured state will be upgraded.
  • All reachable replication-configured systems (source and destination site) are upgraded.

View solution in original post

0 Kudos
3 Replies

Re: What is actually upgraded by initiating the upgrade_repv1_to_repv2 -start command?

Jump to solution

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..

SatEnthu
1 Copper

Re: What is actually upgraded by initiating the upgrade_repv1_to_repv2 -start command?

Jump to solution

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.

0 Kudos
chrisv2
1 Copper

Re: What is actually upgraded by initiating the upgrade_repv1_to_repv2 -start command?

Jump to solution

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:

  • Offers the ability to run pre-upgrade checks prior to actual upgrade (-check option)
  • Aborts all V1 replication sessions
  • Turns off the V1 replication license
  • Configures authentication and interconnects
  • Turns on the V2 replication license
  • Configures V2 replications to correspond to V1 configured sessions.

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

  • All types of replications, local, loopback and remote will be upgraded.
  • File system and VDM replications will be upgraded.
  • The upgrade script can be run on either the source or destination Control Station of a configured Replicator V1 session.
  • Only V1 replications in a configured state will be upgraded.
  • All reachable replication-configured systems (source and destination site) are upgraded.

View solution in original post

0 Kudos