Issue has been reported to happen after upgrading a client to NetVault 12.2 and suddenly after several successful job instances on version 12.4. On both cases, the job hung after identifying the NetVault Client as seen below and never progresses past that point (check timestamp). Only way to stop backup is to abort the job:
Binary log extract:
| Job Message | 2019/06/04 09:26:03 210 | Data Plugin | NV-Client | File System 12.2.0.8 Backup |
| Information | 2019/06/04 09:26:03 210 | Data Plugin | NV-Client | Current host : Windows 6.1 (build 7601), service pack 1.0 |
| Information | 2019/06/04 09:26:03 210 | Data Plugin | NV-Client | Current host : Terminal Services is installed |
| Information | 2019/06/04 09:26:03 210 | Data Plugin | NV-Client | Current host : The system is a server |
| Job Message | 2019/06/04 09:26:03 210 | Data Plugin | NV-Client | Adding System State System Files to selected files |
| Error | 2019/06/04 10:36:51 210 | Jobs | NV-Server | Fatal error: Aborted by user |
Also, trace log file nvfs-YYYYMMDDhhmmss-xxx.log includes the following entry:
Message 'CMGR_PROCESS_UNREACHABLE_MSG' not handled at depth 0
'Netvault-VSS-Provider' is used instead of 'Microsoft Software Shadow Copy provider 1.0'
Reinstalling NetVault Client nor forcing NetVault to use “Microsoft Software Shadow Copy provider 1.0” on vss.cfg have any effect on the job outcome.
To solve the problem, remove 'Netvault-VSS-Provider' using the instructions below:
1. Checking VSS providers with command “vssadmin list providers”. NetVault VSS provider should be listed similar as seen below:
Provider name: 'Netvault-VSS-Provider'
Provider type : Matériel
Provider ID : {38016df0-b1d4-4d7d-bb1a-93d6f72d72cf}
Version : 0.16.0
2. Open Windows Registry using Regedit
Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\
Expand Providers and you should see three keys: Enum, and two GUID’s (long strings of letters and numbers).
Click on the GUID on the list on the left and in the right-hand pane the default string value is the name of the provider.
3. Find the GUID for "Netvault-VSS-Provider"
4. Export the whole GUID, so that the operation can be reverted if needed.
5. Delete "Netvault-VSS-Provider" GUID subkey. Close the registry.
6. Open Windows services and restart the “Volume Shadow Copy” service.
7. Re-run "vssadmin list providers" to verify that the provider is gone.
If for some reason the process needs to be reverted to the initial state, import the previously exported registry sub-key and bounce the Volume Shadow Copy service.
