ERR - Error encountered while attempting to get additional files for System State

Removable Storage Manager should be disabled to prevent this error.

See http://www.symantec.com/business/support/index?page=content&id=TECH178896

I should not have included the removable storage manager error in this.  The issue is with the system state files not being backed up and generating the error.  This is happening on this server as well as another.  This server has Removable Storage Manager disabled. The other doesnt evern have that service. 

The issue is ERR - Error encountered while attempting to get additional files for System State:\

OK, see the technote mentioned in this thread

https://www-secure.symantec.com/connect/forums/err-error-encountered-while-attempting-get-additional-files-system-state-1

Ok I'll try that.  This client had open file backups enabled but was using VSP.  I dont understand why but some windows clients are using vsp and some are using vss.  This is and one other are the only ones that failed. 

quote:  "Check the Windows Open File Backup setting on the master server to ensure VSS is being used
Host Properties > Master Servers > (master) > Client Attributes > Windows Open File Backups tab
Ensure the client name is added to this list, then highlight client in the list, and select 'Use Microsoft Volume Shadow Service (VSS)'"

I thought this was solved but now I have a client with the same error but they have VSS enabled correctly. I am not sure which log to look at but since the below indicates error from bpbrm I created that log directory and am rerunning the backup.  The backup is a diff.  The errors we are seeing are intermittant and inconsistant with clients.  Hard to figure out.

Error from job display in java console

09/11/2013 17:08:57 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\System Files\System Files (WIN32 -536805679: Unknown error)
09/11/2013 17:08:57 - Error bpbrm (pid=7081) from client ifwlwss1: ERR - Error encountered while attempting to get additional files for System State:\
09/11/2013 17:08:57 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\Automated System Recovery\BCD\BCD (WIN32 -536805679: Unknown error)
09/11/2013 17:08:57 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\Internet Information Services\IISCONFIG (WIN32 -536805679: Unknown error)
09/11/2013 17:08:57 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\Internet Information Services\IISMETABASE (WIN32 -536805679: Unknown error)
09/11/2013 17:08:58 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536805679: Unknown error)
09/11/2013 17:08:58 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\Registry\Registry (WIN32 -536805679: Unknown error)
09/11/2013 17:08:58 - Warning bpbrm (pid=7081) from client ifwlwss1: WRN - can't open object: System State:\Windows Management Instrumentation\WMI (WIN32 -536805679: Unknown error)

If you set these 2 windows 2003 clients to use "VSS" via the master server "Client Attributes", there is no reason why it still use VSP except:

- you haven't run a "bprdreq -rereadconfig" to refresh the setting on master server. OR
- "Volume Shadow Copy" service was disabled in the client. OR
- "Volume Shadow Copy" service is enabled, but not able to start properly due to OS issues, if this is the case, you need to check system & application event logs for more details, or contact Microsoft support.

what is the backup selection in your policy setting?

If it's set to "System_State", try not to use that and change it to "Shadow Copy Components" directive. If you have been using ALL_LOCAL_DRIVES (which include the above), try to split it into and see how it goes:

C:\
NEW_STREAM
Shadow Copy Components:\ 
 

More details in http://www.symantec.com/docs/TECH35151

Agree with watsons - the key may be in what you have in your selection lists

ALL_LOCAL_DRIVES is fine (as long as you do not have anything else also in the selection list) but if you have System State change it to Shadow Copy Components as System State is for Windows 2000 / XP only.

Also worth asking what the server actually does as sometimes being an application server (AD, Exchange etc.) can also have an affect on things - as can be virtualised when the VMware tools can affect the VSS processing.

You said earlier that the clients were set to use VSP - but that does not actually exist in 7.5.x - are your clients definately on 7.5.0.3?

That's worth a try.  But I never read it that way. 7.5 Admin Guide quote (emphasis added)

System State:\ directive

The System State:\ can be used on Windows 2003 systems and later.

 

The System State:\ directive is needed for the operating system versions which

do not support Shadow Copy Components, such as Windows XP.

 

Windows 2003 Server computers recognize the System State:\ directive and

behave as if following the Shadow Copy Components:\ directive. A message

informs the user that this directive translation occurred.

 

The System State:\ directive creates a backup for critical system-related

components. The exact set of system components that are backed up depends on

the operating system version and system configuration.

Thanks for all the feedback! 

Watsons:  The backup selection in your policy setting is ALL_LOCAL_DRIVES with the  understandign that this will catch the shadow copy components and system state.

Mark_Solutions:  The server being backed up.. at least one of them.. is an IIS server. The other is a sharepoint server but is not in production yet.. just being built.  The issue is not every night and not always the same server.

Mark_Solutions:  When I go into master server properties and click on client attributes then Windows Open File Backup tab it shows the Snapshot Provider.  I did read in the admin guide that windows clients default to VSS for 7.5 but was wondering why the console has this as configurable.  Anyway I looked at windows clients and noticed some are configured to use VSP in this gui.*  This may be a different issue because the servers with the system state error show up as using VSS.

My clients are on 7.5.0.3

*In the example screen shot aodoratest is a windows server