Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
16.05.2017, 01:32, Holger Parplies kirjoitti: Hi, Michael Stowe wrote on 2017-05-15 09:58:08 -0500 [Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions]: On 2017-05-15 05:20, Tapio Lehtonen wrote: [...] The share C is shared to network and user backuppc has full rights. [...] There are a few important things to understand here. One is that not all transport mechanisms are created equal when backing up Windows systems. what a nice way to say that :-). I'm not a Windoze expert at all, but I vaguely remember you (Michael) stating in the past that there is a difference between the default C$ share and an explicitly created share ... assuming my memory is correct, might that be the issue here? I.e. does anything change if you (Tapio) explicitly create a share and use that (or use the C$ share if you were previously using something different)? I created a new share Users, for users home directories. I gave permissions to that share to backuppc-user. That seems to have done the trick, now the home directories are backed up including the subdirectories therein. Seems there is a difference with the pre-existing C-share and a share I create myself. Now only the users home directories are backed up, not other files, but home directories are the important ones. I think I will do without backing the OS-files and installed programs. At any rate, these reasons are why I personally switched to a combination of rsync and vshadow (to handle open files) and put together a package to install the proper files on the client side. If I were in the unlucky situation of having to deal with Windoze hosts, that is what I would use. From what I have read on this list, it seems to be the best choice. Regards, Holger -- Tapio Lehtonen OSK Satatuuli <>-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
Hi, I'm maybe late to the discussion, but to the topic of premissions. Always set the user account performing backup (whether using smbclient or cwrsync) to be member of "Backup Operators". It helps a lot. -- Best Regards Vladislav Kurz -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
Hi Michael Huntley, Michael Stowe, and everybody, I overlooked your reply and only now saw it in the archives - also, I don't have your private mail address visible there, to reach out for a "thanks" privately: > Stowe has been around forever. I suggest you read his entire blog - > very entertaining. > > Here's his BackupPC stuff: > > http://www.michaelstowe.com/backuppc/ Thanks a lot for the pointer; testing soon! Cheers, Alexander On 2017-05-17 09:07 AM, Alexander Kobel wrote: > Hi Michael, > > On 2017-05-15 06:32 PM, Holger Parplies wrote: >> Hi, >> >> Michael Stowe wrote on 2017-05-15 09:58:08 -0500 [Re: [BackupPC-users] >> Backing up Windows 7 Pro, not enough permissions]: >> [...] >>> At any rate, these reasons are why I personally switched to a >>> combination of rsync and vshadow (to handle open files) and put together >>> a package to install the proper files on the client side. [...] > > would you mind to share that package, in whatever state it is? I use a > similar setup (Cygwin + rsync over SSH), but getting it to run is less > than intuitive. > > I yet have to find a simple and fool-proof way of installing (don't talk > about keeping up-to-date even) that combination. It takes me less and > less time every time I do it (every few months), but it's still a pain. > IIRC, last time I had to refresh my mind on > - how to enable a cyg_server (appx. a.k.a. root) account with the proper > access rights > - how to open port 22 on the firewall, and (if need be) respond to pings, > - how to make the SSH server accept the BackupPC server pubkey (because > cyg_server has no home by default). > And that's even without vshadow. > > Certainly not an approach that I can load off to the average Joe user, > say, "download and install ..., and I do the BackupPC server setup > remotely". > > > Cheers, > Alexander -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
Stowe has been around forever. I suggest you read his entire blog - very entertaining. Here's his BackupPC stuff: http://www.michaelstowe.com/backuppc/ I decided to use vssadmin and wmic to manage restore points. I then use Cygwin and a bash script to mount the shadow copy for backup. It's kludged together but works for me. Cheers! mph On 2017-05-17 06:07, Alexander Kobel wrote: > Hi Michael, > > On 2017-05-15 06:32 PM, Holger Parplies wrote: Hi, > > Michael Stowe wrote on 2017-05-15 09:58:08 -0500 [Re: [BackupPC-users] > Backing up Windows 7 Pro, not enough permissions]: > [...] At any rate, these reasons are why I personally switched to a > combination of rsync and vshadow (to handle open files) and put together > a package to install the proper files on the client side. [...] would you mind to share that package, in whatever state it is? I use a similar setup (Cygwin + rsync over SSH), but getting it to run is less than intuitive. I yet have to find a simple and fool-proof way of installing (don't talk about keeping up-to-date even) that combination. It takes me less and less time every time I do it (every few months), but it's still a pain. IIRC, last time I had to refresh my mind on - how to enable a cyg_server (appx. a.k.a. root) account with the proper access rights - how to open port 22 on the firewall, and (if need be) respond to pings, - how to make the SSH server accept the BackupPC server pubkey (because cyg_server has no home by default). And that's even without vshadow. Certainly not an approach that I can load off to the average Joe user, say, "download and install ..., and I do the BackupPC server setup remotely". Cheers, Alexander -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
Hi Michael, On 2017-05-15 06:32 PM, Holger Parplies wrote: > Hi, > > Michael Stowe wrote on 2017-05-15 09:58:08 -0500 [Re: [BackupPC-users] > Backing up Windows 7 Pro, not enough permissions]: >[...] >> At any rate, these reasons are why I personally switched to a >> combination of rsync and vshadow (to handle open files) and put together >> a package to install the proper files on the client side. [...] would you mind to share that package, in whatever state it is? I use a similar setup (Cygwin + rsync over SSH), but getting it to run is less than intuitive. I yet have to find a simple and fool-proof way of installing (don't talk about keeping up-to-date even) that combination. It takes me less and less time every time I do it (every few months), but it's still a pain. IIRC, last time I had to refresh my mind on - how to enable a cyg_server (appx. a.k.a. root) account with the proper access rights - how to open port 22 on the firewall, and (if need be) respond to pings, - how to make the SSH server accept the BackupPC server pubkey (because cyg_server has no home by default). And that's even without vshadow. Certainly not an approach that I can load off to the average Joe user, say, "download and install ..., and I do the BackupPC server setup remotely". Cheers, Alexander -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
Hi, Michael Stowe wrote on 2017-05-15 09:58:08 -0500 [Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions]: > On 2017-05-15 05:20, Tapio Lehtonen wrote: > > [...] > > The share C is shared to network and user backuppc has full rights. > > [...] > > There are a few important things to understand here. One is that not > all transport mechanisms are created equal when backing up Windows > systems. what a nice way to say that :-). I'm not a Windoze expert at all, but I vaguely remember you (Michael) stating in the past that there is a difference between the default C$ share and an explicitly created share ... assuming my memory is correct, might that be the issue here? I.e. does anything change if you (Tapio) explicitly create a share and use that (or use the C$ share if you were previously using something different)? > At any rate, these reasons are why I personally switched to a > combination of rsync and vshadow (to handle open files) and put together > a package to install the proper files on the client side. If I were in the unlucky situation of having to deal with Windoze hosts, that is what I would use. From what I have read on this list, it seems to be the best choice. Regards, Holger -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
On 2017-05-15 05:20, Tapio Lehtonen wrote: > Server is Debian 8.7, backuppc version 3.3.0-2+deb8u1 > > Backing up Linux computers works. > > Have not been able to backup Windows 7 Professional. I have on windows > local backuppc user, that user belongs to groups administrator and > backup operator. The share C is shared to network and user backuppc > has full rights. > > Still the home directories of other users are empty. Only > C/Users/backuppc has content. > > So, Backuppc server can read files from the client, but not all files. > Seems I can not figure any more ways to give permissions to backuppc. > > That Windows 7 is client in workgroup, the server is a Linux host > running Samba 4.2.14. Maybe this is not relevant. There are a few important things to understand here. One is that not all transport mechanisms are created equal when backing up Windows systems. From what you've said, I deduce that you're using samba to back up Windows 7, which is important, because it has permission and semantic implications. First, permissions. I note that Windows permissions can be complex and there's no inherent concept of a "root" account. I note that shares permission and files permission are different things and must both be granted for samba to be able to read these files. I note that Microsoft has recently added permissions that block smb/cifs from accessing certain system files or performing actions that might be considered "unsafe," which may be an issue, depending on what you're attempting to back up. Second, is file semantics. Windows isn't particularly good about noting what's wrong (and this also varies by transport) so that it's possible to get what looks like a permission error when what's actually happening is a semantic error. Here I note that Windows can have files open exclusively (Outlook files and database files are common examples) which means that no other process, including backup processes, are allowed to read these files and are denied access. Before leaving the semantic topic, I'll note that Windows also has the concepts of directory junctions and redirection; since that doesn't appear to be the case for something in your own directory. But don't expect to be able to back up your own registry files directly through samba, either. At any rate, these reasons are why I personally switched to a combination of rsync and vshadow (to handle open files) and put together a package to install the proper files on the client side. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
