Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux requirements
- Linux requirements
- Network and firewall requirements
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installing the operating system on each node of the cluster
- Installing Veritas Access on the target cluster nodes
- About NIC bonding and NIC exclusion
- About VLAN Tagging
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading Veritas Access and operating system
- Upgrading Veritas Access using a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Troubleshooting the LTR upgrade
- Appendix C. Configuring the secure shell for communications
Before you uninstall Veritas Access
Perform the following steps before uninstalling Veritas Access:
Before you remove Veritas Access from any node (but not in all the nodes) in a cluster, make sure the node has already been deleted from the running cluster. You can use the Cluster> show command to view the cluster node state, and use the Cluster> delete command to delete a running node from the Veritas Access cluster.
See the relevant man pages for more information on the Cluster> show and Cluster> delete commands.
Stop all the applications that access the file system over NFS, CIFS, or FTP.
Destroy all the replication jobs from the cluster.
Use the Replication> job show command to list all the replication jobs on the cluster.
Replication> job show Job Name Role Job Type Encryption Debug Schedule ======== ====== ======== ========== ===== ======== job1 SOURCE DATA OFF ON sch1 State CKPT Count Exclunit Source repunit Target repunit(s) ======== ========== ======== ============== ================= ENABLED 1 -- scr1 trg1 Link name(s) ============ link1
Use the Replication> job destroy command to destroy the replication jobs.
Replication> job destroy job1 ACCESS replication SUCCESS V-288-0 Removing bandwidth limit on the link: link1 ACCESS replication SUCCESS V-288-0 Job 'job1' disabled successfully. ACCESS replication SUCCESS V-288-0 Job 'job1' deleted successfully.
Stop the NFS, CIFS, FTP, GUI, and the replication service on the cluster using the appropriate CLISH command.
CLISH> cifs server stop Stopping CIFS Server.....Success. CLISH> CLISH> nfs server stop Success. CLISH> CLISH> ftp server stop Success. CLISH> CLISH.Support> gui server stop GUI service is OFFLINE. CLISH> CLISH> replication service stop ACCESS replication SUCCESS V-288-0 Replication service stopped CLISH>
Run the following command to stop AMF:
# /etc/init.d/amf stop Stopping AMF... AMF: Module unloaded
Run the following command and wait for a couple of minutes:
# /opt/VRTS/bin/hastop -all
Run the following command and verify that you only see Port a and Port b:
# gabconfig -a GAB Port Memberships ================================== Port a gen 7f2d0a membership 01 Port b gen 7f2d09 membership 01