You can mount a database and access mailboxes using MAPI based tools, but no client can connect.Ĥ. Client connections are blocked to recovery databases. You can only have one recovery database per server.ģ. A recovery database doesn’t count against any maximum number of databases your license entitles you to, so if you are using Exchange 2010 Standard, you can still have your five mailbox databases plus one recovery database.Ģ. How recovery databases differ is important to understand.ġ. However, that is where the similarities end. Recovery databases are similar to other Exchange mailbox databases in that they require storage, will have both database and log files, and will consume the same amount of space for the same amount of data.
#Exchange 2010 recovery database how to
In this post we are going to take a look at how to create a recovery database in Exchange Server 2010 so that you can recover data from a backup in the event something happens. You can create regular backups and store the tapes offsite to ensure you can restore content even after a user has accidentally deleted something critical. You can implement Exchange archiving to capture a copy of every email message that goes in or out of your environment to ensure you have a copy. You can span a WAN with a DAG to keep mail available even if you have a data Center outage.
You can create Database Availability Groups (DAGs) to ensure that that mail remains available even if you suffer a server failure. There are several ways Exchange 2010 administrators can protect their users’ critical data, and a mix of approaches may be the best way to do this, depending upon your users’ needs.
0 kommentar(er)
