Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Active Directory Disaster Recovery

You're reading from  Active Directory Disaster Recovery

Product type Book
Published in Jun 2008
Publisher
ISBN-13 9781847193278
Pages 252 pages
Edition 1st Edition
Languages
Author (1):
Florian Rommel Florian Rommel
Profile icon Florian Rommel
Toc

Table of Contents (17) Chapters close

Active Directory Disaster Recovery
Credits
About the Author
About the Reviewers
1. Preface
1. An Overview of Active Directory Disaster Recovery 2. Active Directory Design Principles 3. Design and Implement a Disaster Recovery Plan for Your Organization 4. Strengthening AD to Increase Resilience 5. Active Directory Failure On a Single Domain Controller 6. Recovery of a Single Failed Domain Controller 7. Recovery of Lost or Deleted Users and Objects 8. Complete Active Directory Failure 9. Site AD Infrastructure Failure (Hardware) 10. Common Recovery Tools Explained Sample Business Continuity Plan Bibliography

LRS—Lag Replication Site


These sites are also often called RLS (Replication Lag Site), DRS (Delayed Replication Site), and just plain lag site. Officially, there really isn't a "correct" name as Microsoft and AD experts have referred to this concept in all four ways.

A lag site is a site in your AD that will contain at least one DC. This site is configured so that the replication only happens at a delayed schedule compared to all the other sites. This can be anything from one day to one week.

The purpose of lag sites is primarily to restore deleted objects quickly without having to go through the process of authoritative restores or even start working with tapes. If something gets inadvertently deleted, all that is needed is a replication in the opposite direction, from the lag site to the production DCs, and the deleted data is recovered. It is a clean, fast, and efficient way to recovery.

The other feature that is a natural by-product of a lag site, and used by quite a few organizations,...

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 $15.99/month. Cancel anytime