I'm working with someone who has a situation reversed from what I am accustomed, a single Solaris system that needs to be backed up to a PC network. The Solaris system has no tape unit. The PC side h
--On Wednesday, October 15, 2003 23:53:13 -0400 Jon LaBadie <jon AT jgcomp DOT By 'PC', are you implying MS Windows, or are there PC Linux hosts on the network? If it's strictly MS Windows and one So
Author: "Jim" <jim.mozley AT exponential-e DOT com>
Date: Thu, 16 Oct 2003 13:53:13 +0100
You could ftp a single file to the PC (e.g. using perl and net::ftp is easy). Of course you would need IIS or something that provided an ftp server. This might be less effort than getting samba goin
A follow-up to my original query now that I have more info. Found out today that the storage to which the client refered is a "Snap Server" brand of NAS. It was configured only to do SMB protocol. Ho
Author: "Dana Bourgeois" <em-lists AT netgods DOT us>
Date: Sat, 18 Oct 2003 00:12:02 -0700
I'd worry about write problems across the NFS link. Network Appliances could have this problem but in practice, I've never seen it. I have seen lots of problems trying to move gobs of data across NFS
Hi Jon, I may have missed an earlier post, but what kind of network is between the two devices (server you are wanting to back up & Snap storage) ? If you have 10Mbps ethernet hub, then 3.5MB/sec is
Author: Eric Siegerman <erics AT telepres DOT com>
Date: Mon, 20 Oct 2003 16:40:33 -0400
NFS-2 write performance is lousy, since the server needs to effectively fsync() on every write() call before it returns status to the client. (I suspect that one tends to notice this with large files