If this happens whenever he accesses the files QUICKLY in a row IHMO it
does not matter would this access be through TSM, copy files (as he tested)
or by ZIP, RAR. The only chance for success can be if file compression tool
slows enough file access that first compressed files "timeout" and less
than 190 GB were "recently" opened.
Regards
Zlatko Krastev
IT Consultant
Maurice van 't Loo <[EMAIL PROTECTED]> on 11.09.2001 15:04:25
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Backing up large amounts of data on Windows NT
I don't know if NT can handle it, but you can try to RAR or ZIP the file.
With RAR you can also cut the file in pieces.
Succes,
Maurice van 't Loo
Compare Computers
The Netherlands
----- Original Message -----
From: "ProtoTipo srl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 10, 2001 6:51 PM
Subject: Backing up large amounts of data on Windows NT
> Hi all,
>
> I have a 200 GB SAP R/3 - Oracle database on a Windows NT box. Every
night
> I run an online backup using TDP for R/3 and everything goes ok.
> Once a week I run a script that stops the database and performs a whole
> backup of the NT box at the file-system level. After having backed up
about
> 180 GB of files, the backup terminates with the error:
>
> ANS1028S Internal program error. Please see your service representative.
>
> I found an article on Microsoft Knowledge Base, Q192409, that says:
>
> Open Files Can Cause Kernel to Report INSUFFICIENT_RESOURCE: "If you have
> approximately 180 GB of open files that are not being closed continuously
> or are opened and closed rapidly in a looping condition, you may be
> experiencing this problem"
>
> Also if I try to copy 180 GB of files disk-to-disk from a NT box to
another
> one, I got that error.
>
> Again, from Microsoft Knowledge base:
> Open the Task Manager, select Performance window and have a look to the
> "Paged" value of the kernel memory on the bottom-right. This value
increase
> (1KB for every MB of file opened) without decrease. Once reached the
value
> of 190MB the error occurs.
>
> At the moment, the only way to work around the problem seems to be a
reboot
> of the machine (but it's not advisable during scheduled nightly or
weekend
> backups!)
>
> I noticed also that when I start the database again, the paged memory
pool
> is freed...but I can't continue the backup after that, otherwise the
> database won't be consistent.
>
> I opened a PMR, but Tivoli Support told me they can't reproduce the
> problem, because they don't have a NT box with that much space. They're
> looking for a suitable environment.
>
> Any ideas??
>
> Thanks in advance,
> Stefano Massi
>
