Phased migration from CTE-U 9.x to CTE-U 10.x

Previously, all clients on a CTE-U network had to contain the same version of CTE-U because CTE-U 10.x could read the header files in the CTE-U 9.x files, but it could not write to them. This was cumbersome for large networks that had large numbers of CTE-U 9.x clients accessing multiple GuardPoints over multiple NFS shares. Now, you can perform a phased migration. CTE-U 9.x and CTE-U 10.x clients can exist on the same network and access the same network share because now, CTE-U 10.x can read from, and write to, the header files in CTE-U 9.x and migrate the data to the latest version.

Thales recommends migrating one server at a time. After you migrate the data, run PF Migrate to upgrade from CTE-U 9.x to CTE-U 10.x.

Performing a Phased Migration from 9.x to 10.x

1. Create a file called mapping.json that contains a list of the network shares and clients on the CipherTrust Manager. See Migration of NAS policies for more information on the mapping.json file.

   Note

   The source for the mapping.json file is the client file on the CipherTrust Manager called pfclientinfo.json. See Migrating Cluster Policies for more information on the pfclientinfo.json file.

2. To enable a phased migration, BEFORE registering the client, type:

   export pf_mode=1
   

3. To enable a phased migration AFTER registration, edit the etc/agent.conf file and add:

   pf_mode=1
   

4. Run the migration command, type:

   voradmin secfs config pf_mode 1
   

5. Restart secfs:

   1. Type:

      /etc/cte/secfs stop
      

   2. Wait a few seconds and then type:

      /etc/cte/secfs start
      

See the PF Migrate documentation for more information on the entire migration process.