Image_SYSVOL files not cleaned up

After the server has exceeded the soft quota the system cleans up the Image_C files during the next cleanup window. There are two issues I am having.

  1. he first is that the corresponding Image_SYSVOL are not cleaned up and left behind.
  2. The other issue is I have the server set to have a minimum of 6 incremental image backups and 2 full image backups, but after the cleanup it only left 4 incremental images after deleting 6 instead of 4 of the old ones.

I think number 2 happened because I asked for a minimum of 2 full image backups and there are 4 incremental img for each full and it just so happened to have a full for the last image backup. This caused it to delete the older full image backup and all of the incrementals that were created against it. If this is the case I guess I figured since it is called minimum allowed that it would have kept the 3rd full image backup to that the minimum incrementals could be met.

Is there any insight or something I can do to help track down the issues?

You are right and I have noticed that too, quite recently. I will fix it asap. Testing the changes might take a while.

The SYSVOL image should be cleaned up via remove_unknown.

I stopped the server and ran “start_urbackup_server --remove_unknown”
The SYSVOL are not removed

here is an example of the file list for one client
Image_C_150821-1805.vhdz*
Image_C_150821-1805.vhdz.hash*
Image_C_150821-1805.vhdz.mbr*
Image_C_150828-1809.vhdz*
Image_C_150828-1809.vhdz.hash*
Image_C_150828-1809.vhdz.mbr*
Image_C_150904-1810.vhdz*
Image_C_150904-1810.vhdz.hash*
Image_C_150904-1810.vhdz.mbr*
Image_C_150911-1812.vhdz*
Image_C_150911-1812.vhdz.hash*
Image_C_150911-1812.vhdz.mbr*
Image_C_150918-1814.vhdz*
Image_C_150918-1814.vhdz.hash*
Image_C_150918-1814.vhdz.mbr*
Image_C_150921-0129.vhdz*
Image_C_150921-0129.vhdz.hash*
Image_C_150921-0129.vhdz.mbr*
Image_C_150928-0130.vhdz*
Image_C_150928-0130.vhdz.hash*
Image_C_150928-0130.vhdz.mbr*
Image_C_151005-0133.vhdz*
Image_C_151005-0133.vhdz.hash*
Image_C_151005-0133.vhdz.mbr*
Image_C_151012-0137.vhdz*
Image_C_151012-0137.vhdz.hash*
Image_C_151012-0137.vhdz.mbr*
Image_C_151014-1130.vhdz*
Image_C_151014-1130.vhdz.hash*
Image_C_151014-1130.vhdz.mbr*
Image_SYSVOL_150729-1617.vhdz*
Image_SYSVOL_150729-1617.vhdz.hash*
Image_SYSVOL_150729-1617.vhdz.mbr*
Image_SYSVOL_150805-1622.vhdz*
Image_SYSVOL_150805-1622.vhdz.hash*
Image_SYSVOL_150805-1622.vhdz.mbr*
Image_SYSVOL_150812-1623.vhdz*
Image_SYSVOL_150812-1623.vhdz.hash*
Image_SYSVOL_150812-1623.vhdz.mbr*
Image_SYSVOL_150819-1625.vhdz*
Image_SYSVOL_150819-1625.vhdz.hash*
Image_SYSVOL_150819-1625.vhdz.mbr*
Image_SYSVOL_150821-1804.vhdz*
Image_SYSVOL_150821-1804.vhdz.hash*
Image_SYSVOL_150821-1804.vhdz.mbr*
Image_SYSVOL_150828-1808.vhdz*
Image_SYSVOL_150828-1808.vhdz.hash*
Image_SYSVOL_150828-1808.vhdz.mbr*
Image_SYSVOL_150904-1809.vhdz*
Image_SYSVOL_150904-1809.vhdz.hash*
Image_SYSVOL_150904-1809.vhdz.mbr*
Image_SYSVOL_150911-1812.vhdz*
Image_SYSVOL_150911-1812.vhdz.hash*
Image_SYSVOL_150911-1812.vhdz.mbr*
Image_SYSVOL_150918-1813.vhdz*
Image_SYSVOL_150918-1813.vhdz.hash*
Image_SYSVOL_150918-1813.vhdz.mbr*
Image_SYSVOL_150921-0129.vhdz*
Image_SYSVOL_150921-0129.vhdz.hash*
Image_SYSVOL_150921-0129.vhdz.mbr*
Image_SYSVOL_150928-0130.vhdz*
Image_SYSVOL_150928-0130.vhdz.hash*
Image_SYSVOL_150928-0130.vhdz.mbr*
Image_SYSVOL_151005-0132.vhdz*
Image_SYSVOL_151005-0132.vhdz.hash*
Image_SYSVOL_151005-0132.vhdz.mbr*
Image_SYSVOL_151012-0137.vhdz*
Image_SYSVOL_151012-0137.vhdz.hash*
Image_SYSVOL_151012-0137.vhdz.mbr*
Image_SYSVOL_151014-1129.vhdz*
Image_SYSVOL_151014-1129.vhdz.hash*
Image_SYSVOL_151014-1129.vhdz.mbr*

Ok, thanks for trying. I have added that to the cleanup procedure now as well.

Sorry to perform thread necromancy but I think this issue is back, at least for me. Running the latest versions and it’s not cleaning up the old sysvol items.

Is it all of them or only the once in connection with unfinished image backups?

remove_unknown should clean them up in any case.

It’s actually all of them. Got them set to run every 7 days and I see a SYSVOL for every 7 days going all the way back to early March.