> This page location: /docs.md > /docs/management.md > /docs/ops-manager/current.md > /docs/ops-manager/current/administration.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Move Jobs from a Lost Backup Daemon to another Backup Daemon

If the server running a [Backup Daemon](https://www.mongodb.com/docs/ops-manager/current/core/system-overview.md#std-label-backup-daemon) fails, and if you [run multiple Backup Daemons](https://www.mongodb.com/docs/ops-manager/current/tutorial/configure-backup-high-availability.md), then an administrator with the [`Global Owner`](https://www.mongodb.com/docs/ops-manager/current/reference/user-roles.md#mongodb-authrole-Global-Owner) or [global backup admin role](https://www.mongodb.com/docs/ops-manager/current/reference/user-roles.md#std-label-global-backup-admin-role) [role](https://www.mongodb.com/docs/ops-manager/current/reference/user-roles.md) can move all the daemon's jobs to another Backup Daemon. The new daemon takes over the responsibility to back up the associated [shards](https://www.mongodb.com/docs/manual/sharding.md#std-label-sharding-background) and [replica sets.](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-replica-set)

When you move jobs, the destination daemon reconstructs the data using a snapshot and the [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) from the [Snapshot Storage](https://www.mongodb.com/docs/ops-manager/current/core/system-overview.md#std-label-backup-database). Reconstruction of data takes time, depending on the size of the databases on the source.

During the time it takes to reconstruct the data and reassign the backups to the new Backup Daemon:

- Ops Manager does not take new snapshots of the jobs that are moving until the move is complete. Jobs that are not moving are not affected.

- Ops Manager *does* save incoming oplog data. Once the jobs are on the new Backup Daemon's server, Ops Manager takes the missed snapshots at the regular snapshot intervals.

- Restores of previous snapshots are still available.

- Ops Manager can produce restore artifacts using existing snapshots with [point-in-time restore](https://www.mongodb.com/docs/ops-manager/current/reference/glossary.md#std-term-point-in-time-restore) for [replica sets](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-replica-set) or [sharded clusters.](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-sharded-cluster)

## Procedure

With administrative privileges, you can move jobs between Backup daemons using the following procedure:

1. Click the Admin link at the top of Ops Manager.

2. Select Backup and then select Daemons.

   The [Daemons page](https://www.mongodb.com/docs/ops-manager/current/admin/backup/daemons-page.md#std-label-daemons-interface) lists all active Backup Daemons.

3. Locate the failed Backup Daemon and click the Move all heads link.

   Ops Manager displays a drop-down list from which to choose the destination daemon. The list displays only those daemons with more free space than there is used space on the source daemon.

4. Move the jobs to the new daemon.

   Select the destination daemon and click the Move all heads button.
