One of my customer had problem with backup of Enterprise Vault partitions. They use NetBackup to protect Enterprise Vault and they got an error 2 during backup of closed partition.
In the job status, we found the following error (status 2):
2015-03-03 11:29:33 - Info bpbrm(pid=24503) from client ev1.int.nbp.pl: TRV - BPRESOLVER has executed on server (ev-machine)
2015-03-03 11:29:33 - Info bpresolver(pid=6424) done. status: 2
2015-03-03 11:29:33 - Error bpbrm(pid=24503) no worklist items returned from bpresolver on client ev1.domein.local
2015-03-03 11:29:33 - Info bpresolver(pid=6424) done. status: 2: none of the requested files were backed up
Status 2
none of the requested files were backed up(2)
I have found the following errors in the bpresolver.log (on EV server):
11:28:44.582 [5476.7816] <2> DebugLog(): INF - CEVInterface::RequestXML - Error : Access is denied.!!, Error Code = 5
11:28:44.582 [5476.7816] <2> DebugLog(): INF - CEVInterface::RequestXML - Unable to delete File (C:\Program Files (x86)\Enterprise Vault\Reports\EVBackup.xml)
11:28:44.598 [5476.7816] <2> DebugLog(): INF - CEVInterface::RequestXML - EV Admin Services notification sent to generate XML.
The EVBackup.xml file is used by NetBackup to get list of EV resources (Index, Vault Stores etc). Each time the NetBackup scheduler executes an Enterprise Vault backup schedule, bpresolver on the Policy Client will request an Enterprise Vault objects for backup list from the Enterprise Vault Admin Service. The Enterprise Vault Admin Service will execute a Stored Procedure, uspx_BackupLocationsEx on the SQL server that will query the Enterprise Vault Directory database to get the objects for backup and return the result set in xml format. Subsequently, an xml file EVBackup.xml will be created in Program Files\Enterprise Vault\Reports. Because my customer closed two partitions and the EVbackup.xml was not updated (access denied, permissions problem), NBU did not find any information about closed partition (in the file there were only open and ready partitions).
To solve the problem we just corrected the EVbackup.xml file permissions.
NOTE: Always you can edit the EVbackup.xml file manually or run the following command to generate a new file with updated informations:
sc control EnterpriseVaultAdminservice 136