WildFly CLI - Taking and Restoring Configuration Snapshots: Difference between revisions
| Line 31: | Line 31: | ||
} | } | ||
</pre> | </pre> | ||
Record the name of the configuration snapshot (in this case <tt>20160331-205313510standalone.xml</tt>). This information will be needed in case we need to rollback. | |||
Revision as of 03:55, 1 April 2016
Internal
Relevance
EAP 6.4
Overview
This article describes the procedure of taking a standalone instance configuration snapshot, usually performed before a significant CLI-based reconfiguration of the application server and restoring the initial configuration in case of re-configuration failure. This mechanism relies on the fact that the application server maintains a history of its past configurations, and it is capable of taking configuration snapshots. More details about this mechanism are available here:
Take a Configuration Snapshot
Before applying a configuration change - or a set of configuration changes - that could destabilize the application server instance, take a configuration snapshot as described below.
Connect to the application server with the CLI. More details on how to connect to the application server instance are available here: Connect to a Controller.
Take a configuration snapshot as follows:
[standalone@localhost:9999 /] cd /
[standalone@localhost:9999 /] :take-snapshot
{
"outcome" => "success",
"result" => "./configuration/standalone_xml_history/snapshot/20160331-205313510standalone.xml"
}
Record the name of the configuration snapshot (in this case 20160331-205313510standalone.xml). This information will be needed in case we need to rollback.