Be VERY careful here. If your SnapInfo Lun isn't big
enough, SME backups WILL fail (experience talking here). It needs to be
big enough to house (potentially) the entire transaction log, plus some.
Glenn (the other one again).
Hi Jochen,
Snapinfo-lun is needed for SnapManager for
Exchange(SME). This is where SME stores its information for recovery. Its
basically used when running "up to the minute recovery", where it copied all the
transcaction logs before it truncated them while creating the snapshot backups.
So when you do an "up to the minute" recovery from older snapshots, it uses this
location to bring in the older transaction logs to be replayed.
Why do you want to configure 2 separate aggregates? did you mean
volumes? I'd rather have a very large aggregate with as many disks I can get
hold of instead of 2 smaller aggregates. It definetly improves performance.
The way we have it setup in our environemnt is 1 large aggregate with 3
volumes per exchange host..
- 1 vol for the storage group with luns for each
store
- 1 vol for log lun
- 1 vol for snap info lun
We also have other
CIFS shares on volumes/qtrees within the same aggregate.
Hope this
helps
-G
On 3/29/06, Willeke,
Jochen <Jochen.Willeke@wincor-nixdorf.com>
wrote:
Hi
everybody,
we are setting up an exchange 2003 system on a filer. Right
now i am
about to size the system. I often read that i need to have
a
snapinfo-lun. But i do not understand where i need this lun
for.
Exchange does not need it, does it?
What i want to configure
are two aggregates. One containig qtrees with
luns for the databasefiles
and one aggregate with qtrees and luns for
the logfiles. And if really
needed i would put the snapinfo-lun into the
logfile
aggregate.
Perhaps somebody has already set up an exchange server on
netapp storage
and can help me.
Thanks a lot in
advance
Jochen