Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › Working with Controller Volume Streams - 3tsrv sd get

Working with Controller Volume Streams - 3tsrv sd get

These steps should be used if you have a controller failing to start due to any of the controller volumes (meta, boot, impex) being in error state due to a server going down or other issue.

The boot volume and the impex volume are not critical and can be replaced if needed however the meta volume is extremely important. If there is a situation were there is only 1 stream of the meta volume available and its marked as error, its a good idea to first make a copy of this volume stream before doing anything else. It is possible to recover a grid still even without this volume but its an extremely tedious process which can take many weeks for even a small grid.

Were are the controller volumes located and what servers are assigned which roles:

• Log into any grid node and run: $> 3tsrv sd get
• This will display were the volume streams are located, there sync status, and the which nodes are marked as primary or secondary role.

Shutting down heartbeat services:

• First we need to make sure the controller is not stuck trying to start on any of the grid nodes.
• Log into each of the primary/secondary role nodes and run: $> service heartbeat stop Note: This command can take a few minutes to complete.
• On startup of the controller this service is restarted automatically so there is no need to go back and start it later.

Marking volume streams as good:

• Log into either the primary node, or if not available one of the secondary nodes. This will be the new primary if not already.
• Output the controller volume meta data to a temporary file for editing: $> 3tsrv sd get > /tmp/metafile
• Edit this file changing the synced=0 to synced=1 for the appropriate volume(s) for the node which has the good stream.
• The controller volume streams may either be a readable name or a v-xxxx-xxx number.
• Once you have made the neccesary changes you can save and exit the editor.
• Set the modified meta file to be used: $> 3tsrv sd set file=/tmp/metafile

Start the controller:

• This must be done on the same node you updated the metafile on.
• Make this node the primary and start the controller: $> 3tsrv set role=primary --recover
• The updated metadata will automtically propagate to the other grid nodes once the controller starts