Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Exchange 2013 Cookbook

You're reading from   Microsoft Exchange 2013 Cookbook Get the most out of Microsoft Exchange with this comprehensive guide. Structured around a series of clear, step-by-step exercises it will help you deploy and configure both basic and advanced features for your enterprise.

Arrow left icon
Product type Paperback
Published in Sep 2013
Publisher
ISBN-13 9781782170624
Length 354 pages
Edition Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Michael Van Horenbeeck Michael Van Horenbeeck
Author Profile Icon Michael Van Horenbeeck
Michael Van Horenbeeck
Peter De Tender Peter De Tender
Author Profile Icon Peter De Tender
Peter De Tender
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Microsoft Exchange 2013 Cookbook
Credits
About the Author
Acknowledgments
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
1. Planning an Exchange Server 2013 Infrastructure 2. Installing Exchange Server 2013 FREE CHAPTER 3. Configuring the Client Access Server Role 4. Configuring and Managing the Mailbox Server Role 5. Configuring External Access 6. Implementing and Managing High Availability 7. Transitioning to Exchange Server 2013 8. Configuring Security and Compliance Features 9. Performing Backup, Restore, and Disaster Recovery 10. Implementing Security Getting to Know Exchange Server 2013 Index

Introduction


In Chapter 1, Planning an Exchange Server 2013 Infrastructure, we touched briefly on the subject of backups and disaster recovery. So it's high time for us to dig a bit deeper.

When designing an Exchange infrastructure, one of the topics lying on the discussion table always includes backups. Now, what is it that turns this subject into an object for discussion?

Well in my opinion this is because everyone knows that taking backups is critical, yet a lot of organizations don't always follow the best practices. One particular thing that frequently pops up is the question whether or not backups are regularly tested. Because after all, what is the point in taking backups if you never performed a restore? How about finding out your backups are invalid, right at the moment when you need to restore them? Not particularly a situation I'd like to see myself end in.

Ask yourself the same question. Do you test your backups regularly? If you honestly answered "No we don't even have such a plan...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image