Last week, I explained how to manually connect standalone computers to Veeam Availability Console. This time we will try to automate this process as much as possible.
Veeam Availability Console has been designed for multiple use cases, and one of them is to manage large fleets of computers. But what about those standalone machines we have lying around? It could be the last physical server we have in the datacenter, or a laptop of a consultant that is always travelling around. How can we deal with those? I involved my family’s computers to find out.
Veeam Agent for Windows 2.0 is today available as a public beta, and it’s soon to be officially released. One of the most awaited features is for sure the possibility to send backups over the Internet to Veeam Cloud Connect, and the feedback we’ve seen during the public beta period has been great so far. There’s actually however one limit in v2: users can only choose one destination for their backups. So, if you want to consume Cloud Connect, this is going to be your only traget and you will have no local backups, and viceversa. Two different policies cannot be configured in the interface, but this doesn’t mean it cannot be done!
Veeam Agents, both for Windows and for Linux, have the possibility to send backups to a Veeam Backup & Replication server. This is a great feature, but sometimes customers don’t even have anymore any virtualized workload to protect, so they find a hard time to justify the deployment of Veeam Backup & Replication to only protect physical workloads. There’s a solution to this however, and it doesn’t cost anything to users.
Può capitare di avere installato nei server ESX degli agenti di terze parti: sistemi di monitoraggio, controllo remoto, backup centralizzati… Se vi trovate in questa situazione e dovete aggiornare ESX 4.0 col nuovo Update 1, assicuratevi di aver letto bene l’articolo KB1016070, dove vi verrà spiegato come dovrete agire. L’alternativa…