Druva

Enterprise Workloads Editions: ❌ Business | ✅ Enterprise | ✅ Elite

This topic discusses steps to be performed on the AWS proxy to enable debug. The procedure helps in troubleshooting failures during the DR failover job

Login to AWS proxy with the default user name <code>centos</code>.

1. Go to the AWS Console &gt; EC2 Console.
2. From the IPV4 Public IP field, copy the proxy server IP.
3. From the Key pair name field, see the key pair associated with the proxy server.
4. Using an SSH client (for example, Putty), connect to the proxy server. For detailed steps to connect to an EC2 instance, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html" rel="nofollow noopener noreferrer" target="_blank">AWS documentation</a>.
5. Specify the hostname or IP.
6. Provide the key pair you had associated with the proxy server.
7. Login with default username (for centos proxy, use username centos, or for Ubuntu proxy, use username ubuntu) and press enter when prompted for a password.

Switch to sudo role. ​<code>sudo su</code>

Stop Druva services. ​<code>/etc/init.d/Phoenix stop</code>

Check if the Druva related process is not running. ​<code>ps -ef| grep -i phoenix</code>

To Manually stop the Druva services, run the following command: ​<code>Kill -9 &lt;PID&gt;</code>

Edit the Druva configuration file. ​<code>vi /etc/Phoenix/DR/Phoenix.cfg</code>

Add below parameter ( to avoid the automatic termination of failover instance). ​<code>Add DEBUG_TW = True</code>

___________________________________________________________

📝 Note ​In case of DR failover job failure, the failover instance is AWS is terminated by default.

Update the <code>DEBUGLEVEL</code> value from 0 to 9.

Start the Druva services. ​<code>/etc/init.d/Phoenix start</code>

1. Login to AWS proxy with the default user name <code>centos</code>.
 
 1. Go to the AWS Console &gt; EC2 Console.
 2. From the IPV4 Public IP field, copy the proxy server IP.
 3. From the Key pair name field, see the key pair associated with the proxy server.
 4. Using an SSH client (for example, Putty), connect to the proxy server. For detailed steps to connect to an EC2 instance, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html" rel="nofollow noopener noreferrer" target="_blank">AWS documentation</a>.
 5. Specify the hostname or IP.
 6. Provide the key pair you had associated with the proxy server.
 7. Login with default username (for centos proxy, use username centos, or for Ubuntu proxy, use username ubuntu) and press enter when prompted for a password.
2. Switch to sudo role. ​<code>sudo su</code>
3. Stop Druva services. ​<code>/etc/init.d/Phoenix stop</code>
4. Check if the Druva related process is not running. ​<code>ps -ef| grep -i phoenix</code>
5. To Manually stop the Druva services, run the following command: ​<code>Kill -9 &lt;PID&gt;</code>
6. Edit the Druva configuration file. ​<code>vi /etc/Phoenix/DR/Phoenix.cfg</code>
7. Add below parameter ( to avoid the automatic termination of failover instance). ​<code>Add DEBUG_TW = True</code>
 
 ___________________________________________________________
 📝 Note ​In case of DR failover job failure, the failover instance is AWS is terminated by default.
 ___________________________________________________________
8. Update the <code>DEBUGLEVEL</code> value from 0 to 9.
9. Save the Druva configuration file.
10. Start the Druva services. ​<code>/etc/init.d/Phoenix start</code>
11. Initiate the DR failover again.

Procedure