• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

Kudos0

NG14:How to configure not to remove backup files so soon

Hello,

I have NG14 and I need to know how to configure it to not remove backup files so early. There must be a way to configure this but I don't see anything in the Options for it.

I have a RAID 0 array 1TB and I find that NG starts removing older backup files by the time I get to around 400GB of free space. This is too soon for me, how do I configure it to either change this limit or disable it altogether so I can choose when to delete older backups?

Thanks

Allen

Windows 7 Ultimate SP 1, 64 bit, 32 GB * NIS Vers. 21.6.0.32* Ghost 15 * IE 9, Firefox, Safari. Test laptop with W7 Home Premium 64 bit * NIS Vers. 21.6.0.32

Replies

Kudos0

Re: NG14:How to configure not to remove backup files so soon

Ghost doesn't use space as a determination for cleaning up recovery points.  When you set up you backups how many recovery points do you have it set to?  What you'll have is a base image, plus that number of incrementals, then a new base, and then the old set will be deleted after the new base is created.  If you want more to be saved you need increase that number in your backup job.

Kudos0

Re: NG14:How to configure not to remove backup files so soon

Hi Erik,

Thanks, but there has to be more to it than that. I have the number of incrementals set to 10 but also have it set to create a new base point on the 1st and 15th of each month and so a new base point is almost always created based on the 1st and 15th rule and almost never based on the MAX number.

Further I would point out that if Ghost were to start automatically deleting older recovery points simply because a new BASE was created I would escalate that through the roof!! It would be inexcusable for Ghost to do something like this! I as a user have every right to have multiple BASE points and I would never accept Ghost deleting them automatically except in the case of running too low on available disk space. Having a SINGLE base point is risky in the first place - it is like putting all your eggs in one basket. If something were to go wrong with that ONE base point, you have just LOST your disaster recovery capability! At least with multiple base points (space permitting) you are still going to be OK most likely if one base point is found to be bad.

++++++++++++++++++++++++++++++++++++++++++++++++++++

And I can tell you for a fact that Ghost does NOT do that. I have at present time 6 BASE points on my C drive and 5 each on my D and E drives. And I have multiple incrementals associated with quite a few of these base points.

I can also tell you that w/o exception when I get lower than somewhere around 350-400GB of available disk space, THAT is when Ghost pops up a dialog asking me for permission to delete an old recovery point to free up more space. And it uses the phrase "to free up more available space for additional recovery points" or similar wording when it asks me this! The problem is that since I use High compression I can fit at least 5-8 more BASE points before I run out of room. If I don't happen to be there to answer NO to this question it deletes them anway and I have a real problem with that.

There absolutely is a space available criteria for Ghost making this determination. The prompts from Ghost make this very clear and I am a software engineer so I understand this all too well.

Here is what I think is going on - I think Ghost is failing to take my configured Compression rate into account and therefore thinks that I am running out of space on my RAID 0 array. If I were to do backups WITHOUT compression then 400GB would be more appropriate because w/o compression I would need approx 205 GB to backup all 3 HD's.

I think you should ask your engineers this question and find out if this is configurable in some way. There does not appear to be anything in Ghost options to control this but perhaps there might be some registry key - don't know. Either way this should be made to be configurable. Further if I am correct that Ghost is not taking configured compression rate into account this should also be fixed because it would be a bug which causes Ghost to prematurely delete older recovery point sets!

Allen

Windows 7 Ultimate SP 1, 64 bit, 32 GB * NIS Vers. 21.6.0.32* Ghost 15 * IE 9, Firefox, Safari. Test laptop with W7 Home Premium 64 bit * NIS Vers. 21.6.0.32
Kudos0

Re: NG14:How to configure not to remove backup files so soon

Have you checked the Settings under Tools/Manage Backup Destinations? There is s selection for Ghost to monitor disk space for backup storage based on disk size, as well as a selection to automatically optimize storage which will "delete old recovery point sets and limit file versions to remain within threshold without prompting."
Kudos0

Re: NG14:How to configure not to remove backup files so soon

Hi,

I have it set to NOT monitor but it still prompts me for it and my experience has been that if I am not there to answer NO, it has been removing them anyway.

But good point, I should have mentioned that in my original post.

It might even work "sometimes" but I have just seen it remove them too many times to trust this.

Thanks

Allen

Windows 7 Ultimate SP 1, 64 bit, 32 GB * NIS Vers. 21.6.0.32* Ghost 15 * IE 9, Firefox, Safari. Test laptop with W7 Home Premium 64 bit * NIS Vers. 21.6.0.32

This thread is closed from further comment. Please visit the forum to start a new thread.