Category: Backup & Replication
I faced with “Invalid remote certificate”: “Task Failed. Error: The remote certificate is invalid according to the validation process” on some my replication jobs between two our vCenter servers and Veeam BR couldn’t validate our target vCenter server certificate. I found a solution for resolving invalid remote certificate that I want to share it with you. Here is my environment specifications and the configuration. The log file locations maybe different with you environment: What Was “Invalid Remote Certificate” Issue? When vCenter server is adding to Veeam BR, its certificate’s thumbprint will be added to configuration database and if the vCenter server’s certificate was changed (Invalid remote certificate), you have to re-validate it in Backup Infrastructure. So if the certificate isn’t valid, you will see the below error: How Can Resolve It? Disable replication jobs & Veeam service First step, disable all your backup and replication jobs that they are related to the vCenter and also stop Veeam BR service because invalid remote certificate doesn’t allow you Re‑validate certificate via Backup Infrastructure As I said before, you have to re-validate the certificate, so you should go to “Backup Infrastructure” and select your server then right click on the server and click...
If you want to know, how much space is need for your backup on target site or local site and you are confused with backup concepts, add real values to this calculator and it will shows you an estimation: http://rps.dewin.me/
Veeam Backup & Replication is one of the best backup and replication software that you can use them in your virtual environment. Veeam BR be able to IP customization during disaster-recovery and you can have your virtual machines in a DR site with different IP plan. But Veeam BR just support Windows VMs for IP customization or “Re-IP Rule”. So what can we do about Linux virtual machines and others?
Veeam BR informing you about backup job and backup infrastructure performance when job is finished and you will see a window same as the below: Load: Source 54% > Proxy 27% > Network 47% > Target 33% Primary bottleneck: Source What does it mean? No matter what job you are running, and how you have the product deployed, there are 4 main data processing stages that data passes in the specific order (think data processing conveyor). These are Source > Proxy > Network > Target, and each processing stage has a load monitoring counter associated with it. “Source” is the source (production) storage disk reader component. The percent busy number for this component indicates percent of time that the source disk reader spent reading the data from the storage. For example, 99% busy means that the disk reader spent all of the time reading the data, because the following stages are always ready to accept more data for processing. This means that the source data retrieval speed is the bottleneck for the whole data processing conveyor. As opposed to that, 1% busy means that the source disk reader only spent 1% of time actually reading the data (and required data blocks...
If you want to use Veeam BR as you backup and recovery software in your virtual environment, you have to consider the below I/O table about your backup mode and choose best backup mode according to your backup infrastructure and your company backup policies: Backup Mode I/O Cost Incremental Backup 1x I/O on target (write for each changed block) Reversed Incremental Backup 3x I/O on target (write + read + write for each changed block) Active Full Backup 1x I/O on target (write for each block) Synthetic Full Backup For Incremental Backup Mode 2x I/O on target (read + write for each block) Synthetic Full Backup For Incremental Backup Mode With Transform 4x I/O on target (read + write + read + write for each block) Reversed Incremental will reduce your storage cost but increase I/O cost.
