I didn't test it, but I would assume it applies to current versions as well. Otherwise it would state which version has fix included (at least I would expect it that way).

When you configure Avamar to take a system state backup of a windows machine, what happens is that the Avamar client calls on the ntbackup.exe program to take the system state backup of the client. The System state is saved, assuming a default installation, into C:\Program Files\Avs\var.

This error message that you've posted could imply that for some reason ntbackup.exe has not been able to successfully create the system state backup file. I would most definitely test this by calling ntbackup.exe on it's own to determine that the issue does not lie here. Otherwise, I don't believe that the size of the .bf file is still an issue as it was with v3.x of the product.

Check to see if Windows is experiencing problems in actually creating the SystemState.bkf file. Try to create the system state manually, through Windows without using Avamar.

To do this, check the Avamar client log file for the command that is run to create the system state file (search the log for ntbackup.exe). Using a Windows command prompt, try to run the ntbackup command with the parameters in the log file and check to see if the .bkf file gets created.

To verify whether the file is being created, check the Windows Application Log for any messages:

1. Start > Run > Type "eventvwr".
2. Select Application Log.
3. You may need to View > Filter.
4. Select the Event source 'ntbackup' and press apply > OK.
5. Make a note of any messages you find that are related to the System State. Include them in the case notes.

If the SystemState.bkf file *does* get created, make a note of its size. If it does not get created you must fix this before the Avamar client system state backup will be able to complete successfully.