Forum Discussion

C__Bryant's avatar
C__Bryant
Level 3
10 years ago

Unable to write pdi device

*** Moved to new discussion from : https://www-secure.symantec.com/connect/forums/partially-successful-backup-unable-write-pdi-device ***

This has nothing to do with BMR.  We have the same issue and we don't use BMR.

We have a case open right now.  We're getting it with GRT backups of our AD servers to MSDP (NBU 7.6.0.4 on Windows 2012).

  • NetBackup creates a pdi text file to have the client dump GRT info into, and then be re-read by the software.

     

    You'd see this in the bpbkar logging and might be failing the following check.

    PDI disk space check for [C:\Program Files\Veritas\NetBackup\temp\clientname_ctime\System_State failed. freespace: 0, writesize: 16384, reserved: 0

    Object::writeStreamData(): FS_WriteObj() Failure! (0xE000848F:Insufficient disk space.
    )

    raiPdiWrite(): ERR - unable to write to object

     

    If you're seeing this, there is not enough room on the install path for the NetBackup temp directory, you could mount more storage as that folder if you need more room.

     

  • Correct, it doesnt relate to bmr. Its a persistent data image (pdi) which seems to be something that was ported form Backup Exec to do Exchange, SPS and other GRT backups.

  • NetBackup creates a pdi text file to have the client dump GRT info into, and then be re-read by the software.

     

    You'd see this in the bpbkar logging and might be failing the following check.

    PDI disk space check for [C:\Program Files\Veritas\NetBackup\temp\clientname_ctime\System_State failed. freespace: 0, writesize: 16384, reserved: 0

    Object::writeStreamData(): FS_WriteObj() Failure! (0xE000848F:Insufficient disk space.
    )

    raiPdiWrite(): ERR - unable to write to object

     

    If you're seeing this, there is not enough room on the install path for the NetBackup temp directory, you could mount more storage as that folder if you need more room.