https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNTE0IiwiaGFzaCI6ImUxNzhlMzBiLTZmMTItNDk3OC1iYjhjLTQ5OGE2MmM4YWMwYyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam Backup Proxy server becomes unresponsive

Challenge

The Veeam Backup server or the Backup Proxy server becomes completely unresponsive when disks of a backed up virtual machine are being hot-added to the server.

Cause

If CTK parameters are enabled on the Veeam Backup server or on the Backup Proxy server, the Virtual Appliance mode cannot be used to back up machines with large disks.

Solution

Power off the Veeam Backup server or the backup proxy server and set all CTK parameters to "false" as per the following KB:

http://www.veeam.com/KB1113

If you back up or replicate Veeam components, edit properties of a corresponding job: open the Advanced Settings dialog box and disable the Use changed block tracking data (recommended) option on the vSphere tab, so that the CTK parameters are not set to "true" during the next job run.

KB ID:
1514
Product:
Veeam Backup & Replication
Version:
6.x
Published:
2012-02-06
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.