Backing Up and Restoring an AppNode
Backing up an AppNode exports the current state of the specified AppNode to a BWAdmin command file. The command file can be provided to BWAdmin to recreate the AppNode. Output can be compressed to a ZIP file with the
-zipped option.
- Procedure
- To back up the current state of an AppNode,
- Open a terminal and navigate to BW_HOME\bin.
- Enter the
backupcommand from the command line, using-soption to identify the name of the destination file. Use the-domainand-appspaceoptions, with theappnodeargument in the command line. The AppNode can be either a local AppNode or an AppNode in a BWAgent in the agent network. By default, destination files are written to the current working directory.This example backs up AppNodeMyAppNodein a BWAgent network to a command file namedMyAppNode.cmd.BW_HOME\bin>bwadmin backup -s MyAppnode.cmd -d Machine2Domain -a AS1 appnode MyAppNode
- To restore the AppNode,
- Open a terminal and navigate to BW_HOME\bin.
- Enter the
bwadmincommand, providing the name of the backup command file. The following example recreates the AppNodeMyAppNode.BW_HOME\bin>bwadmin -f MyAppnode.cmdIf you are restoring to a different location, you need to update the command file as follows:
- The agent name points to
localhostby default. You need to change this to the name of the machine that you are restoring to. - Update the domain home to point to the absolute path to the new location.
- Update the path to the application archive (EAR) file to an absolute path.
- The agent name points to
- Use the
bwadmin show appnodescommand at the command line with the-domainand-appspaceoptions to verify the restore.
Note: Always use the available port while creating any AppNode, both from the BW_HOME scope and system scope. In case of restoration, if the designated AppNode port is not available, change the port manually.