arcserve-KB : How to create a arcserve RHA D2D integrated scenario when performing scheduled synchronization from a NAS to a NAS

Last Update: 2016-04-25 14:24:14 UTC


There are many times when a NAS is being used as the destination for CA ARCserve D2D backups in the Master site and then another NAS is the target for the replication of those backups with CA ARCserve RHA. This document describes the procedure in order to configure the D2D integrated scenario to Replicate D2D backup folders from one NAS device to another and addresses best practices as well as explains how the scheduled synchronization within CA ARCserve RHA scenario function for this purpose.


Note:  The procedure below is slightly different depending on the version of RHA in use.  Please verify the version of RHA in use and follow the proper procedure identified for that version.

  1. If you are using RHA R16.5  Create a 'D2D scenario' within CA ARCserve Replication
    1. Click Scenario, then click New in the menu
      1. In RHA R16.5 Select the 'ARCserve D2D' scenario type and then click 'Finish'
      2. If you are using RHA R16.1 Select the 'File Server' scenario type, select 'Disaster Recovery (DR)' product type, and check off 'D2D Integration', then click 'Finish'
    2. Next rename the scenario and add the Master server name/IP and Replica server name/IP under hosts in the left pane
    3. Save the scenario
    4. Next select the Master host from the left pane and then click on the 'Root Directories' tab on the right pane
    5. Start by entering the UNC paths that point directly to each D2D Backup folder as root directories in the right hand pane. The first location simply needs to be modified by clicking on 'Enter directory here. ...'.
      1. For this part make sure that each root directory matches the location of the D2D folder. To determine which folders need to be added open a Windows Explorer and browse to the base folder through the UNC path.
      2. i.e. \\NAS1\d2dshare\backups
      3. Within this folder you need to look for the D2D enabled folders that will appear as blue folders and each of these needs to be added to the scenario as a separate root directory
      4. i.e.
      5. To add them on the root directories tab follow these steps:
        1. Right click 'Directories' at the top of the Root Directories tab and then click on 'Insert Directory'
        2. Then click 'Enter directory here...' and add the root folder for that backup folder
        3. i.e. \\nas1\d2dshare\backups\rmw8app
        4. Once added, click on the 'Filter' column next to this root directory
        5. Then click 'Edit' and then 'Set Filter' from the menu and add an exclusion filter for '*.vvl *.mrg'
        6. Continue steps 1-5 for each D2D backup folder found in the Master NAS directory.
        7. Once completed it will look similar to this
        8. Now click 'Scenario' then 'Save' from the menu
    6. Next you will need to add the Replica root directories that will be replicated to.
      1. To do this select the Replica host from the left pane in the scenario
      2. Then click on the Root Directories tab on the right pane
      3. It should look like this
      4. You will now want to add the folders that each of these will be replicating to via the Replica NAS
      5. i.e. \\nas2\mspshare\customer1\rmw8app
      6. You do this by clicking on 'Enter directory here...' and then type or paste the directory into the textbox
      7. i.e.
      8. Once completed click 'Scenario' then 'Save' from the menu
  2. Next you will want to configure the scenario settings for Scheduled Synchronization and also make sure 'Run After Reboot' settings are configured with the proper synchronization method.
    1. First select the scenario name in the left pane
    2. Then click on the Properties tab on the right pane
    3. Expand 'Replication', then 'Run after Reboot', then 'Automatic Synchronization' and make sure that 'Block Synchronization' and 'Ignore Files of Same Size/Time' is 'ON'
    4. i.e.
    5. Next in this same tab under 'Replication', next to 'Mode' click the value that says 'Online' and choose 'Scheduling'
    6. Then next to 'Schedule Setting' click on the 'Not Set' value and a wizard will appear.
    7. At this time it is a good idea for you to understand how Scheduling mode works.
      1. *** IMPORTANT NOTE *** the times in this wizard are START synchronization times only! This means that if a scheduled time is hit, the scenario will start a synchronization again regardless of whether the previous synchronization was completed or not! So if the schedule is too aggressive and the synchronization does not complete in the time that it takes for the next scheduled time is hit the data not synchronized will be missed. The synchronization will continue until it is complete or a new scheduled time is hit as there is no scheduled 'stop' times.
      2. So it is best practices to run (2) two manual synchronizations with the scenario prior to creating the schedule. The first synchronization to populate the data that is empty on the Replica side and the second to determine what a standard block synchronization will take between these two machines and NAS devices. To run a synchronization without starting the scenario click 'Tools', then 'Synchronize' from the menu.
      3. Once you know how long a standard Block Synchronization takes you will then want to create the schedule in the Wizard.
        1. To do this Select the hour(s) in the day(s) that you want the synchronization to Start and then click the 'Set' button. in the below screen shot I have selected to perform a scheduled synchronization at 6pm (1800) once a day
        2. You can also set the schedule at certain hourly intervals with the 'Every hours' setting and then hit 'Apply', again make sure that you know how long the synchronization takes as setting this too aggressively can cause data to not be synchronized.
        3. Once the schedule is set, click 'OK' and then save the scenario.
  3. At this point the scenario is ready to be started and synchronized. Remember to perform at least (2) two synchronizations prior to configuring the synchronization schedule.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request