Skip to content

Conversation

@Jeran-Tek
Copy link

Removed redundant sentence about backing up domain controllers. Backing up the FSMO role owners is unnecessary because they can be seized without loss of data. Starting a restored DC with a FSMO role can significantly delay the first boot because of initial synchronisation requirement.

Removed redundant sentence about backing up domain controllers.
Backing up the FSMO role owners is unnecessary because they can be seized without loss of data.
Starting a restored DC with a FSMO role can significantly delay the first boot because of initial synchronisation requirement.
@prmerger-automator
Copy link
Contributor

@Jeran-Tek : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit c20085d:

✅ Validation status: passed

File Status Preview URL Details
articles/backup/active-directory-backup-restore.md ✅Succeeded

For more details, please refer to the build report.

@AbhishekMallick-MS
Copy link
Contributor

Hi @AkshitGureja , as discussed, request you to please validate the updates and share your inputs/confirmation. Thanks.

@ttorble ttorble requested a review from Copilot December 1, 2025 16:13
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR simplifies the backup best practices documentation for Active Directory domain controllers by removing guidance about backing up FSMO role owners. The change reflects that FSMO roles can be seized without data loss, and restoring DCs with FSMO roles can cause delays during initial synchronization.

Key Changes:

  • Removed the recommendation to back up all domain controllers holding FSMO roles

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ttorble
Copy link
Contributor

ttorble commented Dec 1, 2025

Thanks @AbhishekMallick-MS

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Dec 1, 2025
@prmerger-automator
Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @AbhishekMallick-MS

@AkshitGureja
Copy link
Contributor

Reviewed the PR, it's good to go. Thanks for the inputs @Jeran-Tek. @AbhishekMallick-MS please do the needful.

@AbhishekMallick-MS
Copy link
Contributor

@AkshitGureja - Thanks much for the confirmation!

#sign-off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants