Active Directory
Active Directory
Microsoft's central directory for users, computers, groups and access control in a Windows domain.
In everyday business: One staff account can be managed centrally instead of separately on every PC.
WINDOWS BACKUP
Windows Server Backup and Recovery Playbook
Design Windows Server backup around recovery requirements, system state, files and tested restores rather than job completion alone.
Learning objectives
- Explain the main purpose of Windows Server Backup and Recovery in plain language.
- Identify the components that must work together for the service to operate.
- Use evidence to separate a design problem from a configuration or physical fault.
- Describe the business impact of a failure and the evidence required for handover.
Why this matters in a real company
For a company, the question is simple: if a server fails or files are encrypted or deleted, how much work is lost and how long before people can work again? This chapter turns that business question into a technical recovery design.
PLAIN ENGLISH
Technical terms used in this chapter
You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.
Hypervisor
Hypervisor
Software that lets one physical server run multiple isolated virtual machines.
In everyday business: One powerful server can safely run several separate business servers.
Snapshot
Snapshot
A point-in-time storage or VM state used for short-term rollback depending on the platform.
In everyday business: It can quickly undo a bad change, but it is not automatically an independent backup.
Volume
Container Volume
Persistent storage kept separately from the short-lived container filesystem.
In everyday business: Company data can survive when an application container is replaced.
Backup
Backup
An independent recoverable copy of data or system state.
In everyday business: It is the safety net for deletion, corruption, ransomware, hardware loss or major mistakes.
RAID
Redundant Array of Independent Disks
A method of combining drives for capacity, performance and/or tolerance of certain drive failures.
In everyday business: A failed disk does not always mean immediate data loss, but RAID is not a backup.
ACL
Access Control List
A list of rules that says which network traffic is allowed or blocked.
In everyday business: Like a security guard checking a list at a door.
VM
Virtual Machine
A software-defined computer running on a hypervisor.
In everyday business: It behaves like a separate server even though it shares physical hardware.
BUSINESS TRANSLATION
What this means outside the server room
This topic affects the systems staff depend on for sign-in, files, applications and business continuity. The technical design determines how easy the environment is to manage and how painful a failure becomes.
RAID
What it means: RAID combines several drives so the storage system can keep operating through certain drive failures, depending on the RAID level.
In normal business language: Think of RAID as keeping the business open when one filing cabinet drawer breaks. It helps availability, but it does not protect you if somebody deletes the wrong folder, malware encrypts the files, or the whole building is lost.
Why the decision matters: Use RAID to reduce downtime from disk failure, and use backup for recovery from deletion, corruption, ransomware and larger disasters.
Active Directory
What it means: Active Directory centrally manages users, computers, groups and access in a Windows domain.
In normal business language: Think of it as one employee identity system for the company instead of separate usernames and passwords on every computer and server.
Why the decision matters: Use it when a company needs central sign-in, consistent permissions, controlled administrator access and easier onboarding/offboarding.
Hypervisor
What it means: A hypervisor lets one physical server run several isolated virtual machines.
In normal business language: Think of one office building divided into secure independent suites. The building is shared, but each tenant operates separately.
Why the decision matters: Virtualization reduces hardware sprawl and improves flexibility, but the physical host becomes important because several business systems can depend on it.
Virtual Machine
What it means: A virtual machine is a software-defined computer with its own operating system, memory, CPU allocation, disks and network interfaces.
In normal business language: It behaves like a separate server even though several VMs may share one physical machine.
Why the decision matters: VMs are useful for separating roles such as domain control, file sharing and applications while keeping management and recovery flexible.
Backup
What it means: A backup is an independent recoverable copy of data or system state.
In normal business language: Think of it as having a duplicate of important company records stored safely away from the live filing cabinet.
Why the decision matters: A backup only counts if it can be restored. Test recovery, not just backup completion.
Snapshot
What it means: A snapshot is a point-in-time state of a storage volume or VM on the same platform.
In normal business language: It is like a quick undo point inside the same office. Very useful for rolling back a mistake, but not enough if the whole storage system is lost.
Why the decision matters: Use snapshots for fast rollback, but keep independent backups for real disaster recovery.
Install the feature
Install-WindowsFeature Windows-Server-Backup
wbadmin
Microsoft documents wbadmin commands for configuring and running Windows Server Backup.
wbadmin get versions
wbadmin get disks
wbadmin start backup -backupTarget:E: -include:C: -quiet
Commands are examples. Validate target, volumes and application requirements before production use.
System state
For roles such as Active Directory, system-state backup/recovery has special significance. Do not assume a normal file copy is an AD recovery method.
Independent backup
A backup stored on the same RAID set or VM datastore is vulnerable to the same storage failure. Keep a recovery copy in a different failure domain when the business requires it.
Restore drill
- Restore one ordinary file.
- Restore a representative application/server in isolation.
- Record restore time.
- Verify ACLs and application consistency.
What fails
- Never testing a restore.
- Backing up encrypted data without preserving recovery keys.
- Keeping only one online backup copy.
- Assuming hypervisor snapshot equals backup.
PRACTICAL WORK
Hands-on lab
Create a small isolated lab that reproduces the chapter's core architecture. Record the starting configuration, make one controlled change and prove the result with measurable evidence.
Troubleshooting exercise
Take one realistic failure, list the evidence you would collect before changing anything, then write the shortest fault-isolation path.
Chapter field checklist
- I can explain the subject without relying only on acronyms.
- I can draw or describe the main traffic, storage, power or service path.
- I know what normal operation should look like.
- I know which logs, counters or test results prove the result.
- I can explain the business impact if this component fails.
- I would document the final configuration and evidence at handover.
Chapter summary
Windows Server Backup and Recovery Playbook should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.
Technical references
Use the current product documentation and project requirements for production work.