Network Configuration Rollback and Version Control

A backup stores your configuration so you can recover it if something goes wrong. Version control manages the full lifecycle of configuration changes: every change is captured as a versioned snapshot with attribution, diff, and timestamp. Rollback is the action of restoring a specific version in a controlled way, with diff preview and approval workflows. In ConnectMyAssets, backup provides the raw storage; version control adds the management layer: compare any two versions, understand what changed and why, require approvals for sensitive devices, and execute rollbacks with full audit logging. Backup is storage; version control is governance.

For most devices, the rollback completes within seconds to a few minutes depending on the device polling interval. The pre-rollback diff calculation is instantaneous. If an approval workflow is required, the execution waits for approval, but the approval notification is sent immediately so the approver can act right away. Once approved, the target configuration is staged on the ConnectMyAssets appliance and the device fetches and applies it on its next polling cycle. ConnectMyAssets confirms the rollback success by verifying the running config matches the restored version.

ConnectMyAssets supports triggered rollback via its API and webhook integrations. You can configure your monitoring platform to call the ConnectMyAssets API when a critical metric crosses a threshold immediately after a detected configuration change. The API can initiate a rollback to the previous version automatically, subject to any approval rules you have configured. Fully automated no-approval rollback is available for pre-approved device and version combinations in controlled environments. For production devices, most organizations prefer a human confirmation step even for automated triggers.

For clustered or high-availability device pairs, ConnectMyAssets manages each member as an individual device in the inventory. When you need to roll back a cluster, you can either roll back members individually in sequence, or use a coordinated rollback job that targets all members of the cluster and stages configurations in the correct order for each device to fetch. The platform is aware of HA relationships and can enforce ordering to avoid split-brain or failover triggers during the rollback. All members are tracked in the version history independently, so you have full visibility into the config state of each node.

Yes, always. A rollback in ConnectMyAssets is implemented as a new configuration push, not as a rewrite of history. When you roll back device A to version V3, the system creates a new version V5 (or whatever the next version number is) whose content is identical to V3, but whose metadata records it as a rollback, identifying the source version, the requester, the approver, and the timestamp of the rollback. The original V3 is never modified, and V4 is never deleted. The full history remains intact and auditable. This approach means your audit trail always moves forward and can never be altered retroactively.

ConnectMyAssets integrates with ServiceNow, Jira Service Management, and other ITSM platforms via bidirectional API. When a rollback is initiated, it can automatically reference an open incident or change ticket. When the rollback completes successfully, it can update the ticket status, add the diff as a comment, and attach the audit log entry. Conversely, a rollback can be triggered directly from an approved change record in your ITSM, with ConnectMyAssets receiving the instruction via API and executing against the specified device and target version. This closes the loop between your change management process and the actual network configuration state.