![]() Windows Native Deduplication: File Agent backup is recommended where a machine uses native Windows dedupe.VM backup is capable only of complete system restore and is supported but not recommended. File Agent backup is required to access restored disk data granularly. Microsoft Dynamic Disks: (also applies to any kind of software based RAID system).AD Admins should also configure and be familiar with Windows wbadmin system state backups that are necessary for some DR scenarios including when it is necessary to roll back AD without first restoring servers. Unitrends recommends using image backups of a DC in environments that have exactly one DC. Active Directory Servers: Unitrends recommends using File Agent backups for AD servers where more than 1 AD server is deployed in a domain or forest.File Agent + SQL App backups are required for all other AG and SQL Cluster scenarios. SQL AG Nodes: Image backups are recommended for SQL AGs where AG node uses only local storage (no iSCSI, FC, or CSV use by the node).File Agent and VM backups are only supported over private circuits (Private MAN/WAN). Backups over a WAN: WAN backups are supported with Image Agent over open WAN where bandwidth and latency requirements are met.Application Backups are required for servers hosting Oracle, SharePoint, Exchange DAGs, many SQL AG configurations, and all traditional shared storage cluster systems.Ĭommon Scenarios that override the above best practices:.If the intent is to support instant recovery of high performance systems, replicas using file backup or VMWare backup may be required. File Agent backups (GoS) are best for scenarios for individual systems not supported by the above backup types, or for special scenarios to add backup or recovery flexibility.Image Agent Backups (including those taken using the agent inside a VM) are typically the best in all other scenarios, especially where recovery may involve a Unitrends Physical appliance with Instant Recovery.Virtual Machine Backups (HoS) are best where the intended recovery target is back to a hypervisor node of the same platform.Simple Best Practices: As a general rule, unless otherwise eliminated by supported configurations or documented restrictions, the following are loose best practices for determining which type of backup of a particular system to use. Performing Image based backups using in-guest deployed agents (also referred to as block backups).Performing Traditional Agent File Backups using in-OS deployed agents (Also referred to as GOS backups), which may also include separate Database level backups.Performing VM-level backups (also called Host Based backups, or HOS).In this KB, we'll attempt to summarize that information into a single source to help better convey the best use cases for each protection model. Each of these methods have different benefits, restrictions, and options depending on several factors clarified in the Unitrends Administrators Guide. With Unitrends Release 10.3 and higher, customers have more choices for types of backups methods than prior. This KB will attempt to explain the supported best practices for these varying backup types ISSUE With 10.3 and higher releases, customers have more choices for types of backups methods than prior.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |