You are here: Failover > Full-server workload failover > Failing over from the command line

Failing over from the command line

You can configure connections and initiate failover without using the Full-Server Failover Manager user interface. The same executable that launches the user interface can be used from a command prompt with options. The command line execution opens the user interface, passes through specified parameters, and initiates specified processes. You may want to use this alternate execution if you have different configuration files that you want to execute or if you have multiple connections. The Full-Server Failover Manager command can be initiated one at a time from a command prompt, or it can be scripted. The Full-Server Failover Manager executable is located in the installation directory.

Command

FFMANAGER

Description

Initiates the Full-Server Failover Manager user interface, passes through specified parameters, and initiates specified processes

Syntax

FFMANAGER /SOURCE source_name /TARGET target_name/USERNAME username /PASSWORD password /VALIDATE /FIXALL /PROTECT /FAILOVER /LOGLEVEL number /CONFIG filename

Options

SOURCE source_name—Name of the source
TARGET target_name—Name of the target
USERNAME username—Name of a user who is a member of the Double-Take Admin security group
PASSWORD password—Password associated with the specified user
VALIDATE—Validates the configuration of the two servers to make sure they are compatible
FIXALL—Corrects those errors that Full-Server Failover can automatically correct
PROTECT—Initiates the connection between the source and target
FAILOVER—Initiates failover from the source to the target
LOGLEVEL number—Specifies the level of detailed logged based on the following numbers.
2—Informational messages are logged
3—Informational and error messages are logged
4—Informational, error, and exception messages are logged
5—Informational, error, exception, and debug messages are logged. This is the default setting.
6—Informational, error, exception, debug, and internal coding messages are logged
CONFIG filename—Name of the file that contains the failover options. If no file is specified, the FFMDefaults.xml file will be used.

Examples

ffmanager /source alpha /target beta /username administrator /password password /validate /fixall /protect
ffmanager /source alpha /target beta /username administrator /password password /validate /failover

Notes

If you do not specify any options with this command, the Full-Server Failover Manager user interface will open. The fields will be blank and no processing will occur.
Because the Windows product activation is dependent on hardware, you may need to reactivate your Windows registration after failover. In most cases when you are using Windows 2003, you can follow the on-screen prompts to complete the reactivation. However, when you are using Windows 2008, the reactivation depends on your licensing type. If a Windows 2008 target comes online after failover with an activation failure, use the steps appropriate for your license type.

Retail licensing—Retail licensing allows the activation of a single operating system installation.

Open the System applet in Windows Control Panel.
Under Windows activation at the bottom of the page, click Change product key.
Enter your retail license key. You may need access to the Internet or to call Microsoft to complete the activation.

MAK volume licensing—Multiple Activation Key (MAK) licensing allows the activation of multiple operating system installations using the same activation key.

View or download the Microsoft Volume Activation Deployment Guide from the Microsoft web site.
Using an administrative user account, open a command prompt and follow the instructions from the deployment guide to activate MAK clients. Multiple reboots may be necessary before you can access a command prompt. You may need access to the Internet or to call Microsoft to complete the activation.

KMS volume licensing—Key Management Service (KMS) licensing allows IT professionals to complete activations on their local network without contacting Microsoft.

View or download the Microsoft Volume Activation Deployment Guide from the Microsoft web site.
Using an administrative user account, open a command prompt and follow the instructions from the deployment guide to convert a MAK activation client to a KMS client. Multiple reboots may be necessary before you can access a command prompt.