In Enterprise Vault 8.0, quiescing and unquiescing is done at the component level.
See About granular quiescence.
In Enterprise Vault 7.5, the mechanism to quiesce and unquiesce is performed at the Enterprise Vault server level through the following Enterprise Vault registry keys:
The following lists provide a high-level overview of how to quiesce or unquiesce the Enterprise Vault services.
To quiesce the Enterprise Vault services, stop the Enterprise Vault services, create the special Enterprise Vault registry keys, and restart the services. Make sure that you create the Enterprise Vault registry keys with a value of zero.
To unquiesce the Enterprise Vault services, stop the Enterprise Vault services, delete the special Enterprise Vault registry keys, and restart the services.
Multiple quiescent and unquiescent jobs can run on the same Enterprise Vault server. Therefore, NetBackup uses a registry counter (NBU_EV_QSE_LEVEL) to track the number of times the Enterprise Vault services are put into read-only mode. If the value of this counter is zero, the Enterprise Vault services are running in a read-write mode. If value of this counter is non-zero, then the Enterprise Vault services are running in a read-only mode.
The location of this registry counter is one of the following addresses:
The following lists explain how quiesced and unquiesced jobs affect the state of the NetBackup reference counter, special Enterprise Vault registry keys, and Enterprise Vault services. (The NetBackup reference counter is a registry key at the location, NBU_EV_QSE_LEVEL.)
When a quiesced job begins with the Enterprise Vault services in down state, one of the following occurs:
If the special Enterprise Vault registry keys are not present, they are created to ensure that Enterprise Vault services start in a read-only mode. In addition, the NetBackup reference counter is set to one in the registry key.
If the special Enterprise Vault registry keys are present, the job increments the NetBackup reference counter by one in the registry key.
The following occurs with the quiesced jobs that have Enterprise Vault services in an up state and the special registry keys are not present: (Enterprise Vault is in a read-write mode.)
The following occurs with the quiesced jobs that have Enterprise Vault services in an up state and the special registry keys are present: (Enterprise Vault is in a read-only mode.)
The following occurs when an unquiesced job begins with the Enterprise Vault services in a down state and the NetBackup reference counter is 1:
The following occurs when an unquiesced job begins with the Enterprise Vault services in an up state and the NetBackup reference counter is 1:
The following occurs when an unquiesced job begins with the Enterprise Vault services up and the NetBackup reference counter is greater than 1:
If jobs fail during a policy execution, or the Enterprise Vault archive jobs do not work after the policy execution, perform the following steps sequentially:
Verify that the value of NetBackup reference counter is set to zero. If it is left as a non-zero value, then the subsequent quiesce jobs may not work as expected. You may have to manually set this value to zero.
Verify that there are no special Enterprise Vault registry keys present. If any special Enterprise Vault registry keys are present, the Enterprise Vault services are in a read-only mode. You must manually restart the Enterprise Vault services in a read-write mode.
To manually restart the Enterprise Vault services in read-write mode:
Set the value of the NetBackup registry counter (NBU_EV_QSE_LEVEL) to 1.
bpresolver.exe unquiescence -v -c <EV Server> -pt 39 -S <NetBackup Master Server> EV_SERVER
The EV Server variable is the host name of the Enterprise Vault server where you must restart the Enterprise Vault services in a read-write mode.
If the NetBackup unquiescence job is not able to start Enterprise Vault in read-write mode, then you must unquiesce the Enterprise Vault services. To unquiesce the Enterprise Vault services, stop the Enterprise Vault services, delete the special Enterprise Vault registry keys, and restart the services.
Verify that no special Enterprise Vault registry key is present. If none are present and some Enterprise Vault services are in a down state, you must manually start those services.