Start a Conversation

Unsolved

This post is more than 5 years old

1091

December 8th, 2010 21:00

Help with "cacheprefix"

Hello,

I have an Avamar client with a few dense filesystems. The backup for this client is intruding on the blackout/maintenance window and is automatically cancelled by Avamar. I want to be able to split the dataset out into smaller chunks.

I have read up on this and am led to believe that "cacheprefix" will help to achieve this.

I have read the Operational Best Practices Guide but it doesn't make sense.

It says:

* Break the client file system into multiple smaller datasets.

* For each dataset, ensure that the maximum file and hash caches assign a unique cacheprefix attribute.

How can I break a client filesystem into smaller datasets? For the life of me, I cannot find out how to do this! I can only see how to assign a single dataset to a client and not more than one.

Does anyone have an example of how to implement this?

Thanks

Justin

307 Posts

December 22nd, 2010 09:00

Hello Justin,

You can have seperate datasets for each of the local drives by selecting the drive under the Source data of the dataset and then, under Options -> More,

enter attribute as cacheprefix=cache_name (for ex, driveC) and specify filecachemax and hashcachemax attributes as well

131 Posts

December 27th, 2010 09:00

Hi,

Break in small dataset, ex:

FS_D_1

FS_D_2

FS_D_3

Create the same number of the groups

GR_1

GR_2

GR_3

Associate an each dataset to a Group.

The cacheprefix must be create for each group.

cacheprefix     FS_D_1

cacheprefix     FS_D_2

cacheprefix     FS_D_3

With this to start the first backup set of Hash (1) be active.
Upon finishing this set will come out of memory
When starting the second group, the set of hash (2) is active.

and so on.

With this you will avoid memory overflow.

regards,

Hormigo

Listen
Read phonetically

Dictionary - View detailed dictionary

  1. pronoun
    1. them
    2. ye
  2. article
    1. the
No Events found!

Top