Image cleanup is cancelling the backup jobs

[Severin]

Hi,

I re-open a problem I already discussed about, without to answer your questions.

I expected the following problem.
Sometimes, the image cleanup job is running during the run of other backup job. That have as consequence that the running backups are all cancelled:

10.01.2011 01:00:18 - granted resource SAP_BrBackup_chbslsv02_on_chbsldd01
10.01.2011 01:00:20 - estimated 0 kbytes needed
10.01.2011 01:00:20 - started process bpbrm (1708)
10.01.2011 01:00:21 - connecting
10.01.2011 01:00:35 - connected; connect time: 00:00:14
10.01.2011 01:00:40 - begin writing
10.01.2011 01:19:27 - Critical bpbrm(pid=1708) from client netbackup-chbslsv02: FTL - socket write failed     
10.01.2011 01:19:28 - end writing; write time: 00:18:48
socket write failed(24) 

The image cleanup is terminate successfully on the same media:

1 0.01.2011 01:19:28 - begin
10.01.2011 01:19:28 - Info nbdelete(pid=5320) deleting expired images. Media Server: netbackup-chbslsv01 Media: \\chbsldd01\backup\chbslsv02\brbackup     
10.01.2011 01:19:28 - started process bpdm (5988)
10.01.2011 01:19:28 - Info bpdm(pid=5988) initial volume \\chbsldd01\backup\chbslsv02\brbackup: Kbytes total capacity: 2628974592, used space: 1487559168, free space: 1141415424
10.01.2011 01:19:28 - Info bpdm(pid=5988) ending volume \\chbsldd01\backup\chbslsv02\brbackup: Kbytes total capacity: 2628974592, used space: 1487559168, free space: 1141415424
10.01.2011 01:19:28 - end ; elapsed time: 00:00:00
the requested operation was successfully completed(0)

You previous contributions was:

Marianne van den Berg You did not mention your O/S or NBU version?

OS: Microsoft Windows Server 2003 R2 Enterprise x64 Edition Service Pack 2

Version of bpbrm.exe: 6.5.2010.423

Marianne van den Berg The problem is possibly not with image cleanup (never seen this at any of our customers, large and small sites) but with Windows memory cache manager.

More of this cancellation occures until today, but the same backup is running without error the most times it run. The cancellation doesn't occur each time, but each time a cancellation occur, I observer the "Image Cleanup" did run too.

Documentation "The Image cleanup property specifies the maximum interval that can elapse before an image cleanup is run. Image cleanup is run after every successful backup session (that is, a session in which at least one backup runs successfully). If a backup session exceeds this maximum interval, an image cleanup is initiated."

On the master server, the properties are set to "After 20 hours" for the Image cleanup.

Andy Welburn So if your backup session has exceeded the 20hour limit then an image cleanup will be instigated whilst the backups are running - this is normal & in no way should affect any active jobs.

The backup (session? what is a backup session?) did start at 01:00, and it's done generaly into 3 hours.

In my first discussion, the error message was about

"image write  failed: error 2060017: system call failed"

Today was the message about:

 FTL - socket write failed 

Who can tell me what is going wrong? Why the cleanup job is running before the backup jobs are finished (i.e. whilst the backup is running)?

Thanks for your help

Best Regards

Séverin

[Marianne · Accepted solution]

Previous post: https://www-secure.symantec.com/connect/forums/image-cleanup-cancelling-backup-jobs

Have you checked the TN that I've posted there? http://www.symantec.com/docs/TECH56632

Overview:
......
"image read failed; error 2060017: system call failed" errors


Cause:
• More files are open than the memory cache manager can handle. As a result, the cache manager has exhausted the available paged pool memory.

• The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is exhausted).


Solution:
On the Windows 2003 server in question, 2 Registry Keys (PoolUsageMaximum, PagedPoolSize) may be created to fine-tune how the operating system manages Paged Pool Memory.  For complete details on creating and configuring these registry keys, review Microsoft Knowledge Base Article below:
 http://support.microsoft.com/kb/304101/en-us