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
Adding an update to the YUM repository server without external access
At times, the YUM repository server in your environment may not have an external access and hence it cannot download the updates directly from SORT. In this situation, you can download the updates on any Linux server in your environment, copy those updates to YUM server, and then add the update to the YUM server.
To add an update to the YUM repository server without external access
- Download the updates from SORT on any Linux system that has access to SORT. Download the tar files for the Update bundle as well as Setup Repository bundle.
- Create directory structure on the YUM server by using the following command:
mkdir -p /var/www/html/patch/
- Copy the tar files in
/var/www/html/patch/
directory on the YUM server using the scp command:scp source_directory_structure /var/www/html/patch/
Note:
The admin and support users do not have access permission to scp files. You must switch to support user. Add the support username in the last line of /etc/ssh/sshd_config file and then restart the sshd service.
- Change permissions for the /var/www/html/patch/ directory:
chmod -R 777 /var/www/html/patch
- Assign httpd_sys_content_t permission to /var/www/html/patch/ directory so that the HTTP daemon can access its contents:
chcon -R -t httpd_sys_content_t /var/www/html/patch
- Access the following path to verify if it can be accessed for download:
http://IP_of_the_YUM_server/patch/
- Click on both the files to check if it is downloadable.
- Change directory to /var/www/html/patch directory:
cd /var/www/html/patch
- Run the following command to verify the permissions for both the files:
ls -Z
The output of the command should be similar to the following:
-rwxrwxrwx. root root unconfined_u:object_r:httpd_sys_content_t:s0 Veritas_Resiliency_Platform_RM_Upgrade_Bundle_release_version.tar.gz
-rwxrwxrwx. root root unconfined_u:object_r:httpd_sys_content_t:s0 Veritas_Resiliency_Platform_Setup_Repository_release_version.tar.gz
Check if httpd_sys_content_t permission exists for both the tar files.
- Switch to the admin user by running the following command:
su admin
- Go to Manage option to locate add-update field and then run the following command to add the update to the YUM server by supplying the location of the Upgrade bundle and setup repository bundle:
add-update http://localhost/patch/Veritas_Resiliency_Platform_RM_Upgrade_Bundle_release_version.tar.gz http://localhost/patch/Veritas_Resiliency_Platform_Setup_Repository_release_version.tar.gz