Views:

Summary

After updating a Windows client from DPX 4.X.X to 4.7.X using autoupdate, there's no reboot request by DPX, even if needed in certain cases. 

Symptoms

The next backup after updating the node without rebooting will result in the following error:

172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP6339J 3192: Node [WIN-2012-xxx] Volume [X:\] used space [118060] KB of total space [125695996] KB
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3072J 3192: Size (in bytes) of volume special ID for volume: X:\ is: 24.
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3069E 3192: Failed to start the journaling for vol(\\?\Volume{ba8aac53-a6c0-4151-81e2-c818cc04c067}\) genrc(0xfffff35e) osrc(0xc0000021d) rc(0xfffff35e : The journaling system is not in a stable state)
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3069E 3192: HotSpotSnapShot::do_pre_snapshot_settings:enable_cj failed vol(\\?\Volume{ba8aac53-a6c0-4151-81e2-c818cc04c067}\) rc(-1)
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP6200E 3192: Failed to perform the pre snapshot setting for volume(X:\); rc (-1)
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3069E 3192: MsSnapShot::add_physical_disks_to_backup:add_to_snapshot_set error(\\?\Volume{ba8aac53-a6c0-4151-81e2-c818cc04c067}\) (23075)
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3069E 3192: MsSnapShot::backup_components:add_physical_disks RC(-1)
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3069E 3192: BACKUP::backup_components failed rc(-3)
172.20.XX.XX sssnap Tue Aug 31 01:57:11 2021 SNBSNP3069E 3192: Failed to backup the applications / disk ( RC(-16)

Resolution

Reboot the node and restart the backup.

Keywords: update, gpt, dynamic disks, dpx autoupdate, client, node