Storage Foundation Cluster File System High Availability 8.0.2 Configuration and Upgrade Guide - Linux
- Section I. Introduction to SFCFSHA
- Introducing Storage Foundation Cluster File System High Availability
- Section II. Configuration of SFCFSHA
- Preparing to configure
- Preparing to configure SFCFSHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring SFCFSHA
- Configuring a secure cluster node by node
- Completing the SFCFSHA configuration
- Verifying and updating licenses on the system
- Configuring SFCFSHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Performing an automated SFCFSHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Configuring CP server using response files
- Manually configuring SFCFSHA clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Configuring server-based fencing on the SFCFSHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Section III. Upgrade of SFCFSHA
- Planning to upgrade SFCFSHA
- Preparing to upgrade SFCFSHA
- Performing a full upgrade of SFCFSHA using the installer
- Performing a rolling upgrade of SFCFSHA
- Performing a phased upgrade of SFCFSHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFCFSHA upgrade using response files
- Upgrading Volume Replicator
- Upgrading VirtualStore
- Performing post-upgrade tasks
- Planning to upgrade SFCFSHA
- Section IV. Post-configuration tasks
- Section V. Configuration of disaster recovery environments
- Section VI. Adding and removing nodes
- Adding a node to SFCFSHA clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFCFSHA clusters
- Adding a node to SFCFSHA clusters
- Section VII. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuration files
- Appendix C. Configuring the secure shell or the remote shell for communications
- Appendix D. High availability agent information
- Appendix E. Sample SFCFSHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
- About configuring LLT over UDP multiport
- Appendix G. Using LLT over RDMA
- Configuring LLT over RDMA
- Configuring RDMA over an Ethernet network
- Configuring RDMA over an InfiniBand network
- Tuning system performance
- Manually configuring LLT over RDMA
- Troubleshooting LLT over RDMA
Enabling data encryption over wire
Post VVR upgrade, if you want to set up replication with encrypted data volumes, ensure that you meet the following prerequisites:
Install the user certificates on all nodes, in the
/etc/vx/vvr/
directory, to establish SSL socket communication between user space utilities (vxrsyncd
andvradmind
). Secure communication between user space utilities is created using certificate-based SSL socket.Certificate location
Description
/etc/vx/vvr/key.pem
Specifies the location of the private key. The user space utilities uses the private key in a Privacy Enhanced Mail (PEM) format.
/etc/vx/vvr/cert.pem
Specifies the location of the certificates. The user space utilities uses the certificates in PEM format.
/etc/vx/vvr/cacert.pem
Specifies the location of the root certificate. The user space utilities uses the root certificate for mutual authentication in Privacy Enhanced Mail (PEM) format.
Restart the VVR utilities using the following commands for the certificate to take effect:
/usr/sbin/vxstart_vvr stop
/usr/sbin/vxstart_vvr start
After you install the user certificates and restart the VVR utilities, perform the following steps:
Note:
Ensure that you have upgraded VVR at both the sites. Failing this, the vradmin startrep and the addsec commands may fail with -encrypted option.
Stop replication to the Secondary using the following command:
vradmin -g diskgroup -f stoprep rvgname
Dissociate the Primary and Secondary Rlinks using the following command:
vradmin -g diskgroup delsec local_rvgname sec_hostname/ip
The vradmin delsec command performs the following by default:
Dissociates the data volumes and SRL from the Secondary RVG.
Removes the Secondary RVG from its RDS, deletes the Secondary RVG, and deletes the associated Primary and Secondary RLINKs.
Add the Secondary to the RDS using the following command on the Primary:
vradmin -g diskgroup -encrypted addsec local_rvgname pri_hostname \ sec_hostname
It also creates an encrypted Rlink between primary and secondary host.
Synchronize the Secondary and start replication using automatic synchronization, using the following command:
vradmin -g diskgroup -encrypted -a startrep local_rvgname sec_hostname
For more information about enabling data encryption over the wire, see, Veritas InfoScale Replication Administrator's Guide