Job stop every 50Gb
Hello
We have Media Server Deduplication Pool for backup to disk.
Now each job flow is a sequence about 15 min write first 51 200 000 Kb data and then hang for about 1,5-2 hours then write next 50Gb and hang again and ect. This job flow is same for all policies type: vmware, exchange, file, catalog.
Part of status log of catalog backup:
11/22/2017 06:21:30 - Info bptm (pid=11776) start backup
11/22/2017 07:41:37 - begin writing
11/22/2017 13:57:56 - Info bptm (pid=11776) waited for full buffer 25123 times, delayed 139028 times
11/22/2017 13:57:56 - Info bpbkar32 (pid=15148) bpbkar waited 3838 times for empty buffer, delayed 3991 times.
11/22/2017 13:58:13 - Info bptm (pid=11776) EXITING with status 0 <----------
So backup ~220Gb of catalog take about 7,5 hours instead of 40-50 minutes .
No any errors in status log. As I understand job just wait some timeout and write next.
This value (50Gb) as i understand correlate with only Fragment Size of Deduplication Pool STU.
Why cause of this behavior? How to fix it?
Insufficient memory could very well be the cause.
This TN is actually more accurate: https://www.veritas.com/content/support/en_US/doc/25074086-127355784-0/v25295647-127355784
- at least 1GB RAM for each TB of dedupe storage.
That is over and above 8GB RAM needed for master server processes.
Experience has shown that 1.5 GB RAM per TB is advisable.The MSDP 'write' process can be followed in bptm log.
Level 3 logs should be sufficient.
