How to move a Dollar Universe node to another server?

Products

CA Automic Dollar Universe

Issue/Introduction

Sometimes a server needs to be recreated on a higher version of the OS, keeping the same hostname.
As a result, applications need to be moved/reinstalled as well. This is a high-level explanation on how to do so for a Dollar Universe node.

Some command line experience is assumed.

Environment

Dollar Universe installed in a Unix / Linux / Windows server.

Resolution

Here is a brief description of the actions to move a node from server A to server B.

Action on old server A:

1. Stop all queues on node and wait until jobs Complete or cancel those Running.
2. Stop Dollar Universe
3. Unregister the node (unims -unregister -login XXX -pwd XXX)
4. Backup Dollar Universe data and log folders (<DUAS>/data/ and <DUAS>/log/ ), using the Unix tar command or a Window zip utility
5. Copy the tar/zip files to the server B or to a shared folder
6. Stop Server or remove it from the network so that the hostname is resolved with server B.

Action on new server B:

1. Install the node with the same company name / node name / ports and folders without registering it to the UVMS
2. Stop the node
3. Restore the previously backed up (tar/zip files) containing the data and log folders by:
  - renaming the <DUAS>/data and <DAUS/log/ folder
  - unarchiving/unzipping the compressed folder in a temporary folder
  - copying the data and log folders from the temporary in the DUAS root folder
4. Register node (unims -register -mshost xxx -msport xxx -login admin -pwd xxx)
5. Start the node

Additional Information

On Windows system, follow the same steps, taking consideration of the following changes and additional comments:

1. Compressed and archived files are in zip-format
2. Submission account must be created manually on the target host as described in the documentation:

Submission Account Details (broadcom.com)

As this might be a complicated procedure for some, we advise to assistance from a Broadcom Partner on this operation.

The Broadcom Partner list is available here:

Find a Partner or Distributor (broadcom.com)

Some other options consists on:

a) EXPORT/IMPORT via UNIEXP/UNIIMP

Install a new target Node where the objects and configuration from node A will be imported.
The UVMS utilities available since version 6.10.x uniexp and uniimp allow you to do so, you just need to do a uniexp with the argument -full to extract all objects and job events from your source node and then a uniimp with argument -full to import all objects and job events from the previously generated xml file in the new node.
Then also report the missing lines from Source Node values.xml into the Target Node values.xml (you can create a node settings package for this) and check the Submission Accounts validity.

b) EXPORT/IMPORT OBJECTS via PACKAGES

Install a new target Node where the objects and configuration from node A will be imported.
Go to the Menu Design and select the Source Node and create several packages with the objects (ie. one for tasks, one for sessions, one or multiple for uprocs, one for submission accounts,mus, rules, applications, domains, one for resources, one for business views and so on.
Then go to the deployment hub of the Target Node and deploy the packages previously created until having all the Objects on node B.
Then also report the missing lines from Source Node values.xml into the Target Node values.xml (you can create a node settings package for this) and check the Submission Accounts validity