Hi Darren,
I have had customers running snapmanager and I have never seen anything like this. As far as I know Snapmananger uses the the Exchange backup API so nothing should be different, except where the backup is stored and how it is stored.
How many stores and how many storage groups does your customer have ? Have they been changing their exchange storage layout lately?
Victor
-----Opprinnelig melding----- Fra: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] På vegne av Darren Dunham Sendt: 10. november 2004 21:55 Til: toasters@mathworks.com Emne: Exchange growth after migration.
Danger, I'm not a windows person, so I'm a little over my head on part of this.
I've got a client that has just completed a migration of their Exchange 2000 servers onto a netapp iscsi lun with snapmanager. So far everything seems to be working great on the netapp side.
However, after running on the server for two weeks, their private store has jumped from about 120G to about 220G. Some of their support is suggesting that the standard Exchange backup process has some cleanup functions that run during the backup. Now that it doesn't run any longer with snapmanager in place, the cleanup is no longer performed and the DB grows out of control (unless you shut down and do a defrag).
Does this sound familiar to anyone? I'm looking for confirmation, refutation, or hey, even solutions on this. I'm hoping there are similar environments out there. Specifically, a larger database (such that the nightly cleanup process can't tackle the entire store overnight).
Please don't ask me for anything that requires debugging. I'm not the windows guy. I'm just trying to find out if this growth has occurred at other sites. It's been escalated with both Netapp and Microsoft, but no word yet on if this is expected behavior.
Thanks!