If you have not done so already, launch the Protecting a BlackBerry Server workflow.
The Advanced tab includes advanced configuration options.
|
The following topics explain how to configure the options on the Advanced tab:
A replication set defines what directories/files are to be protected by Double-Take Availability. By default, Application Manager selects all of the necessary directories/files to protect BlackBerry based on your source server configuration. These include the BlackBerry application data and transaction logs, tempdb files, and BlackBerry error logs. By default, the Application Manager-generated replication set will be named BB_<source server>_<target server>.
You should only modify the replication set rules if there are additional directories/files specific to your configuration that must also be protected with BlackBerry. Modifying the default configuration for replication set rules may affect whether data can be successfully replicated. Do not modify the replication set unless you are very familiar with Double-Take Availability and BlackBerry.
To change the replication set rules:
Note: |
When this box is selected, the Protected Databases control on the Connection tab will be disabled. For more information, see Protected Databases. |
|
Note: |
You will need to manually verify that the rule path is correct since the Application Manager does not validate rule paths. |
Note: |
Removing rules that were automatically added by Application Manager could impact the success of failover. Any changes to rules should be thoroughly tested. |
Scripts are executed at different points during the failover/failback process to perform the actions necessary to make BlackBerry available on the appropriate server.
Editing scripts is an advanced feature. Do not edit scripts unless you fully understand what each command is doing.
Scripts are automatically generated by Application Manager during configuration. The scripts are copied to the Double-Take Availability installation directory on the specified server using the administrative share for that server’s drive.
Script |
File name |
Description |
---|---|---|
Failover |
post_failover_<source>_<target>_bb.bat for distributed environments, or post_failover_<source>_<target>_sql_bb.bat for consolidated environments |
A post-failover script is executed after the core failover processes have completed on the target server. The primary functions of the post-failover script are to start the services on the target and to modify DNS and Active Directory entries as necessary. |
Failback |
pre_failback_<source>_<target>_bb.bat for distributed environments, or pre_failback_<source>_<target>_sql_bb.bat for consolidated environments |
A pre-failback script is executed before failback processing occurs on the target server. The primary functions of this script are to stop services on the target and to move DNS and Active Directory entries as necessary. |
Restore |
post_restore_<source>_<target>_bb.bat for distributed environments, or post_restore_<source server>_<target server>_sql_bb.bat for consolidated environments |
A post-restore script is not executed automatically, though it is provided on the source to perform actions that are generally required after data has been restored from the target to source after a failover/failback. The primary function of this script is to restart services on the source server. |
By default, Application Manager generates all the required scripts for you automatically based on your system configuration. You can also edit the scripts to add, modify, or delete specific commands. To edit a script:
Any change you make to the script in the editor will be copied to the appropriate server when configuration changes are accepted, thus overwriting any changes that have been made outside the Application Manager.
The scripts can be overwritten by certain operations during setup. For example, any changes to configuration options done in the Application Manager will overwrite previous script changes. If you want to make permanent changes to a script, you must modify the appropriate .txt file within the Application Manager installation directory. If there is more than one client machine that will be configuring failover, the change must be made to all the appropriate .txt files.
Before running Application Manager multiple times (for example, when re-enabling protection after a failover/failback), save a copy of your post-restore and pre-failback batch files. After Application Manager executes, replace the default script file(s) with the customized file(s) that you saved.
The following options allow you to control what functions Application Manager will perform during configuration. By default, Application Manager performs all of these functions. Individual functions should only be disabled for testing or debugging purposes.
Note: |
These options are only available when you launch Application Manager using the command line /blackberry /advanced option (dtam /blackberry /advanced). |
|
Note: |
If you are using Active Directory, you should enable this option. Otherwise, you may experience problems with failover. |
Next step: Save configuration settings