Topic: backup2 contrib

[icpix]

Could the 'backup2' (aka 'backup2ws' in the era of SME6) contrib be
tweaked in any way so as to run (much) more quickly? Yes, it does
a lot of detail shifting per file but it's really quite slow in comparison
with just plain old manual file movements typically over my intranet.
No, I don't have any figures but I'd like to see backup2 with a turbo
button or limiter disable;~) The hardware is pretty decent here at
the moment but there's an awful lot of backup to shift...

Backup2 moves all the files each time - whether or not amended.
I've always used its predecessor (backup2ws) for the production SME6.
The new SME7 will take over when the code is cleared for gold, so  
I'd like to get my new backup methodology resolved beforehand.

I've had a pretty inexpert bash trying some of the competition but always
return to my old favourite despite it showing its age (somewhat like me).

Turbo edition of backup2 with added bandwidth saving capability?

----best wishes, Robert

[arnoldob]

Modify your backup job and change the compression setting. "0" will disable compression and make the backup quicker. I think Darrell May maintains backup2ws, you might wish to raise a feature request in bugzilla contribs section.

[icpix]

arnoldob----
SME7 has two 3.4GHz Xeons with 4GB of RAM.
Its 'only' task is file serving a single user over an
otherwise unoccupied gigabit unmanaged switch.
Compression hasn't been really significant.
Bottleneck seems to be the way it does the
multiple file transfer across the intranet.
I didn't think this was a bug (ie bugzilla)
more of a wishlist or feature request!
----best wishes, Robert