Run a backup now

Backup Now takes a backup of the node straight away instead of waiting for the next scheduled run. Use it before a risky change, such as an upgrade or a large deletion. The newest recovery point then holds the node as it is now.

Before you begin

Backup Now works on a running node whose first backup has finished.

(Optional) Check the agent connection

A backup needs E2E’s backup server to reach the backup agent on the node. To check the connection first:

1. In Manage CDP Backups, click the node, and open its CDP Backup Details tab.
2. Click Check Agent Connection, then Check Connection.

“Successfully connected to Agent.” means the backup server reaches the agent. “Connecting to agent failed.” means the backup server cannot reach the agent on the node; see Troubleshooting CDP Backup.

When port 1167 is blocked, the check gets no answer and ends with an error instead of either message; see Allow port 1167 in the security group.

Take the backup

1. On the node’s CDP Backup Details tab, click Backup Now.
2. Click Run.

When the backup server is busy, the run can start a while after you click Run. While it runs, disk use on the node rises.

If a backup is already running or queued for the node, you see “Backup already in progress, Please check the Task History tab for details.”, and no second one starts. If the agent is busy, you see “Backup Now failed - the backup agent is currently busy.” Try again once the current backup finishes.

Check that the backup finished

Open the node’s Backup Task History tab. The run is listed with its start time, end time, and duration. Its Task Status reads Finished once it completes, or Backup Provisioning Failed if it ended in an error. Once it reads Finished, a new recovery point appears on the Backup Recovery Points tab.

The node now has a recovery point from this moment, alongside its scheduled ones. To keep it from being merged away later, see Lock a recovery point. If the backup fails, see Troubleshooting CDP Backup.