---
title: "Switching into DR"
canonical: "https://kb.myframeworks.com.au/space/PROSTIXV48DOC/31100692/Switching%20into%20DR"
format: markdown
---
Depending on the time required to recover from a failure on/at the Production Server, a decision must be made to switch your operation over to the DR server. This decision must be made by your IT department, with consultation from either Sterland, your hardware tech support, or both.  Save the Active AI file   The AI files are switched automatically by root's cron at the defined [SyncInterval]. If your system crashes, you need to determine the appropriate steps to follow next, depending on the type of crash, and the status of the AI process at the time of the crash. If it's a hardware or operating system crash, and the files on disk on the Production server are inaccessible, then obviously you cannot perform this step. If the active AI file is still accessible, then the following steps outline the process to recover it and  apply it manually to the DR Live DB before you switch over to it. Determine the current AI file   Change to the Production Database directory, for example: cd [LiveDbPath] Run the Progress 'rfutil' command to find the 'busy' AI file: rfutil stix -C aimage extent list | more   This returns several screens with info; you're looking for the extent flagged with status 'busy', as follows:   Extent: 1 Status:Busy Type: Variable Length Path:/prostix/data/live/stix.a1 Size: 120 Used: 1 Start: Thu Jul 28 16:57:45 2005 Seqno: 1   Note:  The name of the AI file in the 'Path' field. In this example, it is stix.a1  Copy AI file from Production to DR Server Next, copy this AI extent to a temporary directory on the DR Server, for example: [RemoteMethod] [LiveDbPath]/stix.a1[DrServerName]:/tmp Apply AI file to DR Warm Spare DB   Log into the DR server and change to the DR Live DB directory, for example: cd [DrDbPath] Apply the AI file just copied using the Progress 'rfutil' command, for example:  rfutil stix -C roll forward -a /tmp/stix.a1 -B 5000 -TB 24 -TM 32  Start the DR Live Database Start the DR Live DB, Promenu option 18, option 1. This runs the customised version of /prostix/bat/rc.live on the DR Server, which loads in the Production copy of the Progress license file, gives a suitable warning that starting the DR Live DB disables its AI sync ability from the Production Database, and then starts the Database only if you type  'yes'  to the warning.  Log into ProStix DR As per your defined [AccessMethod], instruct your users to log back in. When the users log into the DR Server, they simply select Promenu option 1, as they normally do on the Production server, to log into a Prostix DR session.