amsamba and NTFS permissions
https://forums.zmanda.com/showthread.php?677-NTFS-File-Permissions tells me that (a) the community edition does not support star for Windows shares and (b) that GNU-tar does not preserve NTFS permissions? Is that still true? Couldn't I use amsamba as application and let its property "GNUTAR-PATH" point to the local "star"-binary? Would that work? Thanks, Stefan
Re: amsamba and NTFS permissions
Am 24.09.2014 um 20:04 schrieb Stefan G. Weichinger: > Couldn't I use amsamba as application and let its property "GNUTAR-PATH" > point to the local "star"-binary? > > Would that work? As far as I tested this naive approach it does NOT work this way. Different command line options etc. I will try to combine cifs-mounts and the amstar-application. Hints welcome. Stefan
Re: amsamba and NTFS permissions
Stefan, The "GNUTAR-PATH" property of amsamba is used only for creating the index and when restoring on local machine. amsamba use smbclient to create the tar file and restore on a CIFS share. Do smbclient support NTFS permissions? Jean-Louis On 09/24/2014 02:04 PM, Stefan G. Weichinger wrote: https://forums.zmanda.com/showthread.php?677-NTFS-File-Permissions tells me that (a) the community edition does not support star for Windows shares and (b) that GNU-tar does not preserve NTFS permissions? Is that still true? Couldn't I use amsamba as application and let its property "GNUTAR-PATH" point to the local "star"-binary? Would that work? Thanks, Stefan
Re: amsamba and NTFS permissions
Am 25.09.2014 um 16:12 schrieb Jean-Louis Martineau: > Stefan, > > The "GNUTAR-PATH" property of amsamba is used only for creating the > index and when restoring on local machine. In this case it will be restored on the local machine, but I have to check back with the guys at the site. > amsamba use smbclient to create the tar file and restore on a CIFS share. > Do smbclient support NTFS permissions? I think so but I am not sure from reading the manpage. It talks about the possibility to read ACLs (getfacl, stat) ... that should do it. But that is documented for the shell-style access it provides. In the options for tar (-T) I don't see any flags toggling it. Stefan
Re: amsamba and NTFS permissions
Additional info: they can't use the A/ZManda-Windows-Client because the NTFS-share is shared from a storage/SAN and not from a dedicated MS Windows Server. So we have to solve that on the side of the linux server, I assume. Stefan
Re: amsamba and NTFS permissions
Am 25.09.2014 um 17:21 schrieb Stefan G. Weichinger: > > Additional info: > > they can't use the A/ZManda-Windows-Client because the NTFS-share is > shared from a storage/SAN and not from a dedicated MS Windows Server. > > So we have to solve that on the side of the linux server, I assume. Does nobody here successfully do that with amanda?
Re: amsamba and NTFS permissions
"Stefan G. Weichinger" writes: > Am 25.09.2014 um 17:21 schrieb Stefan G. Weichinger: >> >> Additional info: >> >> they can't use the A/ZManda-Windows-Client because the NTFS-share is >> shared from a storage/SAN and not from a dedicated MS Windows Server. >> >> So we have to solve that on the side of the linux server, I assume. > > Does nobody here successfully do that with amanda? You supposedly could run A/ZManda-Windows-Client on a Windows client (one that remotely mounts the NTFS share). It will have a cost because the files are traveling the network twice (from NTFS server to Windows client and from Windows client to Amanda server). Your Windows client could be some virtual machine that is started only for back-up purposes (a virtualbox running from Amanda server, so you "cut off" one network transfer). That is ugly. It depends what is the NAS/storage amde of. Best regards, Olivier --
RE: amsamba and NTFS permissions
We have several SANS here. I'm not their manager so I'm not able to really be specific as to brand or whatnot, but I know one of them is setup to replicate itself off-site to a backup SAN, so any hosts storing files on it get those backed up for "free" without Amanda. Another SAN we have is ISCSI, and for that one, the VMs and hosts using that SAN are all on am Infiniband dedicated network segment which my Amanda server can't reach anyway. For all of those, one host <-> one mount, and I have Amanda configured to backup the files via the one host that mounts it. As the ISCSI SAN is on a restricted-access, dedicated Infiniband 56G network segment, and the Amanda traffic is going out a normal 1G Ethernet interface, the "double-the-traffic" argument doesn't hold up here. If the windows machine can expose the desired files with a secondary share, you can use Amanda to backup the file content. I don't expect that to have any NTFS or registry information, though. I have several windows clients which, for reasons of elderly OS/crappy application software, use such a thing as their only backup process. -- Joi Owen System Administrator Pavlov Media, Inc -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Olivier Nicole Sent: Thursday, October 02, 2014 3:58 AM To: s...@amanda.org Cc: amanda-users@amanda.org Subject: Re: amsamba and NTFS permissions "Stefan G. Weichinger" writes: > Am 25.09.2014 um 17:21 schrieb Stefan G. Weichinger: >> >> Additional info: >> >> they can't use the A/ZManda-Windows-Client because the NTFS-share is >> shared from a storage/SAN and not from a dedicated MS Windows Server. >> >> So we have to solve that on the side of the linux server, I assume. > > Does nobody here successfully do that with amanda? You supposedly could run A/ZManda-Windows-Client on a Windows client (one that remotely mounts the NTFS share). It will have a cost because the files are traveling the network twice (from NTFS server to Windows client and from Windows client to Amanda server). Your Windows client could be some virtual machine that is started only for back-up purposes (a virtualbox running from Amanda server, so you "cut off" one network transfer). That is ugly. It depends what is the NAS/storage amde of. Best regards, Olivier --
Re: amsamba and NTFS permissions
Am 06.10.2014 um 23:51 schrieb Joi L. Ellis: > We have several SANS here. I'm not their manager so I'm not able to > really be specific as to brand or whatnot, but I know one of them is > setup to replicate itself off-site to a backup SAN, so any hosts > storing files on it get those backed up for "free" without Amanda. > > Another SAN we have is ISCSI, and for that one, the VMs and hosts > using that SAN are all on am Infiniband dedicated network segment > which my Amanda server can't reach anyway. For all of those, one > host <-> one mount, and I have Amanda configured to backup the files > via the one host that mounts it. As the ISCSI SAN is on a > restricted-access, dedicated Infiniband 56G network segment, and the > Amanda traffic is going out a normal 1G Ethernet interface, the > "double-the-traffic" argument doesn't hold up here. > > If the windows machine can expose the desired files with a secondary > share, you can use Amanda to backup the file content. I don't expect > that to have any NTFS or registry information, though. I have > several windows clients which, for reasons of elderly OS/crappy > application software, use such a thing as their only backup process. sorry for the late reply. Thanks for your posting ... they solved it via plain amsamba-DLE already. And it works ;-) Stefan
