The best part of the new Veeam Standalone Console is the fact that Veeam PowerShell snap-in installs as part of this component, and it includes a new cmd-let: Connect-VBRServer. YES! No more PowerShell remoting to invoke your Veeam PowerShell scripts.
When you have to deal with a large environment and several jobs in Veeam, automation via powershell is the only possible solution.
In powershell, in order to use credentials to authenticate against different systems you have different options. When running scripts interactively, we can configure the powershell command to ask us for username and password, but saving passwords in clear text into a script is a bad security practice. Powershell however has a way to hide passwords in commands and scripts.
When you upgrade Veeam Backup & Replication to V8, you have available the new Forward forever-incremental mode for your backups. This is the default method for all newly created jobs, but the already existing backup jobs are not changed, because we do not want to change the user experience or create issues to I/O profiles, backup windows and such.
This great powershell script will take all your existing forward incremental backup jobs and reconfigure them to use the new forward forever-incremental mode.
In a Veeam Backup & Replication environment with a high number of jobs, being sure the configured settings are all the same can be a tough task. Even if there are defined procedures to create new jobs, and every IT admin has these procedures, an error can always happen.
If you have few jobs to check, you can think about opening all of them one by one anche verify this parameter, but as the number of jobs grows, these checks becomes nearly impossible.
A nice solution is to leverage the complete Powershell support offered by Veeam Backup & Replication.
In un ambiente Veeam Backup & Replication che presenta un numero elevato di job, garantire che le loro configurazioni siano omogenee può essere talvolta complicato. Sebbene vengano definite delle procedure di creazione dei vari job e assegnate al personale che gestisce il prodotto, l’errore umano è sempre dietro l’angolo. Prendiamo un esempio. Si utilizzano una […]
As in many datacenters, we use monitoring software to control many parameters of our infrastructure. Thanks to CIM, is it possible to use directly these APIs to monitor hardware and health status of the ESXi servers, rather than using script and agents to accomplish the same results. Nagios has some cool plugins to use CIM […]
Come in molti datacenter, utilizziamo software di monitoraggio per controllare i numerosi parametri della nostra infrastruttura. Grazie a CIM, è possibile usare direttamente queste APIs per monitorare l’hardware e lo stato di salute dei server ESXi, piuttosto che usare script e agent. Nagios possiede alcuni ottimi plugin per usare CIM e monitorare ESXi, ma il problema […]