[daisy] [JIRA] Commented: (DSY-664) lost data with unsuccessful backup?

[Karel Vervaeke (JIRA)]

    [ http://issues.cocoondev.org//browse/DSY-664?page=comments#action_13668 ] 

Karel Vervaeke commented on DSY-664:
------------------------------------

It will make much more sense continuing on the mailing list. (Threading and reply indenting > and such ;-)
Once we narrow things out we can feed the result back into jira if required.

If you're not subscribed yet, send a mail to daisy-subscribe at lists.cocoondev.org

> lost data with unsuccessful backup?
> -----------------------------------
>
>          Key: DSY-664
>          URL: http://issues.cocoondev.org//browse/DSY-664
>      Project: Daisy
>         Type: Task
>   Components: Backup
>     Versions: 2.1
>  Environment: Windows 2003 R2
>     Reporter: Wolfram Mayer
>     Priority: Minor

>
> Hi,
> we had an incident when a backup failed and created empty directories as daisy-blobstore.zip-tmp.
> At that day documents had been changed and saved (nothing obvious was remarked by users that documents had not been saved).
> 3 weeks later it had been discovered that changes were been lost. Scanning all daily backups from it can be seen that the changes were always in the blobstore. Nevertheless these changes can't be seen via the recent changes, versions or recent changes this was visible neither LIVE nor STAGING.
> Backups after that day were successful. How could this happen and how could this be resolved?
> Is it possible that un unsuccesful backup leads to a backup lock. With backup lock no document changes are possible which is not recognized?
> Could this explanation be possible? And if yes how could that be resolved?   
> Kind Regards,
>      Wolfram

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira