zkrusz
1 Copper

Avamar Virtual Edition + DD

Jump to solution

Looking for some guidelines for AVE sizing

Scenario:

We are testing an Avamar M600 grid with several AVE's at various test locations. We have have some Avamar only AVE's and some DD AVE's. The question is in sizing the AVE when paired with DD.  Should we size to the .5TB AVE? How much room does that leave for metadata growth? Its 3x250GB so assumption is its using 33% of the allocated storage for database metadata. Or is the answer that the AVE will simply consume all available space where its client data or database data?

Thanks in advance.

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
ionthegeek
4 Beryllium

Re: Avamar Virtual Edition + DD

Jump to solution

Capacity that is not used for customer backups is reserved for the system's internal use.


This capacity is mainly consumed by the operating system files and checkpoint overhead. Avamar uses checkpoints to provide protection through time -- if there is a data integrity issue, having a validated checkpoint allows you to roll the system back to a known good point in time. Checkpoints are made up of read-only copies of the files that are used to store the data. The software uses a copy-on-first-write strategy to keep the size of the checkpoints down but whenever the data files need to be modified, some space will be consumed. This space will be reclaimed the next time a checkpoint validation completes successfully. The amount of free space available on the AVE's data partitions must be sufficient to accommodate the peak checkpoint overhead with a comfortable margin of safety.

View solution in original post

4 Replies
Highlighted
Nayaks1
2 Iron

Re: Avamar Virtual Edition + DD

Jump to solution

You must go through your EMC account team and discuss with presales about the sizing. In the calculation above if you have concluded that avamar stores the DD-metadata in the 33% space then, no, the 33% ......infact 36% is used for the avamar well being....your metadata is still stored in the 64% of the space,  so you are better of saying " AVE will simply consume all available space where its client data or database data"

zkrusz
1 Copper

Re: Avamar Virtual Edition + DD

Jump to solution

Ok that creates another question, If 36% of space allocated to its well being is quite alot of space especially if its the 4TB AVE. What happens when its being well(what is the 36% used for), if not for client meta data?

0 Kudos
ionthegeek
4 Beryllium

Re: Avamar Virtual Edition + DD

Jump to solution

Capacity that is not used for customer backups is reserved for the system's internal use.


This capacity is mainly consumed by the operating system files and checkpoint overhead. Avamar uses checkpoints to provide protection through time -- if there is a data integrity issue, having a validated checkpoint allows you to roll the system back to a known good point in time. Checkpoints are made up of read-only copies of the files that are used to store the data. The software uses a copy-on-first-write strategy to keep the size of the checkpoints down but whenever the data files need to be modified, some space will be consumed. This space will be reclaimed the next time a checkpoint validation completes successfully. The amount of free space available on the AVE's data partitions must be sufficient to accommodate the peak checkpoint overhead with a comfortable margin of safety.

View solution in original post

zkrusz
1 Copper

Re: Avamar Virtual Edition + DD

Jump to solution

Thanks for the responses.