Richard, What did the accounting log say for the transfer ? I know that you said there was no compression set, but it would be good to know that the results from the accounting log for the session matched that of what was reported in the activity log. You can check the accounting log with the following
select bytes,entity,number from summary where entity='nodename' and number=session number Leigh -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: 17 November 2005 15:57 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Storage pool usage But I never saw any tapes being used by the backup process ? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of David E Ehresman Sent: Thursday, November 17, 2005 10:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Storage pool usage The client sends an estimate of the amount of data it is sending. If a file is calculated to be too big to fit in the 1st storagepool, it is written to the 2ndard stgpool (usually tape) instead. >>> [EMAIL PROTECTED] 11/17/05 10:22 AM >>> Hi *, I have a 300Gb storage pool which I used last night to send a 306Gb Oracle database using RMAN ( no compression on the backup ). I checked the usage of the storage pool after the backup, and it only shows 60% used. However,I checked the activity log and I condfirmed that 306Gb of data was sent to the server and I did a q con on the volumes in the storage pool and all the files are there. Shouldn't the storage pool show 100% used ? No migrations ever happened during the backup the whole time it ran. Shouldn't a migration to tape have kicked off as I had exceeded the storage pool capacity ( we set migration to 100 during the night to not allow migrations unless absolutely necessary ) ? Rich