Today, I’m going to talk about the backup options Veeam offers for both physical and virtualized Domain Controllers, and backup considerations to keep in mind while you do that. The actual series is going to discuss how Veeam can protect Active Directory data - preserve Domain Controllers (DCs) or individual AD objects and recover either of them when required.
Before reading this, you might want to take a look at the Best practices for AD administration series we posted a while ago. The purpose of this series is intended to aid you with the successful backup and recovery of Active Directory Domain Services with Veeam, giving you all the keys to painless AD protection. Not only is Active Directory a great power, but it’s also a great responsibility - and it requires spending a lot of time with it in order to maximize its capabilities. It’s almost impossible to imagine how system administrators would be able to do their jobs effectively if this technology didn’t exist. Microsoft Active Directory is a standard in corporate environments where authentication and central user-management are required. Remove backups of production VMs (those not to be archived), from moved Copy jobs files that will retain data to be archived.Read the full series: Ch.1 - Backing up Domain ControllerĬh.2 - How to recover a Domain ControllerĬh.3 - Reanimating Active Directory tombstone objectsĬh.4 - Leveraging Active Directory Recycle Bin.
Remove production VMs to archive from originals Backup and Copy jobs (with repos rescan et backups re-maping).Create new Copy jobs for newly created backup jobs, with GFS retention enabled, and set 0 restore points to keep, retain backup locally and on the other site, set repository to our new "Archives" repos, then map moved backups-copy files to those jobs.Create new Backup jobs, with only part of our VMs which we want to archive, set the repository to our new "Archives" repos, then map moved backups to those jobs.Move all my backups and backups-copy files to those new repositories, then launch rescan on them.
Create new repositories "Archives" (only new folders on same storage) on each sites, to split things for monitoring purpose.I plan to re-organize our backup jobs and repositories, because the actual plan is consuming nearly all of our storage on repositories : all of our production VMs are kept with GFS retention policy. Our goal is to kept a part of our production VMs for archive purpose, with maintaining protection for all of our production VMs. Both server have proxy and repository roles, and both are running one job to backup all production VMs of on-site ESXis.Īlso, they are both running Copy jobs to move and retain all backups on local and distant site (GFS retention policy enabled). I have two sites, one hosting the Veeam Management Server, the other hosting a Proxy.
0 kommentar(er)
