Download Altaro Offsite Backup

Bandwidth Throttling for Offsite Backups / Replication If you're taking offsite backups over the WAN / VPN / Fiber connections or even running Replication and especially going over a slow connection, you might be looking to throttle the bandwidth available for the offsite backups via VM Backup.VM Backup does not offer throttling natively as it stands, but fortunately Windows gives you the functionality to do this built-in.Version 9All you have to do is open PowerShell and run the following command on the VM Backup machine and ALL Hyper-V Hosts:Syntax for Offsite Backups going to an Offsite Backup Server:New-NetQosPolicy "OBS Throttle" -IPDstPortStartMatchCondition 36000-IPDstPortEndMatchCondition 36001 -ThrottleRateActionBitsPerSecond 10000000Syntax for Offsite Backups going to a Cloud Backup Location:New-NetQosPolicy "Cloud Backup Throttle Port 80" -IPPort 80 -IPProtocol TCP -ThrottleRateActionBitsPerSecond 10000000 -AppPathNameMatchCondition 'C:\Program Files\Hornetsecurity\VMBackup\VMBackup.SubAgent.exe'New-NetQosPolicy "Cloud Backup Throttle Port 443" -IPPort 443 -IPProtocol TCP -ThrottleRateActionBitsPerSecond 10000000 -AppPathNameMatchCondition 'C:\Program Files\Hornetsecurity\VMBackup\VMBackup.SubAgent.exe'Syntax for Replication:New-NetQosPolicy "OBS Replication Throttle" -IPDstPortMatchCondition 36100 -ThrottleRateActionBitsPerSecond 10000000The ThrottleRateActionBitsPerSecond must be specified in bits. So for instance;3 Mbps = 3000000 Bits10 Mbps = 10000000 BitsNote:For VMware hosts, this only needs to be applied on the machine running VM BackupIf you wish to remove the QoS Policies, you can run the following commands:Remove-NetQosPolicy -Name "OBS Throttle"Remove-NetQosPolicy -Name "Cloud Backup Throttle Port 80"Remove-NetQosPolicy -Name "Cloud Backup Throttle Port 443"Remove-NetQosPolicy -Name "OBS Replication Throttle"Version 8All you have to do is open PowerShell and run the following command on the VM Backup machine and ALL Hyper-V Hosts:Syntax for Offsite Backups going to an Altaro Offsite Server:New-NetQosPolicy "AOS Throttle" -IPDstPortStartMatchCondition 35116 -IPDstPortEndMatchCondition 35117 -ThrottleRateActionBitsPerSecond 10000000Syntax for Offsite Backups going to a Cloud Backup Location:New-NetQosPolicy "Cloud Backup Throttle Port 80" -IPPort 80 -IPProtocol TCP -ThrottleRateActionBitsPerSecond 10000000 -AppPathNameMatchCondition 'C:\Program Files\Altaro\Altaro Backup\Altaro.Services.BackupAgent.exe'New-NetQosPolicy "Cloud Backup Throttle Port 443" -IPPort 443 -IPProtocol TCP -ThrottleRateActionBitsPerSecond 10000000 -AppPathNameMatchCondition 'C:\Program Files\Altaro\Altaro Backup\Altaro.Services.BackupAgent.exe'Syntax for Replication:New-NetQosPolicy "AOS Replication Throttle" -IPDstPortMatchCondition 35120 -ThrottleRateActionBitsPerSecond

Hola a tod@sEn esta oportunidad continuaremos viendo el software Altaro VM Backup y profundizando en las diferentes opciones que nos ofrece. En este post veremos en concreto como poder integrar Altaro VM Backup con Wasabi Hot Cloud Storage.Al integrar Wasabi nos permitirá almacenar nuestras copias de seguridad en una ubicación externa, lo que es ideal para fines de recuperación ante desastres. Además todas las copias de seguridad están cifradas (AES de 256 bits) de forma nativa.Prerrequisitos:Asegúrese de estar ejecutando Altaro VM Backup versión 8.5 o posterior para hacer uso de esta funciónDebes ejecutar Unlimited Plus Edition para poder acceder a esta función.Notas importantes:Cada instalación de Altaro VM Backup debe hacer uso de un Wasabi Bucket diferente.Wasabi Compliance Mode no es compatible (ya que los derechos de eliminación se limitarían solo a Wasabi).Integrar Wasabi con Altaro VM BackupPara comenzar, abrimos la consola de Altaro VM Backup.Ya en la consola, vamos a la pestaña “Backup Locations” y acto seguido pulsamos sobre “Add Offsite Location” como se muestra en la imagen.Dentro de las opciones disponibles, seleccionamos “Wasabi“.Agregamos los datos de nuestra conexión con Wasabi. Tenemos que agregar el nombre exacto de como nombramos nuestro bucket en Wasabi para evitar errores, probamos la conexión para verificar el correcto funcionamiento.Dentro de lista de máquinas virtuales disponibles en nuestra infraestructura, tomamos la(s) máquina(s) virtual(es) y la(s) arrastramos hasta “Offsite Locations“. Ya seleccionada la maquina(s) virtual(es), vamos a la parte inferior derecha de la consola y pulsamos sobre “save changes” para finalizar y guardar los cambios.Altaro VM Backup nos pedirá crear una contraseña maestra para encriptar nuestras copias de seguridad fuera del sitio.En mi caso en esta ventana, selecciono la máquina virtual que configure en “Offsite Locations” y pulso sobre “Take Offsite Copy” para comenzar el respaldo. Como podrán notar, no es posible seleccionar las demás máquinas virtuales ya que no se agregaron en pasos anteriores.En la ventana de Dashboard, podremos ver el avance de nuestra tarea de respaldo a Wasabi.Verificar respaldo en WasabiIngresamos a página de Wasabi con nuestras credenciales.Dentro de la pestaña “Buckets” vamos al bucket que configuramos en Altaro VM Backup e ingresamos en este.Ya en el bucket, podremos navegar dentro de este y ver que Altaro VM Backup creo varios archivos dentro del bucket.Con estos simples pasos podemos integrar Wasabi con nuestra solución de respaldo Altaro VM Backup y poder almacenar nuestros respaldos en la nube y así también poder cumplir con la regla de 3-2-1. Espero que esta información pueda ser de ayuda y cualquier duda, consulta o sugerencia la dejan en los comentarios. Saludos.

Do is put a check in the Application Consistent column for each virtual Domain Controller. You find these settings under VSS Settings in Altaro VM Backup. Tip! Check the VMware ToolsTo offer the best integration between the virtualization host and guests, VMware offers VMware Tools. Similarly, Hyper-V offers Integration Components (ICs). Hyper-V’s ICs come with the Windows Server Operating System (OS) and are automatically kept up to date through Windows Update. VMware Tools, however, need to be installed inside the virtual guest and require somewhat more effort to keep up to date.It is easy to forget to install the VMware Tools on virtual Domain Controllers. It is easy to not have the latest VMware Tools on virtual Domain Controllers. Don’t make these mistakes, as application consistent backups rely on them. Tip! Check the VSS writersWhen you create a backup of Domain Controllers using the relevant VSS writers, an event is logged in the Event log. This event has event ID 1917 with source ActiveDirectory_DomainService and is recorded in the Directory Services event log (underneath Application and Services logs).When Active Directory-aware backups do not occur, you can check the relevant VSS writers for errors:The NTDS VSS writer should report no errorsThe DFS Replication VSS writer should report no errorsBoth writers can be checked with the following line of code in an elevated Command Prompt (cmd.exe) window on a (virtual) Domain Controller:vssadmin list writersThe output of the command lists all the VSS writers on the system. The relevant VSS writers are among them. Tip! Backup to a location outside of the reach of Active DirectoryOne of the other mistakes I see admins make is to write all domain controller backups to a (networking) location that is governed by access control lists (ACLs), filled with Active Directory principals. When Active Directory is unavailable, that location is unavailable, because you gained access to it through one or more Active Directory group memberships. Make sure you create backups of Domain Controllers in locations, whose access is not governed by Active Directory or IPSec. Then, make use of the Offsite Copies functionality in Altaro VM Backup