Our Building private VSTS build agents using the Microsoft Packer Diaries

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

In this KB, we'll try to summarize that info into a single source to help much better communicate the best usage cases for each protection design. agentimage consists of: Performing VM-level backups (also called Host Based backups, or HOS) Carrying Out Conventional Representative File Backups using in-OS deployed agents (Also described as GOS backups), which may also include separate Database level backups Carrying out Image based backups utilizing in-guest released representatives (also referred to as block backups) As a basic rule, unless otherwise gotten rid of by supported configurations or recorded constraints, the following are loose best practices for determining which kind of backup of a specific system to utilize.

File Agent backups (Go, S) are best for circumstances for specific systems not supported by the above backup types, or for special situations to include backup or healing versatility. If the intent is to support immediate healing of high efficiency systems, reproductions utilizing file backup or VMWare backup may be required.

WAN backups are supported with Image Agent over open WAN where bandwidth and latency requirements are satisfied. File Agent and VM backups are just supported over personal circuits (Personal MAN/WAN). Image backups are suggested for SQL AGs where AG node uses just local storage (no i, SCSI, FC, or CSV usage by the node).

: File Representative Backups might be advised for many DR scenarios where a standby Reproduction (Windows Representative Reproduction or VMWare Replica) would be required to support large systems or high IO applications. Unitrends suggests using File Representative backups for advertisement servers where more than 1 advertisement server is deployed in a domain or forest.

Advertisement Admins need to likewise configure and recognize with Windows wbadmin system state backups that are essential for some DR situations including when it is necessary to roll back AD without first bring back servers. (likewise uses to any type of software based RAID system). File Agent backup is required to access restored disk data granularly.