On Mar 09 2016, Riku Bister <[email protected]> wrote:
>> If you did something like that, you can try to get things in order by
>> removing the s3ql_metadata_bak* files from the storage backend, as well
>> as the local cached copy of the metadata (.db and .param file) and then
>> running S3QL 2.17's fsck. But no guarantees.
>>
> nope, but i have a backup of those files before upgrade from storage. is
> it safe restore them and re-try? only files i dont have back up is the data
> files
The upgrade aborted before it had a chance to modify any of these
files. So unless you did something you did not tell me about, the
backups should be identical to what's stored in the remote server. Can
you confirm?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
