Single version backup appends to file name
With TI2012, I was able to create daily archives with the exact same file name ("Backup.tib") which made it easy to copy over an older, unneeded backup. Now with TI2013, I'm seeing file names like "Backup_full_b6_s1_v1.tib" where the "b" parameter keeps incrementing.
Is there a way to lose this file name suffix and return to TI2012 behavior?
Woodp,
I too, find that the new naming feature is sometimes not the best for all users. It helps with identifying the type of backup as well helping to identify the correct backup files associated in a set (version chain). When doing a single version chain backup, the new naming scheme increments the "b" paramenter and this causes issues for some folks. At this time, it is not an option to change this behaviour.
Please feel free to post your suggestions for the ability to turn this feature on and off, or at least have the single version chain scheme not increment the "b" value when creating full backups.
There are two locations for you to be heard.
First, submit feedback directly to Acronis here: http://www.acronis.com/support/feedback.html
Acronis does review and implement changes based on user requests, but only if they are aware of them.
Many changes for the current version were based on user requests that were submitted to them.
Only if multiple users request a change, will a change be considered
Make your suggestions count by providing feedback to Acronis directly, not just in the forums.
Please be specific and detailed when providing feedback to Acronis.
Second, in this forum topic: http://forum.acronis.com/forum/35369
(Not nearly as effective as direct feedback)
James
Woodp,
When doing a single version chain backup, the new naming scheme increments the "b" parameter and this causes issues for some folks. At this time, it is not an option to change this behavior.
Thanks, James.
I'll take your advise and submit feedback. My particular use case is that TI2003 creates an archive on a secondary drive (Drive D:) in the same box. Since I want an offsite copy, I have a scheduled task that copies the TIB file to a remote storage location. Obviously my scheme falls apart when the filename changes every day.
My ideal solution would be TI2012 behavior in which I could turn off the filename suffix.
Question: Did TI2013 installation change any of my TIB files? Could I uninstall TI2013 and reinstall TI2012 and still have access to all my archives?
The tib files should work between the 2012 and 2013 versions without any problems. Be sure to validate the files again in 2012 to be sure they are okay. 2013 does not change the older files.
woodp,
Under backup options, there is the feature to run a second backup to a different location.
In your copy methods, you could use a copy program such as Replicator and it could be Replicastor scheduled (or manual) to copy the contents of one folder to another folder and after the first run, it would only copy anything new inside the folder on any subsequent copy. Thus, if Replicator ran after each backup, it would only copy the backup which was not there on the prior copy run.
The tib files should work between the 2012 and 2013 versions without any problems. Be sure to validate the files again in 2012 to be sure they are okay. 2013 does not change the older files.
Thank you. I have reverted to TI2012 and it's working exactly as expected.
It helps with identifying the type of backup as well helping to identify the correct backup files associated in a set (version chain).
I don't mean to beat a dead horse here, but isn't TI2013 intended to be a home user product? I would expect business users to need that degree of file identification but a home user with 2 or 3 computers should be able to manage his own backups ... Just saying ...
In your copy methods, you could use a copy program such as Replicator and it could be Replicastor scheduled (or manual) to copy the contents of one folder to another folder and after the first run, it would only copy anything new inside the folder on any subsequent copy..
GroverH,
I'm not sure I fully understand - If TI2013 can be programmed to created a second copy on a remote system, what's the purpose of Replicator? And why wouldn't just running XCOPY as a scheduled task be so much easier?
For now I've reverted to TI2012 and filed a feature request. At least for me, simple is better.
Woodp,
Experience on the forums has shown that for a number of reasons, users who have multi tasks for one machine and large archives have in the past become confused as to what image in an archive is what, and have inadvertnently deleted parts of an archive causing chain images to either fail or not be restorable. This system is meant to be of help to them.