USB Key protected by Acronis. Backup impossible on this key.
Bonjour à tous
J'écris en français car ce sera plus facile pour moi. Je posterai une traduction à la fin de mon message :-)
Je rencontre un problème grave avec Acronis 2015 (et 2014).
Je veux faire une sauvegarde (shéma unique) sur 2 clés USB. Un jour sur une clé, le lendemain sur l'autre et ainsi de suite.
Le problème que je rencontre est le suivant : avec une des 2 clés, dès qu'une autre sauvegarde se fait (il y a une sauvegarde programmée sur un disque externe), Acronis "protège" la clé, il n'est plus possible d'écrire dessus. La sauvegarde sur cette clé est donc impossible.
Si le lendemain, on remplace la clé par une autre, tout se passe bien.
Le surlendemain, "la clé qui pose problème" n'est plus protégée (!), jusqu'à ce qu'une sauvegarde Acronis démarre.
L'assistance Acronis n'a pas été capable de m'aider et a fini par refuser de m'aider, malgré des captures d'écran qui montraient bien que la clé était vérouillée pendant la sauvegarde Acronis.
Cela fait plus d'un mois que je me débrouille seul, sans trouver de solution.
Quelqu'un a-t-il déjà rencontré ce problème ? Existe-t-il une solution ?
Merci :-)
Stéphane
Hello everyone
I write in French because it will be easier for me. I'll post a translation at the end of my message :-)
I am having a serious problem with Acronis 2015 (and 2014).
I want to backup (single backup) on 2 USB keys. A day on a key, the next day on the other and so on.
The problem I encounter is: with one key, as soon as another backup is done (there is a scheduled backup to an external drive), Acronis "protect" the key, it is no longer possible write on it. The backup on this key is not possible.
If the next day, the key is replaced by another, everything goes well.
Two days later, "the problem key" is no longer protected (!), Until a backup Acronis starts.
The Acronis support has not been able to help me and eventually refuse to help me, despite screenshots which demonstrated that the key was protected during Acronis backup.
For over a month I manage alone, without finding a solution.
Has someone already encountered this problem? Is there a solution?
Thank you :-)
Stéphane

- Log in to post comments

Hi David
Thanks for your help.
The key is a 64 GB Kingston DataTraverler.
I suppose this is this option you mind. (see image2). If yes, yes I've unchecked it.
But in any case, why this option would product this problem ?
Any other suggestion ? :-)
Stéphane
Attachment | Size |
---|---|
275244-120190.jpg | 162.4 KB |
- Log in to post comments

Hello,
Your question, when translated, is unclear.
I am going to bring a laptop to work with tomorrow, I have a co-worker who is from France, and she will translate your question and help me write a reply. I need to boot up an Acronis version to get the answer you need.
David
Bonjour,
Votre question , une fois traduit , est incertaine.
Je vais apporter un ordinateur portable pour travailler avec demain, je dois un collègue qui est de la France , et elle va traduire votre question et me aider à écrire une réponse . Je besoin pour démarrer une version d'Acronis pour obtenir la réponse dont vous avez besoin .
David
- Log in to post comments

Hello David.
Sorry if my question is unclear :-(
Perhaps this screen-shots will help you to understand my problem.
I'm not sure you will easily obtain the same behavior on your PC ...
Thanks :-)
Attachment | Size |
---|---|
275271-120208.jpg | 210.04 KB |
275271-120211.jpg | 219.4 KB |
275271-120214.jpg | 214.49 KB |
275271-120217.jpg | 233.77 KB |
275271-120220.jpg | 198.17 KB |
275271-120223.jpg | 215.51 KB |
275271-120226.jpg | 206.48 KB |
275271-120229.jpg | 220.33 KB |
- Log in to post comments

General comments:
If the problem is that if tasks in the main menu list a higher file count ((TASK TOTAL BACKUPS) than the number of actual tib files in the storage folder,
the cause is that specific backup task has become mis-matched with the history file.
GH57. Assorted task features.
Quickest and only solution for the mis-match is to stop using the problem task and create a new task with a new task using a different task name.
I prefer to each task to have its own storage sub-folder and each task has its own unique name.
---------------------------------------------------------------
Or, if have many problem tasks and you want to start over with ALL NEW TASKS, you can delete the Acronis history file.
dit/added:
To clear out all backup tasks so the history file starts over fresh. The tib files are not affected and remain untouched in their storage folders.
No tasks will remain and new tasks will need to be recreated. Remember, editing existing tasks are cause for the task to malfunction. Once the task is in use, make no further changes to the task. If changes needed, start a new task and stop using the old task.
How to delete the Archives.xml file
Prior to deleting the archives.xml file, Acronis has unofficially suggested that you first
01) Stop the program.
02) Stop all acronis services.
3) select "show hidden files and folders"
http://windows.microsoft.com/en-gb/windows/show-hidden-files#show-hidden
4) delete following folders:
C:\ProgramData\Acronis\Home\Database
C:\ProgramData\Acronis\TrueImageHome\ArchiveOptions
C:\ProgramData\Acronis\TrueImageHome\Database
C:\ProgramData\Acronis\TrueImageHome\Scripts
5) start Acronis services
6) start Acronis True Image 2014 and add backups
http://www.acronis.com/en-us/support/documentation/ATIH2014/#3504.html
7) check if it solves the issue
__________________
- Log in to post comments

Hi GrovertH :-)
It seems I'm not clear when I explain what is my problem. The problem is that Acronis "locks" (is it the right word ?) the usb Key. After that, it's impossible to write on this key.
You wrote : "Remember, editing existing tasks are cause for the task to malfunction. Once the task is in use, make no further changes to the task. If changes needed, start a new task and stop using the old task."
"Ah bon ?" Acronis 2014 and 2015 are really reliable if it's not possible to change any parameter once a backup is created ! I don't remenber that previous versions were so sensitive.
Best regards.
Stéphane
- Log in to post comments