SnapManager provides rapid online backup and near instantaneous restoration of
Exchange databases by using online Snapshot™ technology that is part of the
Data ONTAP® software and integrating the Microsoft Exchange backup and
restore APIs and VSS. SnapManager can also leverage the SnapMirror
capabilities of storage systems to provide on-site or off-site SnapManager backup
set mirroring for disaster recovery.
Data management:
SnapManager supports the following data management
capabilities:
◆ Migrating Exchange databases and transaction logs to LUNs on storage
systems
◆ Backing up Exchange databases and transaction logs from LUNs on storage
systems
◆ Verifying the backed-up Exchange databases and transaction logs
◆ Managing the SnapManager backup sets
◆ Restoring Exchange databases and transaction logs from previously created
SnapManager backup sets
Data archival for long-term or remote storage of backups: You can
use SnapManager to create offline archives of Snapshot copies containing
Exchange backup sets for long term or remote backup storage. Three different
archive methods are supported:
◆ Manually initiated archival using NDMP (Network Data Management
Protocol) or the storage system’s dump command
◆ Manually initiated archival using a Windows backup utility
◆ Automatic archival using the Run Command After Operation feature with
your backup operation
The SnapVault software can be used to archive backup sets.
What Snap Manager does NOT do :
SnapManager 4.0 for Microsoft Exchange does not support the following uses:
◆ SnapManager does not support the capability to restore individual mailboxes
or public folders.
◆ SnapManager does not support SnapDrive versions prior to 4.2.1.
◆ SnapManager does not create or restore backups of Microsoft Exchange
databases that are stored on storage devices that are provided by companies
other than NetApp.
◆ SnapManager does not support Microsoft Windows 2000.
◆ SnapManager does not restore Microsoft Exchange Server 2003 and
Microsoft Exchange Server 2007 databases to an alternate location.
◆ SnapManager does not back up and restore Microsoft Exchange 5.5 and
Exchange 2000 databases.
◆ SnapManager is not supported for use on Windows Server 2003 IA-64
edition.
2 comments:
few points..
1. Install SME on both the nodes before starting the SME on the node which owns the resource group. without installing the SME on other node, will have the LUN status as "INVALID".
2. Transaction logs and exchange databases should be in a FCP or ISCSI lun.
3. Verification server should be a exchange server.
Procedure I carried out for configuration :
1. Install Snapmanager on the cluster owned node, then on the other node. Its a windows cluster.
2. Start snapmanager on the node which owns the cluster resource.
3. Exchange databases & transaction logs should reside on the lun.
4. Snapmanager can also leverage the snapmirror capabilities of storage systems to provide onsite offsite snap manager backup set mirroring.
5. User account to run snap manager.
5(a) a/c must have administrator privileges.
5(b) a/c must also have system administrator privileges.
6. It should have snapdrive 5.0 or higher on both the nodes to have the lun detected.
7. SME_snapinfo is the directory created to store the files.
Post a Comment