Robin,

I forgot that compression is turned on by default on the client. I have turned it off and restarted svpmgr. All compression is already off on the filer side. I'm restarting one of the file systems and we'll see how it behaves with tonight's nightly backups.

Thanks,

Jeff

On Tue, Jun 26, 2012 at 3:33 AM, Robin Mesotten robin.mesotten@gmail.com wrote:

Jeff,

OSSV can do compression on its transfers. At high transfer speeds this could hog up the CPU. You can disable/enable this globally or for each OSSV relation separate.

Also In-line compression on the volume can cause a high load on the CPU at high transfer speeds. For the volume compression you could change it to post-processing.

-- Greetings, Robin Mesotten

On Tue, Jun 26, 2012 at 1:48 AM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:

...

Greetings,

I'm running OSSV3.0 on some RH5.4 clients to a 6040 NearStore running 8.1 with 10G networking.  The process works OK, but when I have an OSSV transfer running, the system load on the filer goes to 100%, it starts behaving very sluggishly, and the regular filer to NearStore backups start running very long, in some cases 2-3 days when they should complete in no more than 6 hours.

I've gone through the installation and best practices guide and don't see anything about tuning the secondary.  I've looked at sysstat during the load times and disk and network throughput are hardly above 60 MB/s.  I know I can try throttling the backup, but it doesn't appear to be a throughput or bottleneck issue.  Has anyone else seen this or is there anything I can do to help this?

Thanks,

Jeff

-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611 _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters