You could try to write the backup to a non collocated pool.. so the data gets spread on multiple tape volumes.
Then expiriment with the resourceutilisation parameter in your option file.
The net effect you want to create is to do non qeury restores with as mutch tapemounts as possible... because the data is spread over multiple volumes you get more tape mounts and more restore streams...You also should raise the maxmountpoints paramaters on your client to allocate enough mointpoint for your client.
If you have enough diskspace use devclass volumes file for your onsite pool... this will give you the fastest restore in the biss..( on the client option resourceutil eg 10) ( on your client maxnummp 10 ) using only tape for copypools.
Suc 6.
Koen
From: Robert Ouzen <[EMAIL PROTECTED]> Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Help on SAP filesystems Date: Fri, 6 Feb 2004 10:34:39 +0200
Hi to all
In my organization I have a SAP database to backup I do it with Sap Backint TDP without any problem , my concern is about my File Systems (13 f.s) , in particular the F.S: /sapmnt with thousands of files changing every time.
I backup this station in a particular Stg Pool collocate with selective command e.g.: s // /sapmnt/ /usr /home/ . My backup copy group is in copy mode: absolute and copy serialization: dynamic
My total F.S is 16 G ( 304,000 files) made today a restore test ( all the data is on one cartridge) but the restore is so slow in particular /sapmnt
Did anyone can suggest how to improve this process ... What recommendations to apply , what to exclude ..
TSM Server on AIX 5.1.8 Sap Backint TDP TDP R3 Aix Client of Tsm for AIX 3.7.2 Client OS Level 4.3
Regards Robert Ouzen E-mail: [EMAIL PROTECTED]
_________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
