backup of shadow copy components on some Windows 2008 agents failing with Error: 2: pdrai main: unable to perform operation: no such object

Article:TECH181322  |  Created: 2012-02-13  |  Updated: 2013-02-08  |  Article URL http://www.symantec.com/docs/TECH181322
Article Type
Technical Solution


Issue



A handful of Windows 2008 R2 agents cannot be backed up. Backup of shadow copy components on Windows 2008 agents failing with Error: 2: pdrai main: unable to perform operation: no such object


Error



 *** Start: PutFiles ***
 --- Put Files SCC ---

Info: Snapshot required for resource: 'Shadow?Copy?Components'
Error: 0: handle folder enter: unable to process po list: no error
Error: 0: resource root process: unable to handle directory enter: no error

Error: 2: resource child process: snapshot required but there is nothing to snap: no such object
Error: 2: name process: unable to process 'Shadow?Copy?Components': no such object
Error: 2: pdrai main: unable to perform operation: no such object

Error: 2: pdrai main: unable to perform operation: no such object

INFO (5164): Incoming request: Get log for job step 152088.
ERROR (5164): Return error event: Get Job Log Event: No log file present for step.
DEBUG (2020): Webservice call complete, reading data.
DEBUG (2020): Webservice call done, cleaning up.
00 INFO (2020): JobStep 'FinishBackup.php' (id: 152088, jobid: 15548): Has been retrieved for processor Agent.
DEBUG (2020): Starting process. Command is: ".\32\pdengine" -c ".\php.ini" "C:\PROGRA~1\Symantec\NETBAC~1\tmp\pd_jobstep_152088.php"

wfe.log
INFO (1085315392): Job 15548: Workflow Engine: Step 152081 returns ERROR
INFO (1075325248): Job 15548: Update status of jobstep 152085 from RUNNING to ERROR

jobstep log
agentid | 23

:  Import of POList in Metabase did not complete successfully. Not setting dataselection to clean


Environment



PureDisk 6.6.1.2 SPA EEB20 and EEB36
PureDisk agent backups of windows 2008 clients.
Some successfully backing up all drives and shadow copy components, some others are failing on shadow copy components.


Cause



It is possible this is a shadow copy component issue or a data selection issue.
Suspect issue pdrai error is due to Etrack 2574978 - PutFilesSCC workflowstep fails on Windows Server 2008 backing up ASR files when agent server has EFI boot partition.


Solution



- verify no other active jobs for the agent 23
- create a test data selection to backup just shadow copy components, don't include system state as a separate item
- reboot the Window 2008 server
- reinstalled the PD agent
- made sure the anti virus software was not scanning the PD install folder.
- vssadmin listwriters show all writers as stable
- not showing DFSR on the windows agents.
- checking to see if the failing clients have PD installed in a different location from the working clients.

1. Used the PureDisk Web UI see if there are any other active jobs for the agent running.
- There were none.

2. Created a test data selection to see if it was successful. So, for agent 23, create a new data selection and backup just shadow copy components. Do not include system state as a separate item. This failed with the same error.
- backing up any other data folder is successful, so issue only happens with shadow copy components backups.

3. Suspected issue is with backing up EFI boot partition so installed EEB36-ET2574978 on SPA and reinstalled agent on agent 23.

4. Rebooted the Windows 2008 agent.

5. Check to see if there is any antivirus software running on the failing Windows 2008 clients and if yes, make sure it is not scanning the PD install folder.
- the client has Symantec Endpoint Protection (SEP). It does not appear to be scanning the PD install folder(s).

6. Check to see if the failing clients have the PD agent software is installed in a different location than the working Windows 2008 agents.
- It is not. PD SW is installed in the same location(s) on working and not working Windows 2008 clients.

7. Checked cache size setting in vssadmin

8. Kicked off backup.  Looked at the pdrai process in Task  Manager.   It was idle.

9. Created a new data selection independent of the original, new data selection ID and did not copy any of the attributes from the original.




Article URL http://www.symantec.com/docs/TECH181322


Terms of use for this information are found in Legal Notices