When you start SnapManager for the first time
After you install or upgrade SnapManager and start the application for the first time, SnapManager verifies the Exchange server, SnapDrive version, and databases for compatibility. You must follow certain guidelines to start SnapManager for the first time.
- What SnapManager verifies at startup
When SnapManager starts for the first time, it verifies the Exchange server first, checks the SnapDrive version, and finally checks for database configuration, ensuring that the basic prerequisites to run the Configuration wizard have been met .
- Why you should administer SnapManager from the system console
Run SnapManager from the system console, not from a Terminal Services client. Do not use Terminal Services for any type of SnapManager administration, because you might miss critical information that is displayed only in pop-up boxes at the system console.
- Starting SnapManager and connecting to the default server
When you start SnapManager for the first time after either an installation or upgrade, you have to select one or more Exchange servers that you want to manage.
- Starting SnapManager and connecting to the CCR server
After starting and connecting to the default server, you can connect to a CCR-enabled server by using SnapManager for Exchange. You need to add the CCR-enabled server if you are using a clustered configuration.
- SnapManager Dashboard view
You can view the status of different SnapManager servers connected to the SnapManager for Exchange network. This is a dynamic view that is refreshed frequently. You can view your Exchange server configuration and add new Exchange servers.
- Scheduled jobs
When you select Scheduled Jobs in the Scope pane, the details of all scheduled jobs such as backup and integrity verification jobs are displayed in the Results pane. You can view, edit, and delete these jobs.
- Database Availability Group
The Database Availability Group (DAG), a high availability feature of Exchange Server 2010, provides database-level recovery from failures and data corruption.
