Windows client and system state

Question

Hello.

We've installed the Windows client on several servers and the backup of the System State appears to be taking a lot of disk space, and appears to be growing over time. The systemstate.bkf file Avamar created on one server was 1.5GB. A manual backup of the system state using NTBackup took only 500 MB.

There's a (non-EMC) web site that mentions using the systemstatefile attribute to change the location.

http://www.mygeekfinds.com/2009/04/how-to-backup-an-active-directory-domain-controller-with-avamar/

Is that advised?

Does that work with version 5?

Is there a way to install the client to another drive\location?

Anybody tried the x15=16 option or have any additonal information about it?

luishdez1 · Accepted Answer

Anybody tried the x15=16 option or have any additonal information about it? I have used this option and had great success with it.  We keep logs on some of our webservers for quite awhile, so the system state can get large sometimes.  Using this option works as advertised and shrinks the system state to a manageable size. https://solutions.emc.com/emcsolutionview.asp?id=esg99020

Heffe1 · Answer

Thanks for your response.  For the good of the community, I will say that we had an EMC consultant verify the option is still valid with version 5.  We enabled it globally by going into our dataset and adding the attribute there instead.  The System State backup is now taking much less space.

dstarm · Answer

When you said you did this globally by modifying the dataset, are you refering to the Avamar dataset as an advanced attribute?

Heffe1 · Answer

Correct.

fl1 · Answer

Heffe,

In the dataset under advance options do you use --x15=16 or just x15=16? When I add the parameter (I tried both ways) and noticed that they show up in red so I don't know which is the correct syntax to use.

Avamar

Windows client and system state

Was this post helpful?