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
About klish
Once the Veritas Resiliency Platform virtual appliance is deployed and configured, you are given limited, menu-based access to the operating system and the product. You need to use Command Line Interface Shell (klish) menu to manage the configuration-related changes to the product.
Below are the Klish options:
Table: Klish main menu options
Menu option | Description |
---|---|
manage | Manage the Veritas Resiliency Platform appliance |
monitor | Monitor the Veritas Resiliency Platform appliance activities |
network | Change some of the network configurations |
settings | Change the system settings |
hotfix | Manage the Veritas Resiliency Platform hotfixes |
support | Access the Veritas Resiliency Platform logs |
updates | Manage Veritas Resiliency Platform updates and patches |
utilities | Run the miscellaneous utilities of the appliances |
After the product configuration, whenever you log in to the Resiliency Platform appliance, you get the main menu of klish. This menu is the starting point, from which you can configure, manage, monitor, and support your application using the command line. You can reconfigure or modify some of the appliance settings that are configured through the product bootstrap. Following are the settings that you can reconfigure using klish:
Network settings:
You can reconfigure the subnet mask, IP, default gateway, DNS server, route, traceroute, SSH-enable-NIC, NIC for accessing product user interface and search domains using the klish menu. You cannot reconfigure the hostname that you had configured through the bootstrap process. In case of static DHCP, you cannot change the network settings using the klish menu. You cannot change the network settings for any component that is configured in the cloud environment.
System settings:
You can reset the time zone, perform operations related to NTP server, shut down the appliance, reboot using the klish menu. Changing the system settings can affect the product functionality if incorrect values are set. You can also perform logical volume management (LVM) operations such as adding a disk or removing a disk using the klish menu.
About updates:
You can apply patch updates on Resiliency Platform virtual appliance, list the patch updates and view the latest version of the Resiliency Platform. You can also configure the repository, display the current repository configuration and remove the repository.
How to use help in Klish:
You can press the tab key to display the menu options or you can run the help command to get detailed help on how to use klish. Use space key for auto-completion of command. If you get the Syntax Error: Illegal command line error or Syntax Error: The command is not completed error, press ? key to display detailed help on the required parameter.
If a klish command is expected to perform any operation on an entity such as start or stop services, it goes into lock mode and does not allow any other operation from any other session to be performed till the first operation gets completed. In such a scenario, you may encounter the following warning:
Warning: Try to get lock. Please wait...
After waiting for some time, if the operation still cannot be performed due to the lock, then you may encounter the following error:
Error: Can't get lock
In this case, you need to execute the same command after waiting for some time. The operation is performed if the lock gets released by that time.
At times, you may not be able to run the klish commands if the /var/opt
directory is fully utilized and there is no space to run the klish commands. Once this issue occurs, there is no way to recover from this situation. Hence, you need to periodically check if the space in that directory is getting fully occupied, and provision for an extra disk accordingly. See Troubleshooting: klish commands for Resiliency Manager, IMS, or Replication Gateway.