Triggers a script to run before each synchronization. The synchronization process does not start until this script run is completed.
Enter the full name and path of the script.
Arguments to pass to the script specified in the previous property. Arguments are static values.
Triggers a script to run after each synchronization. The synchronization process does not wait for the script run to finish.
Enter the full name and path of the script.
Arguments to pass to the script specified in the previous property. Arguments are static values.
Compresses data before sending it to the Replica. This option optimizes bandwidth and transfer time.
Encrypts data so that data sent between the Replica and its parent node are transferred securely (also called Secure Communication). This property can only be set on the Replica host, which means this property will not exist on the Master. However, during recovery or when you run backward scenarios, this option will be adjusted so that the link between the two hosts remains secure (or non-secure, for plain data, if this option is set to No Encryption).
Note: See Change the Engine Security Method to define your own security parameters to encrypt the data.
During synchronization, do not remove from the Replica files that were deleted from the Master. Best suited for cases in which several scenarios use the same Replica directories.
During replication, do not remove from the Replica files that were deleted from the Master.
Controls the size of the allowed incoming bandwidth on the Replica host. You can either define one limit size that will apply to all hours of the day, or you can specify different values for different hours. The default value is Unlimited.
For a detailed description of bandwidth scheduling, refer to Schedule the Bandwidth Limit.
When set to On, if a database scenario (Exchange, SQL, Oracle) is running and the database is running on the Replica server, Arcserve RHA stops the database services before running the scenario. [Does not apply to HA scenarios]
This option can be enabled only when the System State Protection property in the Scenario Properties list is set to On. For more information, refer to Protecting Your System State.
These options are relevant only for Windows servers. If changes were received for a busy file (opened as non-shared for read), these options define how many times and at what interval to attempt replacing this file with the one that contains the changes.
Enter the number of attempts to be made for replacing a modified file that is busy (and therefore cannot be replicated). If the file is not released before the last attempt is made, the change is lost and an error message is initiated.
The time between an unsuccessful attempt and the next attempt.
[For File Server only] Defines whether special actions should be triggered via a script, when a specified trigger file appears.
Enter the name of the file that triggers the script, which is specified in the next property. The script is triggered once the file creation event occurs.
This script is invoked, when the trigger file specified in the previous property is created. Enter the full name and path of the script.
Arguments to be passed to the script specified in the previous property. Arguments must be static values.
Lets you enter the user credentials to access the host folder. If the user has no permission to access the root directory, then scenario will not run.
|
Copyright © 2015 Arcserve.
All rights reserved.
|
|