This article applies to:
- OS: NA
- Product edition: DRaaS v2.1
This article provides the steps to be performed over the Source VM, AWS proxy and failover instance to troubleshoot and get to the cause of the issue.
Checklist for the source VM
- Provide the output of the execution of the following command from the source virtual machine.
(Importantly ask the antivirus installed on the server)
wmic product >C:\test
- System events and application events
- Free space on the system disk
- Virtual memory configuration, including size and location of the pagefile.sys file
- Check if Windows update is ongoing
- Partition Type of OS disk (NTFS or something else)
- Check if server is Domain Controller-
- VMchecker script Output (Only to get more information for Source VM): How to run the AWS VMImportChecker script to find the reason for VM import failure
Steps to perform on the source VM (When antivirus is installed)
- If antivirus installed then ask the customer to whitelist the following program/process:
- Run the VM backup.
- Update the DR Copy.
- Perform the DR failover (with DEBUG_TW = True in the AWS proxy)
Steps to perform on AWS proxy
- Login to AWS proxy.
- Switch to sudo role.
- Stop Phoenix services.
- Stop all the Phoenix-related process.
ps -ef| grep -i phoenix
- Edit the Phoenix configuration file.
- Add below parameter ( to avoid the automatic termination of failover instance).
Note: In case of DR failover job failure, the failover instance is AWS is terminated by default.
Add DEBUG_TW = True
- Save the Phoenix configuration file.
- Start the Phoenix services.
- Initiate the DR failover again.
Steps to perform on the failover instance
Prerequisite: Failover instance must be in power on state.
- To get the system logs from the failover instance, select the instance >Action > Instance Settings > Get System Log.
- To get the instance screenshot from the failover instance, select the instance > Action > Instance Settings > Get Instance Screenshot.
- If the failover instance is not passing through 2/2 checks successfully:
- Detach the volume from the failover instance.
- Mount the system disk from the target to some EC2 test instance running in the same AZ.
- Collect the application and system logs from the attached volume.
- Collect the Druva folder from the attached volume.
- Download Phase-1 and Phase-2 logs from S3 as specified below. (Bucket details can be fetched from the Phoenix Management Console)
- Phase-1: When EC2 instance is launched using the RM AMI, EBS snapshot and failover settings.
- Phase-2: When EC2 instance is booted from the DR copy root volume rather than RM root volume.
Ex: [2019-03-22 18:51:42,789] [INFO] S3client<is_bucket_exists> exist :phoenix-1765-153859650232 Where “phoenix-1765-153859650232” is the s3 bucket.
- Collect the DR failover job. Refer the Logs section.