Today my backup failed due to lack of space....
I don't know what happened here? I back up to my P: drive. It has plenty of space and no disk errors?
============================
C:\>chkdsk p:
The type of the file system is NTFS.
Volume label is P_Drive.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
7424 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
16 reparse records processed.
8340 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
16 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
459 data files processed.
CHKDSK is verifying Usn Journal...
11639288 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
3815444 MB total disk space.
2603323 MB in 6787 files.
1584 KB in 460 indexes.
0 KB in bad sectors.
204455 KB in use by the system.
65536 KB occupied by the log file.
1241006428 KB available on disk.
4096 bytes in each allocation unit.
976753919 total allocation units on disk.
310251607 allocation units available on disk.
==================
Meanwhile I'm getting out of memory errors? From the more detailed MVP Log Viewer program:
==================
log uuid=EEC360A5-022A-4287-BAFA-BACAA58106FE; product=True Image; version=19.0; build=6595; task=14267A53-DF4E-4FCC-A637-D474537F212E; task_name=All Drives C and K
Start= 7/7/2018 2:29:33 PM
id=1; level=2; module=100; code=0; date/time=7/7/2018 2:29:33 PM
message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2; level=2; module=100; code=2; date/time=7/7/2018 2:29:33 PM
message=Operation All Drives C and K started by schedule.
id=3; level=2; module=100; code=0; date/time=7/7/2018 2:29:37 PM
message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=4; level=2; module=316; code=0; date/time=7/7/2018 2:29:37 PM
message=Operation: Backup
id=5; level=2; module=100; code=11; date/time=7/7/2018 2:29:37 PM
message=Priority changed to Low.
id=6; level=2; module=11; code=1008; date/time=7/7/2018 2:29:37 PM
message=Create Backup Archive From: Disk 2, Disk_K (K:) To file: P:\Acronis_Backup\All Drives\All Drives C and K.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\ispal_000\AppData\Local\Temp
C:\Users\Administrator\AppData\Local\Temp
C:\Users\ispal_000\AppData\Local\Microsoft\Windows\INetCache
C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache
id=7; level=2; module=1; code=504; date/time=7/7/2018 2:29:37 PM
message=Pending operation 172 started: 'Creating partition image'.
id=8; level=2; module=100; code=0; date/time=7/7/2018 2:32:14 PM
message=Writing full version to file: All Drives C and K_full_b75_s1_v1.tib
id=9; level=4; module=1; code=502; date/time=7/7/2018 2:42:11 PM
message=Not enough memory; line_tag=0x65B5EB7011094700
Error_Code=AfYBAQAARwkRcOu1ZU5vdCBlbm91Z2ggbWVtb3J5ACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVccHJvY2Vzc29yXGRpc2thZG1cZGFfY29tbWl0LmNwcAAkZnVuYwBBRGFQcm9jZXNzb3I6OkNvbW1pdEltcGw6Ok9uRGFFcnJvcgAkbGluZQBOWQEAAAAAAAAAAgAHACQ7DLc5k9uCTm90IGVub3VnaCBtZW1vcnkAJG1vZHVsZQBBdGlfZGVtb25fdnNfNjU5NQAkZmlsZQBBazpcNjU5NVxyZXNpemVyXGxpYnJhcnlccmVzZXJyb3IuY3BwACRmdW5jAEFyZXNpemVyOjpOZXdIYW5kbGVyOjpIYW5kbGVyACRsaW5lAE42AAAAAAAAAAA=
id=10; level=4; module=7; code=2; date/time=7/7/2018 2:42:11 PM
message=Not enough memory; line_tag=0x82DB9339B70C3B24; hide=1
id=11; level=4; module=7; code=2; date/time=7/7/2018 2:42:11 PM
message=Not enough memory; line_tag=0x91BD40306B6C5083
Error_Code=AQIABwCDUGxrMEC9kU5vdCBlbm91Z2ggbWVtb3J5ACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpBcmNoaXZlT3BlcmF0aW9uOjpFeGVjdXRlACRsaW5lAE5tAAAAAAAAAAACAAcAJDsMtzmT24JOb3QgZW5vdWdoIG1lbW9yeQAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XHJlc2l6ZXJcbGlicmFyeVxyZXNlcnJvci5jcHAAJGZ1bmMAQXJlc2l6ZXI6Ok5ld0hhbmRsZXI6OkhhbmRsZXIAJGxpbmUATjYAAAAAAAAAAA==
id=12; level=4; module=7; code=2; date/time=7/7/2018 2:42:11 PM
message=Not enough memory; line_tag=0x82DB9339B70C3B24; hide=1
id=13; level=4; module=316; code=5; date/time=7/7/2018 2:42:11 PM
message=Operation has completed with errors.; line_tag=0x9F2C53C72E8BCE7B
Error_Code=AQUAPAF7zosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XHByb2R1Y3RzXGltYWdlclxkZW1vblxtYWluLmNwcAAkZnVuYwBBbWFpbgAkbGluZQBOhQIAAAAAAAAA
id=14; level=2; module=103; code=0; date/time=7/7/2018 2:42:19 PM
message=The e-mail notification has been successfully sent.
id=15; level=4; module=103; code=0; date/time=7/7/2018 2:42:20 PM
message=Batch operation has completed with errors.
Start= 7/7/2018 2:29:33 PM
Finish= 7/7/2018 2:42:20 PM
Total Time= 00:12:47
===================
Don't understand? Prior backups are not large?
---------------
P:\Acronis_Backup\All Drives>dir
Volume in drive P is P_Drive
Volume Serial Number is BEE5-01F4
Directory of P:\Acronis_Backup\All Drives
07/07/2018 02:42 PM <DIR> .
07/07/2018 02:42 PM <DIR> ..
04/28/2018 02:35 PM 257,757,798,912 All Drives C and K_full_b67_s1_v1.tib
05/12/2018 03:40 PM 253,568,274,944 All Drives C and K_full_b68_s1_v1.tib
05/19/2018 02:41 PM 278,391,522,304 All Drives C and K_full_b69_s1_v1.tib
05/26/2018 03:06 PM 274,792,765,440 All Drives C and K_full_b70_s1_v1.tib
06/09/2018 02:46 PM 274,308,208,128 All Drives C and K_full_b71_s1_v1.tib
06/16/2018 02:40 PM 270,298,889,728 All Drives C and K_full_b72_s1_v1.tib
06/23/2018 05:27 PM 269,713,005,056 All Drives C and K_full_b73_s1_v1.tib
06/30/2018 02:37 PM 268,210,439,168 All Drives C and K_full_b74_s1_v1.tib
8 File(s) 2,147,040,903,680 bytes
2 Dir(s) 1,270,748,225,536 bytes free
-----------------
I ran CHKDSK on the 3 drives I'm backing up (only showing space used which might include data that is excluded):
C: - 86411388 KB in 337954 files.
K: - 261848608 KB in 246802 files.
L: - 309326716 KB in 5053 files.
I'm assuming the error is hard disk space? Might it be RAM? Task Manager shows a lot available, even before swapping?
Any ideas or should I just retry?

- Anmelden, um Kommentare verfassen zu können

Irv, there looks to be two different issues at work here.
Not enough memory; - this is unrelated to your physical backup drive but refers to either program memory required by the ATI application, or to snapshot memory for VSS.
This could indicate a RAM issue but given your subsequent backups look to have run without giving the same issue, then I would suspect that there was some other background activity taking place which was placing a heavy demand on memory such as Windows Update or an antivirus scan etc.
Failed to exclusively access backup P:\Acronis_Backup\All Drives\All Drives C and K_full_b67_s1_v1.tib during consolidation. Make sure the backup file is not opened in other applications.
This could well have been caused by having an Explorer application open to the backup location - the backup task itself was successful and this error was given when automatic cleanup (shown as consolidation in the log) was trying to perform its actions.
The best advice for these issues is to try to run your ATI backups when there is minimal other significant activity taking place on your computer - not always possible but worth trying if you can!
- Anmelden, um Kommentare verfassen zu können

Steve, I think we both came to the same conclusion... first one had too much in memory, 2nd was due to the Explorer open to the backup folder.
In the first case I had Firefox open with maybe 14 tabs open... and I'll assume I had eaten a lot of RAM... got 8GB's, normally 3 to 4GB's being used.. The screen grab shows a NEW run of ATI operating and the RAM usage. The Resource Monitor shows a lot of closed programs using up RAM which would be discarded once RAM is used up.
Now in all my years of using ATI on a few computers I have never seen this happen? Therefore the surprise this time.
Also I had something really 'odd' happen on boot this morning? I get a dialog box that I don't have a swap file? Huh, it is on drive L:? Opened Exporer++ and I see I now have an H: and no L:??? Well H: was my old L:. Fixed that by changing the drive letter and then fixed the swap file to be on L: again. Problem is I didn't recall what I had. I don't think I've ever swapped, and when I did, not much. So I set the initial size to 300MB's and 3GB's as max. Figured when I hit a problem I'd move the max. Wondering now if that did indeed cause the problem. I do recall opening Task Manager after I got that error I opened TM and only 6GB's were used with a peak of 7.5GB's?
Anyway, I reran ATI and it worked fine....
==================
1 True Image 7/7/2018 4:32:15 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 True Image 7/7/2018 4:32:15 PM Operation All Drives C and K started manually.
3 True Image 7/7/2018 4:32:18 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
4 True Image 7/7/2018 4:32:18 PM Operation: Backup
5 True Image 7/7/2018 4:32:18 PM Priority changed to Low.
6 True Image 7/7/2018 4:32:18 PM Create Backup Archive From: Disk 2, Disk_K (K:) To file: "P:\Acronis_Backup\All Drives\All Drives C and K.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\ispal_000\AppData\Local\Temp, C:\Users\Administrator\AppData\Local\Temp, C:\Users\ispal_000\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache
7 True Image 7/7/2018 4:32:18 PM Pending operation 172 started: 'Creating partition image'.
8 True Image 7/7/2018 4:34:44 PM Writing full version to file: All Drives C and K_full_b76_s1_v1.tib
9 True Image 7/7/2018 5:50:32 PM Pending operation 172 started: 'Creating partition image'.
10 True Image 7/7/2018 5:50:35 PM Pending operation 172 started: 'Creating partition image'.
11 True Image 7/7/2018 5:50:35 PM Pending operation 172 started: 'Creating partition image'.
12 True Image 7/7/2018 6:02:20 PM Pending operation 172 started: 'Creating partition image'.
13 True Image 7/7/2018 6:02:25 PM Pending operation 172 started: 'Creating partition image'.
14 True Image 7/7/2018 6:02:25 PM Pending operation 172 started: 'Creating partition image'.
15 True Image 7/7/2018 6:02:25 PM The following backups have been successfully created: "P:\Acronis_Backup\All Drives\All Drives C and K_full_b76_s1_v1.tib"
16 True Image 7/7/2018 6:02:25 PM Consolidate Backup Archive Location: "P:\Acronis_Backup\All Drives\All Drives C and K_full_b76_s1_v1.tib" Destination: "P:\Acronis_Backup\All Drives\All Drives C and K_full_b76_s1_v1_9183BF48-2F03-4904-9E4D-D114C74FFEEC.tib"
17 True Image 7/7/2018 6:02:25 PM Consolidate Backup Archive Location: "P:\Acronis_Backup\All Drives\All Drives C and K_full_b76_s1_v1.tib" Destination: "P:\Acronis_Backup\All Drives\All Drives C and K_full_b76_s1_v1_9183BF48-2F03-4904-9E4D-D114C74FFEEC.tib"
18 True Image 7/7/2018 6:02:25 PM Deleting backup file with path P:\Acronis_Backup\All Drives\All Drives C and K_full_b67_s1_v1.tib.
19 True Image 7/7/2018 6:02:25 PM Deleting backup file with path P:\Acronis_Backup\All Drives\All Drives C and K_full_b68_s1_v1.tib.
20 True Image 7/7/2018 6:02:26 PM Operation has succeeded.
====================
Interesting last few line. TWO files deleted... I missed the one DIR list above that there were 9 backups and I only specified 8. I guess ATI could have had a better error message detailing why it was failing.
Anyway, all is well now, thanks.
Anhang | Größe |
---|---|
454629-149397.JPG | 150.21 KB |
- Anmelden, um Kommentare verfassen zu können

Irv, thanks for the update and glad that all seems to be OK again now.
I have to say that it has been a long time since I have bothered to manually configure swap file sizes or move the swap file to a different disk or partition. I guess that Windows 10 is a whole lot better at handling these aspects of the system than the earlier versions of Windows were, and especially with 64-bit processors, multi-threading etc that is now common-place.
Drive letter changes is another story, something that can be a little unpredictable at times, especially if you forget to disconnect a USB drive and boot with it connected etc. Windows Updates can also trigger such changes too when a new Windows Recovery partition is created. So again, letting Windows manage swap file settings in this regard works for me.
- Anmelden, um Kommentare verfassen zu können

Steve, normally I would let Windows manage the swap file location and size. However my OS is on an SSD (I keep mostly only the OS and some programs I need on it so a restore would get me going) and Windows puts it by default on C:. I had 2 problems with this, when I put the SSD in this particular PC the cost was high for large SSD's and I used only a 128GB. My 'image' of C: is around 60GB's usually, but when Windows would install a new version WINDOWS.OLD could be as high as 30GB's, and the default size of the swapfile and hibernation file could be another large file. I also tend to leave the Recycle Bin collect files for a long time. So I worried about the size of C: and also SSD's do have a limited read/write surface life, so because of all that, I moved the 2 files off of the SSD. Plenty of free space on the hard drives I have.
As for the disk letter change, no, a USB drive was not left in. The letter changed to a place that was unusual to say the least. This PC is a Dell XPS that has a multi-function card slot which used 4 drive letters. Well H: is between the last slot and the one before it (G: and I:). I: used to be H: and I do recall sometime before a USB drive came up in H:. Not a problem as there are no programs associated with those drive letters. Suspect the PC has some problem bringing up either the card reader or L: which is a single hard drive and assigned letters differently? I checked and I had NO MS Updates? I did recall my PC took a LONG time to shutdown the night before, and that day Dell's Support Assist bugged me to allow it to 'SCAN THE H/W' which I did let it do. It supposedly found no problems and made no changes? Either that did something or I'm starting to have drive failure? Today, no problems booting? Odd...
- Anmelden, um Kommentare verfassen zu können

Irv, fully understand the reason for managing the Windows swap file when you have only a 128GB SSD for the main OS - I am sure that I would do the same and for the same reasons.
- Anmelden, um Kommentare verfassen zu können