cancel
Showing results for 
Search instead for 
Did you mean: 

unable to write to pdi device

AlChie
Level 4

*** moved to new post from
https://vox.veritas.com/t5/NetBackup/Unable-to-write-pdi-device/m-p/741639
***
Greetings!
And what if it happens on Win 2012 client:
Moreover it looks very frustrating:
06/21/2017 00:00:00 - Info nbjm (pid=22242) starting backup job (jobid=2645732) for client CAB-VOP-DC00008.omega.sbrf.ru, policy DC_AD_OMEGA_2_Daily, schedule Full_Daily
06/21/2017 00:00:00 - Info nbjm (pid=22242) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2645732, request id:{6C54BC70-55FB-11E7-98FA-0010E02070F6})
06/21/2017 00:00:00 - requesting resource Backup2m3_DD990-Q6_DFC
06/21/2017 00:00:00 - requesting resource netback.cgs.sbrf.ru.NBU_CLIENT.MAXJOBS.CAB-VOP-DC00008.omega.sbrf.ru
06/21/2017 00:00:00 - requesting resource netback.cgs.sbrf.ru.NBU_POLICY.MAXJOBS.DC_AD_OMEGA_2_Daily
06/21/2017 00:00:01 - granted resource  netback.cgs.sbrf.ru.NBU_CLIENT.MAXJOBS.CAB-VOP-DC00008.omega.sbrf.ru
06/21/2017 00:00:01 - granted resource  netback.cgs.sbrf.ru.NBU_POLICY.MAXJOBS.DC_AD_OMEGA_2_Daily
06/21/2017 00:00:01 - granted resource  MediaID=@aaadj;DiskVolume=ddboost-stu-nbu-510;DiskPool=DD990-Q6;Path=ddboost-stu-nbu-510;StorageServer=DFC-DD990-Q6;MediaServer=backup2m3.ca.sbrf.ru
06/21/2017 00:00:01 - granted resource  Backup2m3_DD990-Q6_DFC
06/21/2017 00:00:03 - estimated 49027526 kbytes needed
06/21/2017 00:00:03 - Info nbjm (pid=22242) started backup (backupid=CAB-VOP-DC00008.omega.sbrf.ru_1497992403) job for client CAB-VOP-DC00008.omega.sbrf.ru, policy DC_AD_OMEGA_2_Daily, schedule Full_Daily on storage unit Backup2m3_DD990-Q6_DFC
06/21/2017 00:00:14 - started process bpbrm (pid=9736)
06/21/2017 00:00:19 - Info bpbrm (pid=9736) CAB-VOP-DC00008.omega.sbrf.ru is the host to backup data from
06/21/2017 00:00:19 - Info bpbrm (pid=9736) reading file list for client
06/21/2017 00:00:20 - connecting
06/21/2017 00:00:24 - Info bpbrm (pid=9736) starting bpbkar32 on client
06/21/2017 00:00:25 - connected; connect time: 0:00:00
06/21/2017 00:00:26 - Info bpbkar32 (pid=5796) Backup started
06/21/2017 00:00:26 - Info bptm (pid=2192) start
06/21/2017 00:00:26 - Info bptm (pid=2192) using 1048576 data buffer size
06/21/2017 00:00:26 - Info bptm (pid=2192) setting receive network buffer to 4195328 bytes
06/21/2017 00:00:26 - Info bptm (pid=2192) using 128 data buffers
06/21/2017 00:00:28 - Info bpbkar32 (pid=5796) change time comparison:<DISABLED>
06/21/2017 00:00:28 - Info bpbkar32 (pid=5796) archive bit processing:<ENABLED>
06/21/2017 00:00:32 - Info bpbkar32 (pid=5796) not using change journal data for <>: not enabled
06/21/2017 00:00:33 - Info bptm (pid=2192) start backup
06/21/2017 00:00:34 - Info bptm (pid=2192) backup child process is pid 8388.4152
06/21/2017 00:00:34 - Info bptm (pid=8388) start
06/21/2017 00:00:34 - begin writing
06/21/2017 00:02:08 - Info bpbkar32 (pid=5796) 5000 entries sent to bpdbm
06/21/2017 00:02:41 - Info bpbkar32 (pid=5796) 10000 entries sent to bpdbm
06/21/2017 00:05:23 - Info bpbkar32 (pid=5796) 15000 entries sent to bpdbm
06/21/2017 00:06:28 - Info bpbkar32 (pid=5796) 20000 entries sent to bpdbm
06/21/2017 00:09:07 - Info bpbkar32 (pid=5796) 25000 entries sent to bpdbm
06/21/2017 00:17:19 - Info bpbkar32 (pid=5796) 30000 entries sent to bpdbm
06/21/2017 00:33:23 - Error bpbrm (pid=9736) from client CAB-VOP-DC00008.omega.sbrf.ru: ERR - unable to write to pdi device
06/21/2017 00:33:23 - Error bpbrm (pid=9736) from client CAB-VOP-DC00008.omega.sbrf.ru: ERR - Active directory granular restore from this image may not work.
06/21/2017 00:37:21 - Info bpbrm (pid=9736) from client CAB-VOP-DC00008.omega.sbrf.ru: TRV - Starting granular backup processing for (System State\Active Directory). This may take a while...
06/21/2017 02:12:48 - Info bpbrm (pid=9736) from client CAB-VOP-DC00008.omega.sbrf.ru: TRV - Successfully finished granular backup processing for (System State\Active Directory).
06/21/2017 02:13:33 - Info bpbkar32 (pid=5796) 35916 entries sent to bpdbm
06/21/2017 02:13:56 - Info bpbkar32 (pid=5796) 40916 entries sent to bpdbm
06/21/2017 02:14:43 - Info bpbkar32 (pid=5796) 45916 entries sent to bpdbm
06/21/2017 02:15:23 - Info bpbkar32 (pid=5796) 50916 entries sent to bpdbm
06/21/2017 02:16:42 - Info bptm (pid=2192) waited for full buffer 21956 times, delayed 502106 times
06/21/2017 02:16:43 - Info bptm (pid=2192) EXITING with status 0 ----------
06/21/2017 02:16:43 - Info bpbrm (pid=9736) validating image for client CAB-VOP-DC00008.omega.sbrf.ru
06/21/2017 02:16:46 - Info bpbkar32 (pid=5796) done. status: 1: the requested operation was partially successful
06/21/2017 02:16:46 - end writing; write time: 2:16:12
The requested operation was partially successful (1)
What logs should I check?
I have checked the temp folder \Veritas\Netbackup\Temp on the media server (backup2m3) and there is plenty of space on HDD it's on.(701GB free of 787GB)
Many thanks,

----
Best Regards, AlChie
2 REPLIES 2

Nicolai
Moderator
Moderator
Partner    VIP   

Pretty sure you have to check the temp folder on the client, not the media server.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

As per the 2015 solution, you need to check bpbkar log on the client.
Logging level of 3 should be sufficient (but will compound space issue on the client).