I am just reframing  my query just in case , My configuration is tested with
a test server in this domain. The destination pool is correctly configured
as the diskpool. In the test case it works fine by utilizing the diskpool.
However when I include the production exchange server in the same domain
configuration , It fails to use the diskpool and starts using the secondary
storage pool. My information store on the production server is very large
than the diskpool.
I wish to benefit from users having exchange agent.

do I necessarily have to increase the diskpool to the size of the
information store to be utilized?

sincere regards

sri
> -----Original Message-----
> From: Gogineni, Sri
> Sent: Tuesday, November 03, 1998 6:41 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      exchange agent configuration
>
> Hi all,
>        I have an information store of about 17GB to backed up. I know this
> information store is treated as two or three individual objects. The
> problem is that while I backup it does not go to a diskpool which is
> significantly less than the 17Gb size ( approx about 8GB). and instead it
> is directly backed up onto the secondary storage pool.
>
> Is there any way of forcing the agent to use the diskpool  or do I have to
> live with this degraded performance?.
>
> Thanks
>
> Sri