Hi Ben, I wish TSM could perform both at the same time, but it is not doable. This is a Microsoft restriction, not a TSM implementation issue. The Microsoft interfaces to check the integrity are at the whole file-level, not at a buffer-level like we would need to perform the backup and integrity check at the same time. We have asked Microsoft for a better interface, but it has not raised high enough in their queue. And with their current emphasis on replication and also allowing customers to skip the integrity check in those DAG environments, I suspect they will not invest more in this and encourage customers to use Exchange 2010 DAG replication to handle their integrity checking.
Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 08/25/2011 04:41:08 PM: >> From: Ben Bullock <bbull...@bcidaho.com> >> To: ADSM-L@vm.marist.edu >> Date: 08/25/2011 04:57 PM >> Subject: Re: Exchange Legacy 2007 to VSS 2010 backup performance >> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> >> >> Del, >> Thanks for piping in with the official word, since all my >> statements were "anecdotal" in nature. I wasn't too far off though. ;-) >> >> I actually like the idea of the integrity check being performed at >> the same time as the backup and then failing the backup if it finds >> anything. It just seems more efficient than reading the data twice. >> Our SAN admins I'm sure would prefer the lesser number of IOPS on >> the storage. >> >> Are there any options/flags I can use to make it behave that way? >> >> Thanks, >> Ben