8:32am, Greg Smith wrote:

> Thanks to all for the replies.  I've read all the backuppc docs and 
> realized that hard links were an integral part of the design so I thought 
> the answer to my question would be "no" but thought I'd ask.  Since the 
> principle reason for using hardlinks in backuppc is to use space more 
> efficently, I was hoping that there was some hack (e.g., setting 
> HardLinkMax to 1) that would work but use more disk space.
>
> There is no h/w interface into the NAS other than two 1GB network links 
> (no iSCSI) and I don't think (I've got a call into the tech support to 
> confirm) that it supports NFS.  The only way that I know of mounting the 
> device is via samba/cifs.  Since both samba & cifs support hard links it 
> might be the device does too with some undocumented setting, we'll see 
> what tech support has to say.
>
iSCSI is software, not hardware ("i"nternet SCSI)--so an ethernet port is 
all you need (from a hardware standpoint).
If you can't get hard links over samba/cifs, I doubt you'll be able to have 
them through NFS. It sounds like the backing filesystem doesn't support 
them.
Just what make/model is this creature, anyway?


> In the meantime, I'm taking Dan's suggestion of a loopback fs.
>
loopback is what my money's on...

Paul

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to