ERROR: not enough space for snapshot
Getting an error and backup doesn't complete. It's not enough space where snapshot is stored. I have a 512 SSD configured as C:(390GB free) and D:recovery(27MB free). I presume it's the D: causing the issue, any work arounds? If not I will just delete D: info since I have the OEM drive yet thx


- Log in to post comments

Sorry for the paste but couldn't attach files
10/18/2019 12:32:56 AM: -----
10/18/2019 12:32:56 AM: ATI Demon started. Version: 23.5.1.17750.
10/18/2019 12:32:56 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/18/2019 12:32:56 AM: Operation HP-VW-DOCTOR started by schedule.
10/18/2019 12:32:57 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/18/2019 12:32:57 AM: Operation: Backup
10/18/2019 12:32:57 AM: Priority changed to Low.
10/18/2019 12:32:59 AM: Create Backup Archive From: To file: nas://WDMYCLOUD/Larry/Backup/HP Pavlon/HP-VW-DOCTOR.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Larry\AppData\Local\Temp, C:\Users\Larry\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Larry\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Larry\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Larry\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Larry\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Larry\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC
10/18/2019 12:32:59 AM: Pending operation 173 started: 'Creating partition image'.
10/18/2019 12:33:00 AM: Writing full version to file: HP-VW-DOCTOR_full_b1_s1_v1.tib
10/18/2019 12:33:47 AM: Pending operation 173 started: 'Creating partition image'.
10/18/2019 12:33:58 AM: Pending operation 173 started: 'Creating partition image'.
10/18/2019 2:05:23 AM: Pending operation 173 started: 'Creating partition image'.
10/18/2019 2:06:58 AM: Pending operation 173 started: 'Creating partition image'.
10/18/2019 2:07:04 AM: Error 0x101f6: Unable to create volume snapshot
10/18/2019 2:07:10 AM: Error 0x13c0005: Operation has completed with errors.
Start: 10/18/2019 12:32:56 AM
Stop: 10/18/2019 2:07:10 AM
Total Time: 01:34:14
2019-10-18 07:49:02 GMT-04:00
AcronisVSSDoctor-net45, 1.0.39.0, v4.0.30319
Microsoft Windows NT 6.2.9200.0, 4.0.30319.42000
===========================================================
VSS Services Configuration and Status
Status: OK
Description: All VSS-related services are configured correctly
Services:
Name: swprv
Title: Microsoft Software Shadow Copy Provider
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:
Name: VSS
Title: Volume Shadow Copy
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:
Name: EventSystem
Title: COM+ Event System
Status: Running
ReferenceStatus: Running
NeedToFixStatus: False
StartMode: Auto
ReferenceStartMode: Auto
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:
===========================================================
VSS Providers Configuration
Status: OK
Description: Only known VSS provider(s) found
Providers:
Id: b5946137-7b9f-4925-af80-51abd60b20d5
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}
Name: Microsoft Software Shadow Copy provider 1.0
IsDefault: True
===========================================================
VSS Access Control Configuration
Status: OK
Description: Known VSS access control entries are configured correctly
AccessControls:
UserName: NT Authority\NetworkService
EntryExists: True
UserExists: True
IsActive: True
IsOk: True
StatusDescription:
===========================================================
VSS Components Availability
Status: OK
Description: VSS components are accessible
===========================================================
VSS Writers Status
Status: OK
Description: All VSS writers are working correctly
Writers:
Name: Task Scheduler Writer
Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
State: [1] Stable
IsOk: True
Error: No error
Name: VSS Metadata Store Writer
Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
State: [1] Stable
IsOk: True
Error: No error
Name: Performance Counters Writer
Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
State: [1] Stable
IsOk: True
Error: No error
Name: System Writer
Id: {e8132975-6f93-4464-a53e-1050253ae220}
State: [1] Stable
IsOk: True
Error: No error
Name: ASR Writer
Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
State: [1] Stable
IsOk: True
Error: No error
Name: IIS Config Writer
Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
State: [1] Stable
IsOk: True
Error: No error
Name: BITS Writer
Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
State: [1] Stable
IsOk: True
Error: No error
Name: MSSearch Service Writer
Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
State: [1] Stable
IsOk: True
Error: No error
Name: WMI Writer
Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
State: [1] Stable
IsOk: True
Error: No error
Name: Shadow Copy Optimization Writer
Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
State: [1] Stable
IsOk: True
Error: No error
Name: Registry Writer
Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
State: [1] Stable
IsOk: True
Error: No error
===========================================================
VSS Shadow Storages Status
Status: OK
Description: All VSS shadow storages are configured correctly
Storages:
ForVolume: C:\
OnVolume: C:\
Used: 0 B
Allocated: 0 B
Maximum: UNBOUNDED
Minimum: 320 MB
VolumeSize: 441 GB
Available: 392 GB
TargetMaximum: 44 GB
MaximumGreaterThenMinimum: True
MaximumIsEnough: True
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: True
Description:
ForVolume: D:\
OnVolume: D:\
Used: 0 B
Allocated: 0 B
Maximum: UNBOUNDED
Minimum: 320 MB
VolumeSize: 21 GB
Available: 27 MB
TargetMaximum: 2244 MB
MaximumGreaterThenMinimum: True
MaximumIsEnough: True
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: True
Description:
===========================================================
Disk Free Space Available
Status: Warn
Description: Some disks have insufficient free space. Perform a cleanup.
Volumes:
Name: C:\
DeviceId: \\?\Volume{e2a2111a-32a3-4bd4-b7ad-4b66a005223a}\
Size: 441 GB
Available: 392 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True
Name: D:\
DeviceId: \\?\Volume{f0dddda2-f0cf-4022-8279-04f27b70ab09}\
Size: 21 GB
Available: 27 MB
Minimum: 320 MB
IsOk: False
Description: Free space is below required minimum
IsMounted: True
Name: \\?\Volume{358dae30-2a93-46e4-9839-c22e332f38c4}\
DeviceId: \\?\Volume{358dae30-2a93-46e4-9839-c22e332f38c4}\
Size: 649 MB
Available: 392 MB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: False
Name: \\?\Volume{e6960150-dc77-43fd-810c-9f525528197f}\
DeviceId: \\?\Volume{e6960150-dc77-43fd-810c-9f525528197f}\
Size: 935 MB
Available: 414 MB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: False
===========================================================
Disk I/O Load
Status: OK
Description: All disks are currently not overloaded
Disks:
Name: 0 C: D:
DiskBytesPersec: 442205
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 14
DiskWriteBytesPersec: 442205
DiskWritesPersec: 14
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 99
IsOk: True
Name: 1 F:
DiskBytesPersec: 0
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 99
IsOk: True
===========================================================
NTFS Volume Access Control Configuration
Status: OK
Description: All volumes have correct access control configuration
Volumes:
Name: C:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access
Name: D:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access
Name: \\?\Volume{358dae30-2a93-46e4-9839-c22e332f38c4}\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access
Name: \\?\Volume{e6960150-dc77-43fd-810c-9f525528197f}\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access
===========================================================
Event Log
Status: OK
Description: No VSS-related errors or warnings during previous day
Events:
- Log in to post comments

Name: D:\
DeviceId: \\?\Volume{f0dddda2-f0cf-4022-8279-04f27b70ab09}\
Size: 21 GB
Available: 27 MB
Minimum: 320 MB
IsOk: False
Description: Free space is below required minimum
IsMounted: True
Larry, if the D: drive is an OEM recovery partition, i.e. to allow setting the computer back to the factory state it had when purchased, then I would recommend trying to omit it from your backup source selection.
- Log in to post comments

Steve Smith Going to add D:\ to the exclusions tab. Is this the correct way to do so?
- Log in to post comments

Another possibility to try, if you do need to try and back it up (it's really not needed if you don't mind restoring a fresh OS and this is running Windows 10 - the OEM recovery goes back to factory with all the bloatware and old OS and Old patches) is to try disabling system protection and re-enable it again.
This is where Windows keeps recovery points and where VSS takes snapshots during backups with Acronis and other backup tools.
It's possible that system protection is enabled on that partition and is using too much space. Turning it off, delete restore points, turn it back on and take a new restore point so you have a current one again if you want. This may clear things up with VSS for the backup by freeing up some space.
Also check to make sure the same parition doesn't show up twice (like 2 instances of the C drive). This is a sure sign of a problem with VSS. You would want to disable both, close out and go back in and then there should only be one if that is the case.
- Log in to post comments

Larry, if you want to exclude, the best way is to go back and update the Source, then, pick only the desired paritions (all but that one).
- Log in to post comments

UPDATE: created new backup to only backup C: and still getting the same error.
- Log in to post comments

Larry, what does the log for the latest backup show?
- Log in to post comments

10/28/2019 2:50:28 AM: -----
10/28/2019 2:50:28 AM: ATI Demon started. Version: 23.5.1.17750.
10/28/2019 2:50:28 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/28/2019 2:50:28 AM: Operation VW-DOCTOR C ONLY started by schedule.
10/28/2019 2:50:29 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/28/2019 2:50:29 AM: Operation: Backup
10/28/2019 2:50:29 AM: Priority changed to Low.
10/28/2019 2:50:29 AM: Create Backup Archive From: To file: nas://10.0.0.196/Larry/Backup/HP Pavlon/VW-DOCTOR C ONLY.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Larry\AppData\Local\Temp, C:\Users\Larry\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Larry\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Larry\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Larry\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Larry\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Larry\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC, D:\
10/28/2019 2:50:29 AM: Pending operation 173 started: 'Creating partition image'.
10/28/2019 2:50:29 AM: Writing full version to file: VW-DOCTOR C ONLY_full_b1_s1_v1.tib
10/28/2019 2:51:13 AM: Pending operation 173 started: 'Creating partition image'.
10/28/2019 2:51:24 AM: Pending operation 173 started: 'Creating partition image'.
10/28/2019 4:10:18 AM: Pending operation 173 started: 'Creating partition image'.
10/28/2019 4:11:49 AM: Pending operation 173 started: 'Creating partition image'.
10/28/2019 4:11:56 AM: Error 0x101f6: Unable to create volume snapshot
10/28/2019 4:12:02 AM: Error 0x13c0005: Operation has completed with errors.
Start: 10/28/2019 2:50:28 AM
Stop: 10/28/2019 4:12:02 AM
Total Time: 01:21:34
- Log in to post comments

David, have you actually deselected the D: drive in the Source selection panel for this backup task. I can see that you have added D:\ to the Exclusions list for this task, but that will not override the source selection if D: is still selected there!
- Log in to post comments

First log and second log both show 5 Pending operation 173 started: 'Creating partition image' entries, so it seems there is no change to the selection. Be sure to use Bobbo's method for selection/deselecting partitions on the physical drive.
Why is the recovery partition assigned a drive letter? Is that normal? Since it is, can you open up System Protection and see if it is turned on for D:?
Might be worth trying to take a full backup of D: only. In the Advanced settings under Performance, turn off Snapshot.
- Log in to post comments

Trying again per bobo's suggestions. What I did notice when excluding D: under disks and partitions D:\ gets added to the exclusions tab list. Going to run backup tonight and will update. BTW, backup is 46GB and destination has 2.7TB free
- Log in to post comments


Glad to hear it worked out, Larry.
- Log in to post comments