Dell,
we should not do this or there would be no benefit of doing so? Are there
any known issues (like transaction sending to more than one stgpool) if
these zero-lenght object are bound to different class?
Zlatko Krastev
IT Consultant
Del Hoobler <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.06.2003 22:55
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: TDP Exchange META data
Bill,
No. You should not do this.
The meta object in SQL actually contains restorable data
that describes the physical layout of the database.
That data is used for some types of queries and for
the GUI restore tree expansion. So, keeping the meta data
on quicker (available) storage devices is a good idea.
The meta object in Exchange is a zero length object
that contains no data in the object itself. It is
simply used as the coordinator. There is no reason
to redirect this to a different destination.
Thanks,
Del
----------------------------------------------------
> I experimenting with the TDP SQLServer, we could that directing the META
> data to a disk-only storage pool separate from the data has a big impact
on
> queries and restore GUI. This data doesn't appear to be very large
(META)
so
> we include it in out DIRMC destination.
>
> Would the META data for Exchange backups benefit from this same scheme?
