Retired backup scheme, ok to delete those files at will?
I have created a new backup scheme and have disabled the old backup which ran daily. As far as I can see there is no reason to retain the old backup scheme tib files once the new backup has engaged. I don't need them for archival purposes. I do delete the old scheme tib files, it's not going to invoke any problems with acronis? I'm being cautious because with the older scheme, where automatic cleanup was enabled, when I manually deleted some files acronis went into a tizzy of backup consolidation.


- Log in to post comments

Thanks...just to be ultra clear, the backup is still listed, but it will never be executed manually or via schedule. That's what you mean by 'removed the old backup task", correct?
I will delete the backup from the list as soon as I know that the new backup is working as intended.
- Log in to post comments

Remove the backup task - he means from teh console. There are 2 options:
Delete Entirely = remove from console and delete the physical backup .tib files off the machine
Remove = remove from the console but keep the physical backup .tib files on the machine.
If you want to get rid of everything for good in one swoop, use "delete entirely" - your backup are now gone forever.
If you want to remove from the console, but possibly hold onot the backu files to be used later, select "remove". Then, when you're comfortable, go to the files using Windows file explorer and delete those backup files and it will have no impact on the console since the backup was already "removed". Just make sure you're only manually deleting the correct backup files when you use this method.
Otherwise, if you manually delete files in Windows file explorer FIRST, and then try to do something with teh backup in the console (validate, delete entirely, etc), Acronis will throw out warnings that the files can't be found. Then you have to ignore each one until they all disappear.
Attachment | Size |
---|---|
400982-135775.jpg | 27.09 KB |
- Log in to post comments
