Dear subversion community,
as part of a daily backup process, I do "svnadmin dump"s, gzip
them
and create several encrypted backups of the "*.dump.gz".
Now, the svn admin dump step (svnadmin dump -q ...)
worked without errors (exit code 0 and no errors on
stdout/stderr),
and during the next step (encrypted backup) the VM crashed.
When looking into the log, I see that there was an I/O error on
the
disk which is used by the VM. Now I now that the foo.dump.gz
are correctly backed up, but are they consistent (i.e. not
affected
by the I/O error(s))?
So the question is: Does "svnadmin dump" do some consistency
checks (like svnadmin verify does)?
Regarding "svnadmin verify path/on/server": Can I be sure that
this does not modify the data?
Or do I have to use "svnadmin load" (on another machine),
does "load" do more consistency checks?
Many Thanks(!) and Best Regards,
Felix
Phone | : +49 228 5348 0430 |
Direct | : +49 228 4097 7118 |
: felix....@sidact.com | |
Web | : http://www.sidact.com/ |
hello Andreas,
many thanks for the quick answer. I found this link:
https://svnbook.red-bean.com/en/1.7/svn.ref.svnadmin.c.verify.html
which states "... This basically iterates through all revisions in the repository by internally dumping all revisions and discarding the output—...".
which leads me to think that "svnadmin dump" does the same checks as "svnadmin verify".
Anyway, I do get your point that it is a good idea to "load" the
repos every month
or so.
Many Thanks and Best Regards,
Felix