Manually removing deprecated resource types and modifying attributes


Manually removing deprecated resource types and modifying attributes
Prev	Appendix D. Changes to bundled agents in VCS 6.0.1	Next

With VCS 6.0, certain resource type definitions are no longer used. Before you start the upgrade process, you must remove the resources of the deprecated resource types from your cluster configuration.

If you use the resource type ServiceGroupHB, Symantec recommends the use of I/O fencing.

VCS 5.1 does not support gabdiskhb. So, the installvcs program removes the gabdiskhb entry from the /etc/gabtab file.

Note:

Make sure you start VCS on the local node before starting on the other nodes. This standard ensures that HAD reads the configuration from the local node and updates it on the remaining nodes.

To remove the deprecated resource types and modify attributes

Save the VCS configuration and stop the VCS engine.
```
# haconf -dump -makero
# hastop -all -force
```
Back up the configuration file, main.cf to a location on the cluster node.
Edit the main.cf located under /etc/VRTSvcs/conf/config.
Perform the following instructions:
- Remove the resource of the deprecated resource types.
  
  You must modify the resource dependencies to ensure that the configuration works properly.
- Modify attribute values that might have changed.
  
  See Table: Changes to attributes from VCS 5.0 or later to VCS 5.0 MP3.
  
  See Table: Changes to attributes from VCS 4.0 to VCS 5.0.
- Save the main.cf.
- Reformat the main.cf file.
```
# hacf -cftocmd config
# hacf -cmdtocf config
```

Verify the configuration.

# cd /etc/VRTSvcs/conf/config
# hacf -verify config

Start VCS on the local node.
Start VCS on other nodes.

Prev	Up	Next
New and modified attributes for VCS 6.0.1 agents	Home	Creating new VCS accounts if you used native operating system accounts