Re: [ARMini-support] SafeStore Question
- From: A Rawnsley <rcomp@xxxxxxxxxxx>
- To: armini-support@xxxxxxxxxxxxx
- Date: Wed, 28 Jun 2017 19:21:00 +0100
In message <1751615356.chris@xxxxxxxxxxxxxxxxx>
Chris Hughes <lists@xxxxxxxxxxxxxxx> wrote:
In message <bf95605356.boase@xxxxxxxxxxxxxxxxx>
Bernard Boase <b.boase@xxxxxxx> wrote:
On 26 Jun, ricp@xxxxxxxxxxxxxxxx typed:
SafeStore is prone to corrupting its tree files, not just on ARMX6.
Usually it just misses out lines, which can be recovered if you add
the missing <dir> and </dir> lines. I assume any missing file tags
will just result in those files being treated as new. Unfortunately
when it starts setting all the stamps to zero there's not a lot you
can do.
I wouldn't want my backups to depend on manually checking the (quite
large in some cases) Tree files, and altering them! It's alarming,
though, that you say" SafeStore is prone to corrupting its tree file".
Meanwhile, at Andrew's request I have contnued this discussion only
with private emails to Alan Wrigley, who I trust will be able to shed
light on how we should more reliably use SafeStore.
Just for some balance I have only had a tree corrupt after I installed
a new version of SafeStore but does warn you in the readme to redo a
Force refresh. I forgot to do that.
Otherwise it backs everything up to my NAS (Synology) without errors.
Indeed, to echo Chris, I have multiple, daily backups running. Although,
to be fair, most are internal between drives, rather than onto NAS (for
speed reasons mainly).
Do bear in mind that different NAS models will have different "quirks"
when it comes to handling of certain "magic" filenames or characters. We
do our best to resolve these kind of issues internally within SafeStore,
but it is something to be aware of.
This is, I guess, the downside of the "file replication" style of backup
used by SafeStore vs the old "munge-all-data-into-giant-archive-datafiles"
approach used by older backup software. When replicating between two
different devices, running different disc formats/OSs, there's always the
potential for mis-match.
(Another one to watch out for, since I've been battling it all day today,
is that Windows' max file path is smaller than RISC OS' at roughly
200chars. There's the potential there for *very* deep folder structures
to cause issues. This one always makes me smile, in a way, because
everyone expects Windows to be soooo good for that kind of thing, yet RISC
OS actually handles longer paths!)
Andrew
--
R-Comp
22 Robert Moffat, High Legh, Knutsford, Cheshire WA16 6PS
Tel: 01925 755043 Fax: 01925 757377
http://www.rcomp.co.uk
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
