Reply to Message

Reply to Message

View discussion in a popup

Replying to:

Re: Ask the Expert: Avamar Server, Capacity and Replication

Hello Pascal,

In most cases, it is not the metadata container which occupies most space but the data container.

Within the GSAN, there are two primary types of containers for storing data: metadata containers and data containers.

◆ Metadata containers store the metadata for backups.

◆ Data containers store the actual backup data.

Both types of containers are created as required, based on the data that is being backed up.

Metadata can only be written to metadata containers. In addition, after the Avamar server creates containers, you cannot remove them. To illustrate how this process affects metadata capacity, consider the following scenario:

A customer uses an Avamar server as the target for backups. The customer is close to reaching full capacity on the Avamar server, and thus purchases a Data Domain system to provide additional capacity for backups. The customer then decides to transition existing backup workloads to the Data Domain system. Doing so results in a decrease in the amount of GSAN capacity used on the Avamar server. The customer then begins adding new backup workloads that require significant metadata capacity to the Data Domain system. The space freed in the data containers cannot store new metadata for the additional backup workloads. New metadata containers must be created for new workloads that require substantial metadata storage (for example, file system backups with lots of files).

The Avamar server must have sufficient disk space available to create new metadata containers. If the server has already allocated data containers, the disk space might be insufficient for creating new metadata containers.

For more information, please reference the following document:

https://support.emc.com/docu49793_Avamar-Metadata-Server-Capacity-Technical-Note.pdf?language=en_US

0 Kudos