DL4000 is running out of space on disk C while disk D is almost empty (4043801)

To resolve the issue please investigate if disk D is used for:
- swapfile pagefile.sys
- Core DVM deduplication cache
- other Core modules
- anything else useful

So, depending on what is D drive was used for, tasks should be processed accordingly. Here are couple of most common scenarios.

A. pagefile.sys is on D drive

To resolve the issue, please perform following steps:
- stop the Core service gracefully
- write down Quest Rapid Recovery services startup type (automatic, manual, delayed) and change them all to Disabled
- go to Control Panel, System, Advanced System Settings, Performance, Settings
- click on Advanced tab and then on Change under the Virtual Memory
- select all disks with swapfile, and select No paging file
- make sure that disk D is no longer used by anything
- open Disk Manager, select and delete volume D
- delete the extended partition that disk D was using (green rectangle)
- select C volume, right-click it and select Extend Volume
- use maximum space to extend the volume C
- reboot
- navigate back to the swapfile settings and enable it again on disk C by using System managed size
- change Rapid Recovery service startup type back to their original value and start the Core service

B. DVM deduplication files are relocated to D

- make sure that DVD dedupe cache is set on disk di by opening regedit, HKLM\Software\Apprecovery\Core\RepositoryService
- there are 3 registry values that may point to the disk D folders: CacheMetadataPath, PrimaryCachePath and SecondaryCachePath
- stop the Core service gracefully
- copy each folder's content back to their locations under C:\ProgramData\AppRecovery\RepositoryMetadata\ Subfolder names are: CacheMetadata, PrimaryCache and SecondaryCache
- modify each value in the registry so they are pointing to these folders on the C drive
- use highlighted steps from scenario A to delete disk D and extend disk C
- start the Core service back and make sure that it's started normally and mounts the repository without issues

It may also be necessary to double-check the whole branch of registry keys and values under HKLM\Software\AppRecovery\Core if there are any references to the paths on disk D