folder backup on client doesn't work
Hi experts,
I tried to backup a local folder on a client server but failed, below are the logs, any idea?
07/30/2019 18:08:20 - connecting
07/30/2019 18:08:24 - Info bpbrm (pid=11308) starting bpbkar32 on client
07/30/2019 18:08:24 - connected; connect time: 0:00:00
07/30/2019 18:08:26 - Info bpbkar32 (pid=7584) Backup started
07/30/2019 18:08:26 - Info bpbkar32 (pid=7584) change time comparison:<disabled>
07/30/2019 18:08:26 - Info bpbkar32 (pid=7584) archive bit processing:<enabled>
07/30/2019 18:08:26 - Info bptm (pid=10732) start
07/30/2019 18:08:26 - Info bptm (pid=10732) using 65536 data buffer size
07/30/2019 18:08:26 - Info bptm (pid=10732) setting receive network buffer to 263168 bytes
07/30/2019 18:08:26 - Info bptm (pid=10732) using 30 data buffers
07/30/2019 18:08:26 - Info bpbkar32 (pid=7584) not using change journal data for <F:\local folder>: not enabled
07/30/2019 18:08:27 - Info bptm (pid=10732) start backup
07/30/2019 18:08:27 - Info bptm (pid=10732) backup child process is pid 8512.11064
07/30/2019 18:08:27 - Info bptm (pid=10732) Waiting for mount of media id 6334L6 (copy 1) on server abcde.
07/30/2019 18:08:27 - Info bptm (pid=8512) start
07/30/2019 18:08:27 - mounting 6334L6
07/30/2019 18:09:31 - Info bptm (pid=10732) media id 6334L6 mounted on drive index 0, drivepath {3,0,0,0}, drivename HP.ULTRIUM6-SCSI.000, copy 1
07/30/2019 18:09:31 - mounted 6334L6; mount time: 0:01:04
07/30/2019 18:09:39 - positioning 6334L6 to file 16
07/30/2019 18:11:00 - Info bptm (pid=10732) waited for full buffer 0 times, delayed 0 times
07/30/2019 18:11:00 - positioned 6334L6; position time: 0:01:21
07/30/2019 18:11:00 - begin writing
07/30/2019 18:11:13 - Info bptm (pid=10732) EXITING with status 90 <----------
07/30/2019 18:11:17 - Info bpbkar32 (pid=7584) done. status: 90: media manager received no data for backup image
Thank you
You can check bpbkar log to see how the backup selection path is interpreted.
About tape - best to ask about different subject in separate/new discussion.
The option to "Allow backups to span tape media" is enabled by default in NBU host properties (see Chapter 3 of Admin Guide I)
If all tapes are full, the backup will fail with Status 96.
NetBackup will only overwrite previously used media if all images on the tape has expired.Important to plan for sufficient media that matches your company's retention requirements.
Never expire existing, unexpired images just because you do not have sufficient media for new backups.
'Murphy' will make sure that your users will ask for a restore the day after you have manually expired tapes and overwrote the contents.CCBNZ you still seem confused about difference between configuring backups of DFS vs. configuring backups of DFSR. You need to be careful. You need to be sure that you understand. You need to check your backup contents, inpect the contents via the restore GUI, be sure you understand what is actually being picked up. Also, see this:
https://vox.veritas.com/t5/NetBackup/DFS-folder-backup-shadow-copy-impossible/m-p/869099#M240563
.
Re tapes:
1) Will Netbackup knows if a tape is full and move to next one?
Yes.
2) If a full backup can't be fit into one drive it will continue to write to the next available one?
No necessarily the next drive, certainly another tape, but usually on same drive.
3) What happen if all the tapes are full?
The currently running backups will fail.
4) Is there a configuration I can change the behavior, e.g. if all tapes are full, overwrite the first tape in the volume pool?
No.
I'll apologize to sdo in advance, but, but I just can't help myself .
1) Will Netbackup knows if a tape is full and move to next one?
Yes.
Actually, no - NBU has no understanding of tape capacity, it thinks every tape is infinite. It relies on the drive firmware telling the tape driver that the tape is full, which in turn tells NBU. Ultimately, the result should be as if 'NBU' detected it.
Why does this matter - it does't until tapes start getting marked as full at an amount way below the natve (uncompressed) capacity - armed with the above information however, you would understand that the isue is tape drive/ hardware/ firmware / driver related not NBU.
