Scheduled Base backup failed with
Description: Error EBAB03F1: The operation was canceled by the user.
Info 6C8F1C2F: A recovery point operation on drive Drive Backup of Seagate1500 (F:\) was cancelled by the user.
Error E7D1001F: Unable to write to file.
Error E7D1003C: There is not enough space.
Error EBAB03F1: There is not enough space on the disk.
Even though the Backup Destination drive is set to "Automatically optimize storage: Delete old recovery point sets and limit file versions to remain within threshold without prompting", and there are 3 old (480MB) sets it could have auto-deleted. The 3 old sets are the only things on the 2TB destination hard drive (well almost; there's also a 91MB one-time backup on it).
Ghost 15
Oops, I forgot to put "Ghost" in the Subject line, hope that doesn't keep people from seeing it!
Start a fresh job, but do not use the automatic optimize feature. Rather, use the setting to retain a certain amount of recovery points, allowing Ghost to delete the oldest after the newest is created. Keep in mind that this means that if you have it set to retains 3 recovery point sets, there must be room for at least 4 sets, as the oldest is deleted only after the newest is completed successfully.
andreash_utah wrote:
Start a fresh job, but do not use the automatic optimize feature. Rather, use the setting to retain a certain amount of recovery points, allowing Ghost to delete the oldest after the newest is created. Keep in mind that this means that if you have it set to retains 3 recovery point sets, there must be room for at least 4 sets, as the oldest is deleted only after the newest is completed successfully.
Thank you very much for the reply, Andy!
The "automatic optimize" feature has always worked for me in the past; and I really like it. (Though I guess the "X sets" strategy would work as long as no incrementals are too big, and I have learned to avoid that issue by not defragging between base backups.)
Do I understand that you are suggesting creating a new backup job? If so I'll try that, but perhaps first again using "automatic optimize".