Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Resiliency Platform features and components
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Integrating with InfoScale Operations Manager
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Prerequisites for adding hosts
- Removing hosts
- Preparing host for replication
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- About Replication Gateway pair
- Managing Data Gateway
- Manage enclosure assets
- Adding a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- AWS Customization options panel
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- Managing virtual machines for remote recovery (DR) to Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Preparing Hyper-V virtual machines for using array-based replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- About custom script
- Perform DR operations for virtual machines
- Section IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
Configuring the Resiliency Manager or IMS
After Veritas Resiliency Platform (Resiliency Platform) deployment, when you log into the virtual appliance console for the first time using the admin user credentials, the bootstrap process is automatically invoked. This bootstrap process is used to set up or configure the Resiliency Platform component for the first time.
The default network protocol for virtual appliance is Dynamic Host Configuration Protocol (DHCP). If the appliance detects DHCP during the first boot or before the completion of bootstrap process, the appliance network automatically gets configured. After the network configuration, you can either use the virtual appliance console or Secure Shell (SSH) to log in as admin user and complete the bootstrap process.
If DHCP is not configured in your environment, you have an option to use a static IP for the appliance. Since the appliance network is not automatically configured in this case, you can only use the console to log into the virtual appliance.
To configure the Resiliency Manager or IMS
- Prerequisites:
See Prerequisites for configuring Resiliency Platform components.
In any non-AWS environment, log in to the virtual appliance console or SSH using the following credentials:
Username: admin
Password: P@ssw0rd
Note:
In Azure environment, the password would be the one provided during deployment.
After a successful login, you are prompted to change the password of the admin user.
See Password policies for Resiliency Platform virtual appliance.
If you are logged in to SSH, you will be logged off the SSH session after the password change and you need to again log in to complete the rest of the steps of the bootstrap process. If you are logged in to the virtual appliance console, you can continue and complete the rest of the steps of the bootstrap process.
In AWS environment, do one of the following:
From Linux system:
Use SSH with the private key from the key-pair that you had selected while launching the instance in AWS. For example:
ssh -i private_key_file admin@ip_address_of_aws_instance
Ensure to modify the permissions for the private key file as 600 before using the file.
From Windows system:
Follow the documentation of AWS to connect to the Linux instance from a Windows system using PuTTY.
- Accept the End User License agreement (EULA) to proceed with the configuration.
- In the Host Network Settings section, you can configure the appliance network by using DHCP or static IP.
- In the Appliance Settings section, do the following:
Press the Enter key to confirm the use of an NTP server for configuring the date and time.
You are required to select the time zone. Follow the instructions as displayed on the virtual appliance console or SSH session to select the correct time zone.
Enter the FQDN or IP address of the NTP server. The appliance verifies the NTP server details. If there are any issues, details are displayed on the screen and you are prompted to enter the details again.
You can reset the timezone and NTP server at a later point of time using klish menu. Changing the system settings can affect the product functionality if incorrect values are set.
- In the Product Settings section, the virtual appliance is configured as Resiliency Manager or IMS, depending upon the OVA file that you had selected for deployment.
- After a successful product configuration, a message is displayed. If you have configured Resiliency Manager on the virtual appliance, a URL for the Resiliency Platform web console login is provided. You can type the URL in a web browser and log in to the web console.
- If the bootstrap is in AWS environment, you must log in once again using the SSH key and set the admin user password. You need to use this password for subsequent logins to the console.
More Information