Agent Image Review and Comparison - The Made in America Can Be Fun For Everyone

With 10. 3 and greater releases, customers have more options for types of backups methods than prior. This KB will attempt to describe the supported best practices for these varying backup types With Unitrends Release 10. 3 and higher, clients have more choices for kinds of backups approaches than prior.

In this KB, we'll attempt to sum up that information into a single source to help better convey the best use cases for each defense model. This includes: Carrying out VM-level backups (also called Host Based backups, or HOS) Performing Standard Agent File Backups utilizing in-OS released representatives (Also referred to as GOS backups), which might also consist of separate Database level backups Carrying out Image based backups using in-guest deployed agents (likewise described as block backups) As a general guideline, unless otherwise gotten rid of by supported setups or recorded restrictions, the following are loose finest practices for determining which type of backup of a specific system to utilize.

File Representative backups (Go, S) are best for circumstances for private systems not supported by the above backup types, or for unique situations to include backup or healing flexibility. If the intent is to support instantaneous healing of high efficiency systems, replicas using file backup or VMWare backup may be needed.

WAN backups are supported with Image Agent over open WAN where bandwidth and latency requirements are met. File Representative and VM backups are only supported over private circuits (Private MAN/WAN). Image backups are recommended for SQL AGs where AG node uses just regional storage (no i, SCSI, FC, or CSV use by the node).

: Submit Agent Backups might be recommended for many DR circumstances where a standby Replica (Windows Representative Reproduction or VMWare Reproduction) would be needed to support large systems or high IO applications. Unitrends advises using File Agent backups for AD servers where more than 1 advertisement server is deployed in a domain or forest.

AD Admins need to likewise set up and recognize with Windows wbadmin system state backups that are necessary for some DR scenarios consisting of when it is essential to roll back AD without first restoring servers. (also uses to any kind of software application based RAID system). Submit Representative backup is required to access restored disk information granularly.