Top 5 Reasons Not to Copy Your Trade 2010 Repository

The practice of fabricating backup copies of one's databases is as old as databases itself. As it means you might lose your entire company overnight you just cannot afford not to have copy if you have a manufacturing database of any form. Exchange 2010 host introduces new data safety functions that, if executed precisely, save from investing the amount of money in backup computer software and equipment. Let's review several of those techniques.Exchange Database ReplicationPrevious type of Exchange server introduced the philosophy of database replication. One user mailbox database could possibly be replicated to some other host effectively developing a redundant database copy. Exchange 2010 created on that function and it's simple to have up to 16 copies of a simple repository. Losing among the database copies means you still have 15 copies left. But let us consider more practical approach and that is having three database copies.Losing one copy would still leave us with two copies so we are still not informed. If we just had two copies originally like in previous Exchange variation dropping a single copy would keep us at risk situation. If the actual media of the database has some harm perhaps not seen before it may come to the surface now and we'd looe our complete database. Three copies is the minimum recommended number of database copies if we are to embrace the philosophy of no database backups.Exchange Database Lagged ReplicationIn a three database copies situation being a copy we could assert one database copy. This effectively produces a database that's perhaps not current for the other two databases. We could imagine that a logical failure in the database would get replicated for the remaining copies which would make all database copies unusable because the reproduction usually happens instantly. If we declare since the lagged database one database the replication won't occur in real time but it would lag for your support of time we set. It could be one-day, weekly or possibly a month. By doing this we're protected from logical failures.E-mail maintenance periodBut what happens whenever a user unintentionally deletes an e-mail communication from his inbox? The e-mail could end up in the deleted objects folder but when he purges the folder we've lost the e-mail meaning forever, right? Wrong. There is a repository feature that maintains deleted items for a specific amount of time in-the users mailbox although e-mail has been deleted. The default time an email is kept is usually 14 days but this may be customized to your or your people needs.Deleted mailbox retentionIf you delete the entire mailbox by intent or by accident it'll stay in the database for extra 30 days until it's immediately rid. You can modify this setting to your needs the same as you can do with the e-mail retention feature.Extended data retentionIf you have a requirement for extensive data retention of multiple month you can nevertheless resort to classic backup but perhaps classic backup has its limits including space, amount of tapes, etc. If your business should comply with laws that control knowledge retention period in your market you should look at journaling and preserving top features of Exchange. Using common backup for longterm data protection could be the proper action to take until you need to extract some data from that backup. Then it might show itself hard to control. Journaling and archiving characteristics are designed for this function and you will get better results using these in place of backup.