cancel
Showing results for 
Search instead for 
Did you mean: 

premature end of file status ( 233 )

gary_williams_2
Not applicable
Has anyone ever encountered this error. It is happening on a client backup, but not every day and the policy names are legal i.e no commas etc
1 REPLY 1

patrickkuah
Level 6
Ok, try this.
http://seer.support.veritas.com/docs/268664.htm

In this scenario, the /usr/openv/netbackup/db/config/sync file had become corrupt.
To fix it, it is necessary to rebuild it, following these steps:
1. Move the /usr/openv/netbackup/db/config/sync file to /usr/openv/netbackup/db/config/sync.old
2. Using the GUI, redefine all DB catalog backup attributes, including any additions/revisions. Click OK to save and a new sync file will be created.
3. Verify that a new sync file was created
4. Run a DB catalog backup to verify the catalog backup is now working correctly
5. Remove the /usr/openv/netbackup/db/config/sync.old file when you have confirmed that the DB catalog backups are working correctly

cheers!!!
patrickkuah