Restructured Documentation
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
---
|
||||
tags:
|
||||
- Veeam
|
||||
- Backup
|
||||
- Disaster Recovery
|
||||
---
|
||||
|
||||
## Purpose
|
||||
You may find that you need to adopt a device that was onboarded by a different Veeam Backup & Replication server. Maybe the old server died, or maybe you are restructuring your backup infrastructure, and want a new server taking over the backup responsibilities for the device.
|
||||
|
||||
If this happens, Veeam will complain that the device is managed by a different server. To circumvent this, perform the following changes in the Windows Registry based on the version of Veeam Backup & Replication you are currently using, then try to Update the Agent / Backup the agent again, and it should be successful after the registry changes are made.
|
||||
|
||||
**Reference Material**:
|
||||
https://forums.veeam.com/servers-workstations-f49/how-do-we-move-agent-to-associate-with-a-new-veeam-server-t79977.html
|
||||
|
||||
=== "VBR v11"
|
||||
|
||||
```text title="HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication"
|
||||
AgentDiscoveryIgnoreOwnership
|
||||
REG_DWORD (32-bit) Value: 1
|
||||
```
|
||||
|
||||
=== "VBR v12"
|
||||
|
||||
```text title="HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication"
|
||||
ProtectionGroupIgnoreOwnership
|
||||
REG_DWORD (32-bit) Value: 1
|
||||
```
|
||||
|
||||
## Related Documentation
|
||||
- [Related Backup and Recovery Documentation](<../../../reference/Backup and Recovery/index.md>) — Find the connected deployments, procedures, and references for this subject.
|
||||
+42
@@ -0,0 +1,42 @@
|
||||
---
|
||||
tags:
|
||||
- Veeam
|
||||
- Backup
|
||||
- Disaster Recovery
|
||||
---
|
||||
|
||||
## Purpose
|
||||
Repair the documented Veeam Cloud Connect certificate failure when a backup reports that no cloud gateways are available because gateway certificates cannot be validated.
|
||||
|
||||
### Symptoms
|
||||
When you try to run a backup to a remote backup server, the backup job fails and gives the following error:
|
||||
|
||||
!!! failure "Error: No cloud gateways are available: failed to validate certificates of some gateways"
|
||||
|
||||
### Reason
|
||||
This means that the SSL certificate installed on the Veeam Backup & Replication Server being used by the endpoint is expired. While you can update the `Web UI` and `Server` SSL certificates, the "**Gateway Connect**" certificate is different. When the certificate is expired, the backup agent stops trusting the backup server and fails all backup jobs to that server until the certificate is updated.
|
||||
|
||||
### Resolution Steps
|
||||
You need to remotely log into the Veeam Backup & Replication server, doing this via RMM tools, RDP, etc. Once logged-in, you need to open Veeam Backup & Replication and login.
|
||||
|
||||
- At the bottom-left sidebar of Veeam Backup & Replication window, you will see tabs such as `Home`, `Inventory`, `Backup Infrastructure`, `Storage Infrastructure`, `Tape Infrastructure`, and `Cloud Connect`. Proceed to click on the "**Cloud Connect**" tab in the sidebar.
|
||||
- Click on the "**Manage Certificates**" button
|
||||
- Click on the "**Select an existing certificate from the certificate store**" radio button
|
||||
- You will be prompted that "*This certificate is used by one or more Cloud Gateways*", simply click on "**Yes**" to proceed.
|
||||
- Look for the current and up-to-date / valid certificate from the certificate list then click "**Next**"
|
||||
- e.g. `*.bunny-lab.io`
|
||||
- You will be given a summary of the changes > Click the "**Finish**" button to finish updating the gateway's certificate.
|
||||
|
||||
### Re-Attempt Backup
|
||||
At this point, the endpoint should immediately trust the new certificate from the remote backup server (assuming the server is `Managed` and not `Standalone`). The backups should be running successfully the next time you run them.
|
||||
|
||||
!!! info "Standalone Mode"
|
||||
In the event that the device is in-fact standalone, you can run the following command on the device via commandline to tell it to immediately sync the configuration settings of the remote backup server with the local backup agent:
|
||||
|
||||
```batch
|
||||
::Connect to the backup server and download current configuration settings.
|
||||
"C:\Program Files\Veeam\Endpoint Backup\Veeam.Agent.Configurator.exe" -syncnow
|
||||
```
|
||||
|
||||
## Related Documentation
|
||||
- [Related Backup and Recovery Documentation](<../../../reference/Backup and Recovery/index.md>) — Find the connected deployments, procedures, and references for this subject.
|
||||
@@ -0,0 +1,36 @@
|
||||
---
|
||||
tags:
|
||||
- Veeam
|
||||
- Backup
|
||||
- Disaster Recovery
|
||||
---
|
||||
|
||||
## Purpose
|
||||
There may come a time that you need to free up space in a Veeam Backup & Replication backup repository because you are running out of space. In these cases, you need to manually trim the older backups in a specific way to ensure this is non-destructive.
|
||||
|
||||
## Manual Removal of Backup Data
|
||||
You need to perform these steps to carefully delete the oldest full backup chain w/ incrementals.
|
||||
|
||||
- Log into the Veeam Backup & Replication server and locate the local folder hosting the backup repository that is running out of space
|
||||
- Locate the oldest "**Full**" backup and delete it along with all of the "**incremental**" backups after it leading to the second-most-recent full backup.
|
||||
|
||||
!!! warning "Incremental Backups Affecting the Chain"
|
||||
Be mindful that if you delete the incremental backups but not the full backup associated with those incrementals you will break the backup chain. In the event this happens, either un-delete the incrementals and try again, or go one-level-deeper and delete the second-oldest full backup and all incrementals to correct the chain's structure.
|
||||
|
||||
## Rescan Backup Repository
|
||||
At this point, you can just re-scan the backup repository within Veeam so the Veeam database gets updated to notice the missing backup files that you just deleted. [Rescanning Backup Repositories](https://helpcenter.veeam.com/docs/backup/vsphere/rescanning_backup_repositories.html?ver=120)
|
||||
|
||||
- Launch Veeam Backup & Replication Console
|
||||
- Navigate to "**Backup Infrastructure > Backup Repositories**"
|
||||
- Locate the backup repository you deleted backup files from, then "**Right-click > Rescan**"
|
||||
|
||||
## Removing Restore Points from Database
|
||||
At this point, you have deleted the backup files and re-scanned the backup repository(s) to ensure that Veeam updated its database to notice the now-missing backup files. Now you need to tell Veeam to "forget" about the older backups you deleted so they are no longer displayed within Veeam itself. [Removing Missing Restore Points](https://helpcenter.veeam.com/docs/backup/vsphere/remove_missing_point.html?ver=120)
|
||||
|
||||
- Navigate to "**Home > Backups > Disk**"
|
||||
- Locate the backup job associated with the device's backup files you deleted
|
||||
- Right-click the associated backup job > "**Properties...**"
|
||||
- In the Backup Properties window, right-click the missing restore point(s) and click "**Forget**" > "**All Unavailable Backups**"
|
||||
|
||||
## Related Documentation
|
||||
- [Related Backup and Recovery Documentation](<../../../reference/Backup and Recovery/index.md>) — Find the connected deployments, procedures, and references for this subject.
|
||||
@@ -0,0 +1,21 @@
|
||||
---
|
||||
tags:
|
||||
- Veeam
|
||||
- Backup
|
||||
- Disaster Recovery
|
||||
---
|
||||
|
||||
## Purpose
|
||||
If you find that you need to migrate cloud backups that are being sent to a server running the Veeam VSCP due to issues like exhausted storage space on existing repositories.
|
||||
|
||||
### Migrate Backup Repository Data
|
||||
- Log into VSPC website and disable all associated jobs that need to be migrated
|
||||
- Log into the endpoint (or veeam backup proxy running at the client location, if there is one) and disable the associated job that we need to migrate the data for.
|
||||
- Navigate to the directory structure where the backup is located on-disk, such as `E:\Backups\clientname` and move it to the destination backup repository, such as `F:\Backups\clientname`
|
||||
- Log back into Veeam Backup & Replication Console and re-scan the new repositories
|
||||
|
||||
### Move Backup Job Location in VSPC Portal
|
||||
At this point, we need to migrate point the backup job(s) that were affected to the new location. This is a job-level change, not company-level change.
|
||||
|
||||
## Related Documentation
|
||||
- [Related Backup and Recovery Documentation](<../../../reference/Backup and Recovery/index.md>) — Find the connected deployments, procedures, and references for this subject.
|
||||
Reference in New Issue
Block a user