# Adding a Deduplication Database Location

You can add a deduplication database location to a MediaAgent.

Each MediaAgent is configured with a single deduplication database (DDB) location during installation. You can add additional DDB locations as needed.

When a DDB location contains zero partitions, the system automatically cleans the location. You can also manually delete a DDB location with no partitions. However, if the location is the last remaining DDB location on the MediaAgent, it cannot be deleted. This makes sure that at least one valid deduplication database location is always available on the MediaAgent.

When configuring a deduplication database location, the following constraints apply:

- The DDB location must not reside within the Commvault installation directory.

- The DDB location must not be a subdirectory of an existing deduplication database location.

- For MediaAgents running on Unix systems, the DDB location must be hosted on LVM (Logical Volume Manager) paths. Do not host DDBs on the root volume.

- For MediaAgents running on Kubernetes, the DDB location must be hosted on PVC (Persistent Volume Claim) paths.

## Before You Begin

To add a location on a Linux MediaAgent, you must use a path hosted on a logical volume. For more information, see KB Article 67762.

## Procedure

1. From the Command Center navigation pane, go to Manage > Infrastructure.

   The Infrastructure page appears.

2. Click the MediaAgents tile.

   The MediaAgents page appears.

3. In the MediaAgent column, click the MediaAgent that you want to add the deduplication database for.

   The MediaAgent page appears.

4. On the Configuration tab, in the Deduplication DB locations section, click Add.

   The Add deduplication DB location dialog box appears.

5. In the Select a Deduplication DB location, browse and select a location to host the deduplication database.

6. Click Save.

×

Loading...