cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are happy to announce the new Windchill Customization board! Learn more.

What is the mail id of PTC Global Service Team ( Need info on Local Replication for populating the initial Replica's)

bt
4-Participant
4-Participant

What is the mail id of PTC Global Service Team ( Need info on Local Replication for populating the initial Replica's)

I m in need of checking the exact procedure to perform Local Replication. I had raised a case and PTC tech support have closed it saying only PTC global service team can help on it. https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=12652764.

Any one who has tried local replication in 10.2 ? and has worked ?

4 REPLIES 4
GaryMansell
6-Contributor
(To:bt)

   Here's some info that may be of help to you - it's a bit old but I expect its still relevant:




Replica Seeding Method:

The following describes the process used to transfer replicated models and processing to a new replication server. This process can also be used when transferring replicated data to a remote location that has too low of bandwidth to support an initial replication process where large amounts of data need to be transferred across the WAN.

Replication Transfer Process

  1. Setup a replica server on the same network as the master server.
  1. Export the Master Key file, and copy to the replica server.
  2. Install the lightweight replica components.
  3. If possible setup the “Replica Vault” folder to the same location as it will be on the remote replica server. Make mount path as it will be on remote site, so there will be no need to change this when the data is copied over to the remote replica site.
  1. Setup the local replica site on the Master replica server
  1. Set the “Site Name” to the name you want to use for the remote site.
  2. If possible set the “Replica Vault” folder the same as the location on the remote site. This can be changed if needed.
  3. Broadcast Configuration of the replica site to confirm communication with the new replica server.
  4. Define the replication rules for the new site.
  5. Perform the replication to the new server.
  6. When the replication is completed, stop Windchill.
  1. Transfer to external media.
  1. You can simply copy the files located in the “Replica Vault” folder to an external drive.
  2. Copy the Master key to the external drive, or to a location you can access from the remote site.
  3. Transport the external media to the remote site.
  1. Setup a replica server at the remote site.
  1. Copy the master key to a location on the replica server.
  2. Install the lightweight replica components.
  3. Create the vault location folder for the replica data.
  4. Copy the replica data from the external drive to the vault location folder.
  1. Setup the remote replica site on the Master replica server.
  1. In the Site Administrator change the URL to the remote replica server site.
  2. In the Vault Configuration change the hostname.
  3. In the Vault Configuration change the mount path if needed.
  4. Broadcast Configuration of the remote site to confirm communication with between the master and remote sites.

    

The master and remote replication servers should now be setup. Any scheduled replications should transfer models between these two servers.

Replica Seeding Method - 2

  1. Create replica vault on master site
    e.g. replica1_local

  1. On master site set wt.fv.localReplica.<local_vault_name> = true
    e.g. wt.fv.localReplica.replica1_local = true
  2. Create replication rule for replica vault created in step 1.
  3. Replicate content to replica vault by creating replication schedule.
  4. Copy replica content from master site to replica site
    On replica site delete MOUNT_VALIDATION_DATA directory in replica vault
  5. Move replica vault configuration from master site to replica site

    On master site create task file:
      LRMV,<local_vault_name>,<replica_site_name>,<master_host>,<replica_host>

    e.g. $WT_HOME/replica1_local.csv
      LRMV,replica1_local,replica1,wcmaster.ptcnet.ptc.com,wcreplica.ptcnet.ptc.com

    windchill shell
    cd $WT_HOME
    java wt.dataops.replication.ReplicaLoader  $WT_HOME/replica1_local.csv

    

    

  1. Validate replica vault on replica site
    Also make sure replica vault is enabled and NOT read only
    Rename vault and folder as required
bt
4-Participant
4-Participant
(To:GaryMansell)

Thanks a lot Gary for the response. We were trying Replica Seeding Method 2- , but it just replicated around 80 objects and said nothing more to replicate. Where as we  have around 630 GB to be locally replicated. We wanted to try out this method so that we wanted to check the if it is possible to populate the replica site within the cutover period for Production Go Live.

PTC tech support too were not able to populate completely from their try and have asked  to contact PTC Global Service Team for the same..

Regards

Baalajee.T

ChrisSpartz
12-Amethyst
(To:bt)

Generally, to contact global services, you'll need to talk to your sales rep:

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS61473

achaube
7-Bedrock
(To:bt)

Hi,

 

I am facing the same issue. I tried Local replication by Replica Seeding Method 2 but only 216 GB of data has been replicated but we have 1.2 TB of data in source vault. I have mentioned Content holder object and all iterations in Replication rule.Would you please let me know how did your issue get solved.

Thank you in Advance.

 

Regards,

Amar

Top Tags