GENERAL ERROR: A PureDisk backup is failing with an error "Data selection dirty. Fetching the PO list corresponding with the current state using DS find-I 408."

Article:TECH50590  |  Created: 2007-01-23  |  Updated: 2010-10-23  |  Article URL http://www.symantec.com/docs/TECH50590
Article Type
Technical Solution


Environment

Issue



GENERAL ERROR: A PureDisk backup is failing with an error "Data selection dirty. Fetching the PO list corresponding with the current state using DS find-I 408."


Error



Data selection dirty. Fetching the PO list corresponding with the current state using DS find-I 408.


Solution



Overview:
If the data selections for a PureDisk client contain invalid entries it will cause the backup of the client to fail.  The error message "Data selection dirty. Fetching the PO list corresponding with the current state using DS find-I 408. " will appear in the details for the backup.  The number at the end of the error message is the id number for which the expdirty flag is set.  The expdirty flag lets PureDisk know that some error occurred during the last backup job.  

Troubleshooting:
To determine why the job is failing, it is necessary to check the job details.  This can be found by logging into the PureDisk Storage Pool Authority (SPA) via the Web interface.
1. Log into the PureDisk SPA by going to http://<ip_address_of_SPA>/spa/gui in Internet Explorer
2. After logging in, go to the Data Management tab
3. Expand the World tree to display the client that has the failed backup
4. Find the failed job in the backup listing and click View Details
Note: If the entry is highlighted it can be difficult to see the View Details option.
5. In the Details tab there will be a status of each part of the backup  

The following message will appear in the Jobstep tab of the details for the job:
Data selection dirty. Fetching the PO list corresponding with the current state using DS find-I 408.

Note: The 408 at the end of the error message is the id number that should be used in any psql commands.

The psql command can be used to verify the expdirty flag has been set to 1 in the database.
The command to view the data selection is.
# /opt/pddb/bin/psql -U pddb ca -x -c "select * from dataselection where id = '408'"

ca_dataselection
-[ RECORD 28 ]-----+-----------------
id                 | 408
originaltemplateid | 8
agentid            | 250
dstypeid           | 1
groupid            | 1182
name               | All Local Files on <client>
description        |
dataselection      | <data selection>
fullvolume         | 0
volumeid           | 0
inherited          | 1
version            | 0
lastcaptureddate   |
expdirty           | 1
...

Log Files:  N/A

Resolution:
The next backup job for the dataselection will download a new polist to the client and reset the dirty flag to 0. If this does not occur it may be necessary to remove the dirty flag from the data selection. Once the flag has been reset then run the backup again.

The command to reset the flag is:
# /opt/pddb/bin/psql -U pddb ca -c "UPDATE dataselection SET expdirty = '0' WHERE id = '408'"
Note: It will be necessary to change the id = '408' in the command to match the id number that appears in the error logs.
 


Legacy ID



287126


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


Terms of use for this information are found in Legal Notices