Welcome to the Dell Technologies Aamar How two series, how to configure plug-in based replication to run longer than 24 hours. Reference Dell Knowledge article number 58188. This video was created to show the steps required to configure over time including updating the M CS go the group policy and the M CS configuration.
The notes section at the end includes an additional step required for Aamar grids running 7.5 0.1 or lower in most situations, 24 hours should be sufficient to complete replication. However, there may be circumstances that require this to be extended such as an initial or catch up replication.
If replication jobs regularly fail to complete within the assigned window, please contact the Dell EMC Aamar support team for assistance. You will need access to Putty and the A Magui, the name or IP address of the AAR utility node and the admin and MC user passwords.
You will also require sufficient UNIX knowledge to use a file editor such as vi first, we need to update the replication client to allow overtime. After logging in open the policy screen, click on the clients tab, select the MC system domain and highlight the client.
In most cases, this will be the ami utility node, click edit from the properties tab change the overtime option to always allow overtime and click. OK. Now we need to update the replication group policies. Click on data movement policy to list the existing replication groups.
Double click on the group name to edit. In our example, this is replication. One click on seven overview, select more options followed by more. Please verify the plug and type is replicate as shown on screen in the enter attribute field type, repel script enclosed within square brackets followed by time out.
And then 999999 in the enter attribute value field, click on the plus symbol to add the attribute and value and OK to save, you will then be returned to the previous screen. Verify the rebel script setting appears in more options and then click finish as noted earlier, these steps must be repeated for each group that requires overtime.
Now we need to update the M CS configuration as admin navigate to the directory shown on screen, check for any existing configuration files by typing the LS command shown and review the output. Make a backup of the current configuration file again. An example is shown on screen, repeat the LS command to verify that the backup file exists using V I or equivalent edit the MC server dot XML file.
Locate the entry form repel underscore window underscore hours and change the value from 24 hours to the desired value. In our example, we change this to 48 save the file and exit. If you wish to verify the changes, you can use the diff command. As shown to see the changes between the two files, check the current services by typing DPN CTL status.
This will take a little time to complete. If M CS is up, it must be restarted for the changes to take effect type DPNCTL stop M CS. This can take minutes to complete once shut down restart M CS by typing DPNCTL start M CS again. This can take minutes to complete once M CS has started, finish the procedure by restarting the backup scheduler type dpnctl start shed and the scheduler will resume.
Please take note of the following step required for AAR version 7.5 0.1 and lower. It is strongly advised that extending the 24 hour limit only be changed short term again. If replication jobs regularly fail to complete within the assigned window, please contact the Dell EMC Aamar support team for assistance. Please refer to the knowledge article 58 188 for more information.
Thank you for watching.
