Post by T Post by B00ze Post by T
Did not see anything helpful.
I don't think I can do this.
As a test, I gave a drive a drive letter, shared it, and
used Windows Explorer to make sure the share was working.
Then I removed the drive letter and the share stopped working
How about using admin shares?
i.e. net use x: \\localhost\c$\Folder\Example
But maybe they disappear when you remove the drive letter? I know
there is a way to access devices directly with \\.\ but I am having a
hard drive finding something that works. For instance, "fltmc volumes"
lists the volumes, but I can't get DIR to work with them (nor NET USE.)
Ya, they disappear when you remove the drive letter. Personal
Back tech support got back wit me today and they reproduced
the same thing.
Looks like I am back to using Cobian Backup. Wish Macrium
did not use proprietary formats. Seen that hostage
situation too many times. If it can't be read with Thunar,
it is a deal killer (I told their sales rep such and
their tech support that too).
So what you're doing then, is hunting for an "imaging" program,
one that captures both files and metadata, and then wishing
that when it stores its output, it only stored it as files
(without metadata) ?
You can't have one without the other. And a backup is no good,
if you "make it easy to lose bits and pieces".
If you want a file by file backup program, then find a file
by file backup program. But don't come back and complain that
"after a restore, it wouldn't boot".
Here's an idea for you, a silly idea, but an idea none-the-less.
1) Make a backup in image format (you know, one of those
evil proprietary formats).
2) Immediately do a second file-by-file backup, which only
collects the files and their data, and it collects no
permissions, attributes, or sufficient metadata to allow
booting. This second backup is solely for the purpose
of meeting your "access" requirement.
You could, for example, do (2) with Robocopy, and (1) with Macrium.
And for God sake, look up how to freeze a partition with VSS,
so when you run Robocopy, run it against a *frozen* copy of
C:, not against C: itself. That way, all the files will be
in a consistent state. This is the same thing that Macrium
does - it prefers to use VSS, for the consistency it brings
to backups of C: . And don't forget to release the shadow
after you're done with it. The system only has room for
64 of them.