Open topic with navigation

Protecting files and folders

Use these instructions to protect your files and folders.

1. Click Get Started from the toolbar.
2. Select Double-Take Availability and click Next.
3. Select Protect files and folders or an entire server and click Next.

4. Choose your source server. This is the server that contains the files and folder that you want to protect.

   

   • Current Servers—This list contains the servers currently available in your console session. Select your source server from the list.
   • Find a New Server—If the server you need is not in the Current Servers list, click the Find a New Server heading. From here, you can specify a server along with credentials for logging in to the server. If necessary, you can click Browse to select a server from a network drill-down list.

   To best prepare for a potential failover, restore, and failback scenario, you may want to use a source server that has been inserted into the console by a private IP address. In this scenario, your source must have at least two IP addresses, one for public communication and one for private. If you insert your source in the console using the private IP address, then that private IP address can more easily be used after a failure to restore the data that changed during failover from the target back to the source. If your source server has already been inserted into the console by name, you can remove it and reinsert it by private IP address on the Manage Servers page.

    

5. Click Next to continue.
6. Choose the data you want to protect. Under Server Workloads, select Files and Folders in the left pane and the volumes you want to protect in the right pane.

7. If you want to select your files and folders in more detail, click the Replication Rules heading and expand the volumes under Folders. Items with a green highlight are included in the protection. Items highlighted in yellow have a subset of the items included in the protection. If there is no highlight, the item is not included for protection. To modify the items selected for protection, highlight a volume, folder, or file and click Add Rule. You can also enter a rule, including a wildcard specification, manually. Specify if you want to Include or Exclude the item from protection. Also, specify if you want the rule to be recursive, which indicates the rule should automatically be applied to the subdirectories of the specified path. If you do not select Recurse, the rule will not be applied to subdirectories.

   If you need to remove a rule, highlight it in the list at the bottom and click Remove Rule. Be careful when removing rules. Double-Take Availability may create multiple rules when you are adding directories. For example, if you add C:\Data to be included in protection, then C:\ will be excluded. If you remove the C:\ exclusion rule, then C:\Data rule will be removed also.

   

8. Click Next to continue.

9. Choose your target server. This is the server that will store the replica data from the source.

   

   • Current Servers—This list contains the servers currently available in your console session. Select your target server from the list.
   • Find a New Server—If the server you need is not in the Current Servers list, click the Find a New Server heading. From here, you can specify a server along with credentials for logging in to the server. If necessary, you can click Browse to select a server from a network drill-down list.
10. Click Next to continue.

11. You have many options available for your files and folders job. Configure those options that are applicable to your environment.

    Click a link below to see the options available for that section of the Set Options page.

    Job Name 

    If desired, specify a unique name for your job.

    Failover Monitor

    

    • Monitor these addresses and add them to the selected target adapter after failover—Select each Source IP Address that you want the target to monitor. A selected IP address has a checkmark in the box next to it. In the event all of the monitored IP addresses fail, failover will be triggered.

      If you want to disable failover, do not select any IP addresses. In this case, if your source server fails, your data will be available on your target, but you will not be able to failover to the target. If you want to be able to failover to the target, but you do not want Double-Take Availability to actively monitor (ping) the source, select at least one IP address to monitor, but configure the Monitoring method to No monitoring.

      For each IP address on the source, select the Target Network Adapter that will assume that IP address during failover.

      If you have inserted your source server into the console using a private IP address, do not select the private IP address for monitoring and failover.

       

    • Consider the source server failed after this duration—The target sends monitor requests to the source to determine if it is online. Specify the length of time, in hours:minutes:seconds, to wait before triggering failover when the target has not received responses from the source to its monitor requests. Consider a shorter amount of time for servers, such as a web server or order processing database, which must remain available and responsive at all times. Shorter times should be used where redundant interfaces and high-speed, reliable network links are available to prevent the false detection of failure. If the hardware does not support reliable communications, shorter times can lead to premature failover. Consider a longer amount of time for machines on slower networks or on a server that is not transaction critical. For example, failover would not be necessary in the case of a server restart.
    • Monitoring method—This option determines how the target monitors the source for a failure.
    • Network service—Source availability will be tested by an ICMP ping to confirm the route is active.
    • Replication service—Source availability will be tested by pinging the Double-Take service.
    • Network and replication services—Source availability will be tested by both an ICMP ping to confirm the route is active and by pinging the Double-Take service.
    • No monitoring—Double-Take Availability will not actively monitor the source. You will be responsible for identifying when a failure has occurred and initiating failover manually.
    Failover Options

    

    • Wait for user to initiate failover—By default, the failover process will wait for you to initiate it, allowing you to control when failover occurs. When a failure occurs, the job will wait for you to manually initiate the failover process. Disable this option only if you want failover to occur immediately when a failure occurs. This option is not configurable if the Monitoring method is set to No Monitoring.

    • Fail over IP addresses—By default, the IP addresses you selected to monitor will be failed over to the target. If desired, you can select to fail over all of the IP addresses on the source. If you do not want to fail over any IP addresses, disable this option.

      If you configure all IP addresses to fail over but are only monitoring a subset of your address, you may have IP address conflicts after failover. For example, if you monitor two out of three addresses, and those two addresses fail but the third one does not, if you fail over all three IP addresses, the third address that did not fail may exist on both the source and the target, depending on the cause of the failure. Therefore, when a source is failing over more IP addresses than are being monitored, there is a risk of an IP address conflict.

      If your network environment is a WAN configuration, do not fail over your IP addresses unless you have a VPN infrastructure so that the source and target can be on the same subnet, in which case IP address failover will work the same as a LAN configuration. If you do not have a VPN, you can automatically reconfigure the routers via a failover script (by moving the source's subnet from the source's physical network to the target's physical network). There are a number of issues to consider when designing a solution that requires router configuration to achieve IP address failover. Since the route to the source's subnet will be changed at failover, the source server must be the only system on that subnet, which in turn requires all server communications to pass through a router. Additionally, it may take several minutes or even hours for routing tables on other routers throughout the network to converge.

       

    • Fail over server name—Be default, the server name will be failed over to the target. Double-Take Availability checks the hosts file and uses the first name there. If there is no hosts file, Double-Take Availability will use the first name in DNS. (Keep in mind, the first name in DNS may not always be the same each time the DNS server is rebooted.) Lastly, if there is no DNS server, Double-Take Availability will use the failover monitor name created by the Double-Take Console. If you do not want to fail over the server name, disable this option.

    • Fail over shares—By default, shares will be failed over to the target. If you do not want to fail over shares, disable this option.

      Automatic share failover only occurs for standard Windows file system shares. Other shares must be configured for failover through the failover scripts or created manually on the target. See Macintosh shares or NFS Shares for more information.

      If you are failing over Windows shares but your source and target do not have the same drive letters, you must use the All to One selection under Network Route & Folder Selection when establishing your job. Otherwise, the shares will not be created on the target during failover.

      If a Windows share is created on Windows 2003 with the default full access permissions (without an ACL) and then failed over, the permissions given to the target will be read-only permissions.

      Windows share information is automatically updated on the target once an hour.

       

    • Scripts—You can customize failover and failback by running scripts on the source and target. Scripts may contain any valid Windows command, executable, or batch file. The scripts are processed using the same account running the Double-Take service, unless you have identified a specific account through the server's properties. Examples of functions specified in scripts include stopping services on the target before failover because they may not be necessary while the target is standing in for the source, stopping services on the target that need to be restarted with the source’s machine name and/or IP address, starting services or loading applications that are in an idle, standby mode waiting for failover to occur, notifying the administrator before and after failover or failback occurs, stopping services on the target after failback because they are no longer needed, stopping services on the target that need to be restarted with the target machine’s original name and/or IP address, and so on. There are four types of failover and failback scripts.

      • Pre-failover script—This script runs on the target at the beginning of the failover process. Specify the full path and name of the script file.
      • Post-failover script—This script runs on the target at the end of the failover process. Specify the full path and name of the script file.
      • Pre-failback script —This script runs on the target at the beginning of the failback process. Specify the full path and name of the script file.
      • Post-failback script—This script runs on the target at the end of the failback process. Specify the full path and name of the script file.
      • Arguments—Specify a comma-separated list of valid arguments required to execute the script.
      • Delay until script completes—Enable this option if you want to delay the failover or failback process until the associated script has completed. If you select this option, make sure your script handles errors, otherwise the failover or failback process may never complete if the process is waiting on a script that cannot complete.

      Scripts will run but will not be displayed on the screen if the Double-Take service is not set to interact with the desktop. Enable this option through the Windows Services applet.

    Network Route & Folder Selection

    

    • Send data to the target server using this route—Specify the IP address on the target that the data will be transmitted through. This allows you to select a different route for Double-Take Availability traffic. For example, you can separate regular network traffic and Double-Take Availability traffic on a machine with multiple IP addresses.

    • Mappings—Specify the location on the target where the replica of the source data will be stored. By default, the replica source data will be stored in the same directory structure on the target, in a one-to-one configuration. Make sure you update this location if you are protecting multiple sources or jobs to the same target. Double-Take Availability offers two pre-defined locations as well as a custom option that allows you to set your path.

      • All To One—Click this button to set the mapping so that the replica source data will be stored on a single volume on the target. The pre-defined path is \source_name\volume_name. If you are protecting multiple volumes on the source, each volume would be stored on the same volume on the target. For example, C:\data and D:\files for the source Alpha would be stored in C:\alpha\C and C:\alpha\D, respectively.
      • One To One—Click this button to set the mapping so that the replica source data will be stored in the same directory structure on the target. For example, C:\data and D:\files on the source will be stored in C:\data and D:\files, respectively, on the target.
      • Custom Location—If the pre-defined options do not store the data in a location that is appropriate for your network operations, you can specify your own custom location where the replica source data will be stored. Click the Target Path and edit it, selecting the appropriate location.

      If you are protecting dynamic volumes or mount points, your location on the target must be able to accommodate the amount of data that may be stored on the source.

      If you are protecting multiple mount points, your directory mapping must not create a cycle or loop. For example, if you have the C: volume mounted at D:\C and the D: volume mounted at C:\D, this is a circular configuration. If you establish a job for either C:\D or D:\C, there will be a circular configuration and Double-Take Availability mirroring will never complete.

      If you are protecting sparse files and your location on the target is a non-NTFS 5 volume, the amount of disk space available must be equal to or greater than the entire size of the sparse file. If the target location is an NTFS 5 volume, the amount of disk space available must be equal to or greater than the on-disk size of the sparse file.

       

    • Block target paths upon connection—You can block writing to the replica source data located on the target. This keeps the data from being changed outside of Double-Take Availability processing. After failover, any target paths that are blocked will be unblocked automatically during the failover process so that users can modify data on the target after failover. During restoration, the paths are automatically blocked again. If you failover and failback without performing a restoration, the target paths will remain unblocked.
    Snapshots & Compression

    

    A snapshot is an image of the source replica data on the target taken at a single point in time. Snapshots allow you to view files and folders as they existed at points of time in the past, so you can, for example, recover from cases where corrupted source data was replicated to the target. When failover is triggered, you can use the live target data at the time of failover or you can failover to a snapshot of the target data.

    • Enable scheduled snapshots—Enable snapshots if you want to be able to use them at failover time. If snapshots are disabled, the live data on the target at failover time will be used.
    • Take snapshots on this interval—Specify the interval (in days, hours, or minutes) for taking snapshots.
    • Begin immediately—Select this option if you want to start taking snapshots immediately after the protection is established.
    • Begin at this time—Select this option if you want to start taking snapshots starting at a later date and time. Specify the date and time parameters to indicate when you want to start.

    • Enable compression—To help reduce the amount of bandwidth needed to transmit Double-Take Availability data, compression allows you to compress data prior to transmitting it across the network. In a WAN environment this provides optimal use of your network resources. If compression is enabled, the data is compressed before it is transmitted from the source. When the target receives the compressed data, it decompresses it and then writes it to disk. On a default Double-Take Availability installation, compression is disabled. To enable it, select this option and set the level from Minimum to Maximum to suit your needs.

      Keep in mind that the process of compressing data impacts processor usage on the source. If you notice an impact on performance while compression is enabled in your environment, either adjust to a lower level of compression, or leave compression disabled. Use the following guidelines to determine whether you should enable compression:

      • If data is being queued on the source at any time, consider enabling compression.
      • If the server CPU utilization is averaging over 85%, be cautious about enabling compression.
      • The higher the level of compression, the higher the CPU utilization will be.
      • Do not enable compression if most of the data is inherently compressed. Many image (.jpg, .gif) and media (.wmv, .mp3, .mpg) files, for example, are already compressed. Some images files, such as .bmp and .tif, are uncompressed, so enabling compression would be beneficial for those types.
      • Compression may improve performance even in high-bandwidth environments.
      • Do not enable compression in conjunction with a WAN Accelerator. Use one or the other to compress Double-Take Availability data.

      All jobs from a single source connected to the same IP address on a target will share the same compression configuration.

       

    Scripts

    

    You can customize mirroring by running scripts on the target at pre-defined points in the mirroring process. Scripts may contain any valid Windows command, executable, or batch file. The scripts are processed using the same account running the Double-Take service, unless you have identified a specific account through the server's properties. There are three types of mirroring scripts.

    • Mirror Start—This script starts when the target receives the first mirror operation. In the case of a difference mirror, this may be a long time after the mirror is started because the script does not start until the first different data is received on the target. If the data is synchronized and a difference mirror finds nothing to mirror, the script will not be executed. Specify the full path and name of the Script file.
    • Mirror Complete—This script starts when a mirror is completed. Because the mirror statistics may indicate a mirror is at 99-100% when it is actually still processing (for example, if files were added after the job size was calculated, if there are alternate data streams, and so on), the script will not start until all of the mirror data has been completely processed on the target. Specify the full path and name of the Script file.
    • Mirror Stop—This script starts when a mirror is stopped, which may be caused by an auto-disconnect occurring while a mirror is running, the service is shutdown while a mirror is running, or if you stop a mirror manually. Specify the full path and name of the Script file.
    • Arguments—Specify a comma-separated list of valid arguments required to execute the script.
    • Allow script to interact with desktop—Enable this option if you want the script processing to be displayed on the screen. Otherwise, the script will execute silently in the background.
    • Delay until script completes—Enable this option if you want to delay the mirroring process until the associated script has completed. If you select this option, make sure your script handles errors, otherwise the mirroring process may never complete if the process is waiting on a script that cannot complete.
    • Test—You can test your script manually by clicking Test. Your script will be executed if you test it. If necessary, manually undo any changes that you do not want on your target after testing the script.

    Mirror scripts are dependent on the target and the Target Path Mappings specified under the Network Route & Folder Selection section. If you establish mirroring scripts for one job and then establish additional jobs to the same target using the same target path mapping, the mirroring scripts will automatically be applied to those subsequent jobs. If you select a different target path mapping, the mirroring scripts will have to be reconfigured for the new job(s).

     

    Mirror, Verify & Orphaned Files

    

    • Mirror all files—All protected files will be mirrored from the source to the target.
    • Mirror different files—Only those protected files that are different based on date and time, size, or attributes will be mirrored from the source to the target.

    • Mirror only if the file on the source is newer than the copy on the target—Only those protected files that are newer on the source are mirrored to the target.

      If you are using a database application, do not use this option unless you know for certain that you need it. With database applications, it is critical that all files, not just some of the files that might be newer, get mirrored.

       

    • Use block checksum for comparisons—For those files flagged as different, the mirroring process can perform a block checksum comparison and send only those blocks that are different.
    • Behavior when automatically reconnecting—Specify which mirroring option to use when Double-Take Availability automatically reconnects an existing protection.

    • Calculate size of protected data upon connection—Specify if you want Double-Take Availability to determine the mirroring percentage calculation based on the amount of data being protected. If the calculation is enabled, it is completed before the job starts mirroring, which can take a significant amount of time depending on the number of files and system performance. If your job contains a large number of files, for example, ten thousand or more, you may want to disable the calculation so that data will start being mirrored sooner. Disabling calculation will result in the mirror status not showing the percentage complete or the number of bytes remaining to be mirrored.

      The calculated amount of protected data may be slightly off if your data set contains compressed or sparse files.

       

    • Enable scheduled verification—Verification is the process of confirming that the source replica data on the target is identical to the original data on the source. Verification creates a log file detailing what was verified as well as which files are not synchronized. If the data is not the same, can automatically initiate a remirror, if configured. The remirror ensures data integrity between the source and target. When this option is enabled, Double-Take Availability will verify the source replica data on the target and generate a verification log.

      Because of the way the Windows Cache Manager handles memory, machines that are doing minimal or light processing may have file operations that remain in the cache until additional operations flush them out. This may make Double-Take Availability files on the target appear as if they are not synchronized. When the Windows Cache Manager releases the operations in the cache on the source, the files will be updated on the target.

       

    • Verify on this interval—Specify the interval between verification processes.
    • Begin immediately—Select this option if you want to start the verification schedule immediately after the job is established.
    • Begin at this time—Select this option if you want to start taking snapshots at the specified date and time.
    • Mirror files to the target server when verifying—When this option is enabled, in addition to verifying the data and generating a log, Double-Take Availability will also mirror to the target any protected files that are different on the source.

    • Mirror only if the file on the source is newer than the copy on the target—If you are mirroring files to the target during the verification process, select this option if you only want to mirror protected files that are newer on the source than on the target.

      If you are using a database application, do not use this option unless you know for certain that you need it. With database applications, it is critical that all files, not just some of the file that might be newer, get mirrored.

       

    • Use block checksum for comparisons—Select this option to have the verification process perform a block checksum comparison to determine which block are different.
    • Log orphaned files—An orphan file is a file that exists in the source replica data on the target, but does not exist in the protected data on the source. For example, an orphan file may be created if you delete a protected file from the source while the job is stopped. Because the job is stopped, the delete operation is not replicated to the target, so the file is not deleted on the target. This option specifies if orphaned files are logged to the Double-Take Availability log file on the target during a mirror or verification.

    • Move or delete orphaned files—Enable this option to move or delete orphaned files on the target during a mirror or verification.

      • Move or delete all orphaned files—Select this option if you want move or delete all orphaned files.
      • Move or delete orphaned files not modified in the last—Select this option if you want to move or delete only those orphaned files older than the specified time.
      • Delete orphaned files—Select this option if you want to delete orphaned files.
      • Move orphaned files to this folder—Select this option if you want to move orphaned files. Identify the location on the target where you want to move the orphaned files. Make sure the location you specify is not included in the location where the source replica data is located so that the orphaned files are only moved once.

      Orphan file configuration is a per target configuration. All jobs to the same target will have the same orphan file configuration.

      The orphans feature does not move or delete alternate data streams. To do this, use a full mirror, which will delete the additional stream(s) when the file is re-created.

      If Double-Take Availability is configured to move orphan files, the Double-Take Availability log file will indicate that orphan files have been deleted even though they have actually been moved. This is a reporting issue only.

      If delete or move orphaned files is enabled, carefully review any replication rules that use wildcard definitions. If you have specified wildcards to be excluded from protection, files matching those wildcards will also be excluded from orphan file processing and will not be deleted from the target. However, if you have specified wildcards to be included in your protection, those files that fall outside the wildcard inclusion rule will be considered orphaned files and will be deleted from the target.

       

    Bandwidth

    

    Bandwidth limitations are available to restrict the amount of network bandwidth used for Double-Take Availability data transmissions. When a bandwidth limit is specified, Double-Take Availability never exceeds that allotted amount. The bandwidth not in use by Double-Take Availability is available for all other network traffic.

    • Do not limit bandwidth—Double-Take Availability will transmit data using 100% bandwidth availability.
    • Use a fixed limit—Enter a value, in bytes per second, to limit data transmission. This is the maximum amount of data that will be transmitted per second.
    • Use scheduled limits—Use a schedule to limit bandwidth for different times. Schedules that you create will be maintained if you change to a fixed limit or to no limit.
    • New—Click New to create a new scheduled bandwidth limit. Specify the following information.
    • Daytime entry—Select this option if the start and end times of the bandwidth window occur in the same day (between 12:01 AM and midnight). The start time must occur before the end time.
    • Overnight entry—Select this option if the bandwidth window begins on one day and continues past midnight into the next day. The start time must be later than the end time, for example 6 PM to 6 AM.
    • Day—Enter the day on which the bandwidth limiting should occur. You can pick a specific day of the week, Weekdays to have the limiting occur Monday through Friday, Weekends to have the limiting occur Saturday and Sunday, or Every day to have the limiting repeat on all days of the week.
    • Start time—Enter the time to begin bandwidth limiting.
    • End time—Enter the time to end bandwidth limiting.
    • Preset bandwidth—Select a bandwidth limit rate from the common bandwidth limit values. The Bandwidth field will automatically update to the bytes per second value for your select bandwidth.
    • Bandwidth—If desired, modify the bandwidth using a bytes per second value. The minimum limit should be 28000 bytes per second.
    • Edit—Click Edit to modify an existing scheduled bandwidth limit.
    • Delete—Click Delete to remove a scheduled bandwidth limit.

    All jobs from a single source connected to the same IP address on a target will share the same bandwidth configuration.

     

12. After you have configured your options, click Next to continue.

13. Double-Take Availability validates that your source and target are compatible for your job type. The Summary page displays the options you selected in your workflow and any additional validation items.

    Errors are designated by a white X inside a red circle. Warnings are designated by a black exclamation point (!) inside a yellow triangle. A successful validation is designated by a white checkmark inside a green circle. Click on any of the validation items to see details. You must correct any errors before you can enable protection. Depending on the error, you may be able to click Fix or Fix All and let Double-Take Availability correct the problem for you. For those errors that Double-Take Availability cannot correct automatically, you will need to modify the source or target to correct the error, or you can select a different target. You must revalidate the selected servers, by clicking Recheck, until the validation check passes without errors.

14. Once your servers have passed validation and you are ready to establish protection, click Finish, and you will automatically be taken to the Manage Jobs page.