On 2017-12-04 06:03, Marc Gilliatt wrote:
Hi,
This backup runs for 3 or 4 days and then fails. I have given full
permission to the bakcuppc user, And I have excluded the \System
Volume Information\SRM\* directory.
I haven't got any more ideas on how to resolve my issue. It still
hasn't done its first full backup.
Any ideas, please?
But of course, let's review a few fundamentals:
- Windows file semantics are such that open files cannot be opened by
other processes, such as SMB.
- Windows file permissions are more complex than *nix, with ACLs, and
there's no concept of "root" with access to everything.
- Windows file systems contain metadata and exotic structures which *nix
systems do not inherently understand.
So, first, think about why you're interested in backing up the System
Volume Information folder in the first place. It's normally a hidden
folder that users don't have access to, used to store metadata and
restore points, indexing data and so on. In the event of a failure,
what do you intend to do with it?
At any rate, because of the nature of this data, you cannot, and should
not, back it up via SMB. Even if you could, it would not be in a
consistent state without a shadow copy (which I note are also
coordinated through the metadata stored here) and I can't say I
understand the point of backing up useless data.
To be fair, I do back mine up, which I do using shadow copies and rsync,
in the event that a system restore point is necessary or a unique
failure mode necessitates a more exotic recovery. However, this is
simply not possible using SMB.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
