Changing timeout and logging values for vSphere

This topic applies to NetBackup for VMware.

Table: DWORD keys and defaults for vSphere timeouts lists the vSphere keys and their default values for various timeouts. These values can be changed on the backup host (see the procedure in this topic).

Table: DWORD keys and defaults for vSphere timeouts

The key and default for the vSphere API logging level are the following.

Table: DWORD key and default for vSphere API log level

DWORD key name	Default value
vmcloglevel	0 (no logging)

Changes to the vSphere API logging level affect the following logs on the backup host:

The logs are in the following location on the backup host:

Windows: install_path\NetBackup\logs\

Linux: /usr/openv/netbackup/logs

To change vSphere timeouts and logging values on Windows

On the Windows desktop of the backup host, click Start > Run and enter regedit.
To be on the safe side, make a backup of the current registry (File > Export).
Go to HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion > CONFIG and create a key that is called BACKUP.
To change a timeout value, create a new DWORD under BACKUP, using the appropriate registry name (such as jobtimeout or poweroptimeout).
Enter a value for the timeout.
To change the level of vSphere API logging, create a new DWORD called vmcloglevel and enter the new logging value.
The allowed values are 0 through 6, where 0 is no logging and 6 is the highest log level.

To change vSphere timeouts and logging values on Linux

On the Linux backup host, create (or open) the following file:
/usr/openv/netbackup/virtualization.conf
To change a timeout value, enter a new dword line under [BACKUP], using the appropriate name (such as jobtimeout or poweroptimeout). Include a value for the timeout.
For example:
```
[BACKUP]
"jobtimeout"=dword:60
```
This example sets the job timeout to 60 seconds.
Note: If the file already contains a [BACKUP] line, do not add another [BACKUP] line. Any other lines that already exist under [BACKUP] should remain as they are.
To change the level of vSphere API logging, enter a dword line for vmcloglevel with a logging value, under [BACKUP]. For example:
```
"vmcloglevel"=dword:6
```
The allowed values are 0 through 6, where 0 is no logging and 6 is the highest log level.

More Information