- Veeam Support Knowledge Base
- Veeam Cloud Connect - Compiling Provider/Tenant Logs for Support Cases
Veeam Cloud Connect - Compiling Provider/Tenant Logs for Support Cases
| KB ID: | 2096 |
| Product: |
Veeam Backup & Replication Veeam Cloud Connect |
| Version: | All |
| Published: | 2016-02-09 |
| Last Modified: | 2023-09-25 |
| Languages: | IT |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Purpose
Given the additional complexity of Cloud Connect compared with standalone installations of Backup & Replication, additional logging and information is needed to expedite cases with our Cloud Connect teams whenever feasible. All information should be obtained whether you are submitting an issue as a Veeam Cloud Connect Tenant or a Veeam Cloud Connect Provider .
Solution
Infrastructure Information
Include the following information:
- Provider Name:
- Tenant Name:
- Job Type that is having issues:
- Job Name that is having problems:
- Tenant Public IP:
*Please document the public IP of the Tenant Veeam Server connected to the cloud gateway. Having this information will help identify the connection in the Cloud Gateway logs. You can identify this by using a utility such as http://www.whatsmyip.org/
Tenant Logs
To ensure that the most relevant logs are present in the latest logs. Reproduce the error (if applicable), and then collect the tenant's Veeam Backup & Replication logs.
Collecting Logs from Tenant Environment
- For failing jobs:
Export logs for the job (backup, backup copy, or replication) that is having an issue.
- For restores and replica failovers:
Export a log bundle for the backup or replication job (as above) and manually collect logs from the following directories on the tenant's Veeam Backup server. (%ProgramData%\Veeam\Backup\)- Entire "CloudConnect" directory (if it exists)
- Entire directory with the name of the VM that was restored or replicated
Service Provider Logs
After reproducing the error (if applicable), collect and submit provider logs for the job using the instructions below:
Collecting Logs from Service Provider Environment
- For providers with newly-configured infrastructure, or a small number of clients, use the built-in log generator tool to gather logs from all managed servers related to the issue. It is crucial to collect logs from cloud gateways, repositories, and other relevant infrastructure in addition to the backup server.
- Providers with a significant number of tenants can use the built-in log collection tool but may find that it produces a large (multi-GB) log bundle. Alternatively, Provider logs may be manually collected; see the “Granular Provider Logs” section below.
Granular Provider Logs
This section lists specific logs and log locations that may be gathered manually as an alternate option to using the built-in log bundling tool.
Tip: It’s best to save the collected information in a .zip file with an identifiable name such as "<tenant_name>-ProviderLogs.zip"
Some listed files may not be present if they do not apply to your issue, but make sure you look at the correct server for each different directory or filename. Some files will have several rotations, with the oldest files archived to .zip or .gz.
Veeam Backup and Replication Server :
Collect these files in the root of %ProgramData%\Veeam\Backup\:
- Svc.VeeamBackup* (filenames beginning with “Svc.VeeamBackup”)
- Zip files named "<date stamp>_Svc.VeeamBackup"
- CloudAppliance*
- RTS.ResourcesUsage.log
- In rare cases, other files in this directory may be relevant, so including anything with a recent modified date is prudent.
Collect the contents of these folders :
- %ProgramData%\Veeam\Backup\Console\ (if using remote console, collect from that machine as well)
- %ProgramData%\Veeam\Backup\CloudConnect\
- %ProgramData%\Veeam\Backup\CloudConnectService\<tenant_name>\
- %ProgramData%\Veeam\Backup\CloudConnectService\ (excluding subfolders for other tenants)
- %programdata%\veeam\backup\Utils
- %programdata%\veeam\backup\ResourceScan
- %programdata%\veeam\backup\RegistryOptions
Cloud Gateway Servers :
- %ProgramData%\Veeam\Backup\Svc.VeeamGateSvc*
WAN Accelerator (if applicable ):
- %ProgramData%\Veeam\Backup\Svc.VeeamWANSvc*.log
Repository Servers (for backup and backup copy jobs) :
Check which server is listed as the Host for the Repository in the console (Backup Infrastructure > Backup Repositories).
Collect the entire content of these folders:
Windows Repostory:
- %ProgramData%\Veeam\Backup\CloudConnectService\<tenant_name>\
- %ProgramData%\Veeam\Backup\CloudConnectService\ (excluding subfolders for other tenants)
Linux Repository:
- /var/log/VeeamBackup/CloudConnectService_<tenant_name>_* (may be multiple directories)
More information
Related Articles
- How to Collect Logs for Veeam Backup & Replication
- How to Locate and Collect VSS/VIX Log Files From Guest OS
- Granular Log Collection Guide for SOBR Capacity/Archive Tier Issues
- How to Collect Logs for Veeam ONE
- How to Collect Logs for Veeam Management Pack for Microsoft System Center
- How to Collect Logs for Veeam Agent for Microsoft Windows
- How to Collect Logs for Veeam Plug-in for Microsoft SQL Server
- How to Collect Logs for Veeam Plug-in for SAP HANA
- How to Collect Logs for Veeam Plug-in for Oracle RMAN
- Veeam Cloud Connect - Compiling Provider/Tenant Logs for Support Cases
- Veeam Service Provider Console – Compile and Upload Server Logs
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.