Darrell----
Ref: smeserver-backup2-1.0.0-a2dmay.noarch.rpm
Trying it out on a live data SME7 fileserver (not public).
Updated over the top of existing Backup2 (e-smith version).
Inherited my old set of jobs (a very comprehensive set!) but
did not use them, other than to copy/paste the source path
into the FOREVER TOO SMALL form box (hint) in the alpha.
Have tried not to stress the alpha too much except to run
concurrent ie multiple realtime manually invoked jobs.
I haven't yet tried any jobs using the timer settings.
All to the W2kPro SP4 (workstation) work perfectly;~)
All to the MSS (a NAS type of box) don't... as you intimated.
Note: production SME6 using Backup2 (e-smith version) has
always successfully completed its own concurrent multiple
jobs to the MSS thing on its own overnight timered runs.
The MSS thing is a networked attached Maxtor Shared Storage
300GB box but unfortunately Maxtor spoiled a really good piece
of kit by inflicting a pointless 10/100Mbps interface on it instead
of a more real world gigabit interface;~/ Its proprietory setup
includes having no authentication as it's on my intranet. Though
I don't think my old MSS is of the new flavour ie a 'Plus' item:
http://www.maxtorsolutions.com/en/catalog/MSS_Plus/Anyway all concurrent jobs to the MSS end up as 'aborted'.
Seems to mess up SME7's /mnt/ area too... Other transfers
ie the good ones to the workstation appear to proceed slowly.
Attempting to manually delete the stuck mount in /mnt/ seems
to do the trick - transfers then get completed faster.
Intranet is an unmanaged gigabit switch (3com), I'm the only user.
Production SME6 (awaiting some courage to move to SME7).
Much prefer your new clean interface form;~)
Mystified by the 'explanatory' help note about the Disaster slot...
Think I know what you mean or mean to say but it's not clear.
The entry box on the form for the source path. It's always been
too small for the endless /home/e-smith... path mantra out to all
the iBays. When I then add the hierarchy of the 2TB RAID5 stuff
on to an iBay the deficit is somewhat risible. It might fit in if the
data slot for the source path were to be twice as long... (hint)
Typo: No compression dramitcally improves backup speed.
No compression dramatically improves backup speed.
What did you do to get it all working more quickly? I think
that Backup2 (the smeserver version not the e-smith version)
is working more quickly ie transfers complete in shorter periods.
Heartfelt thanks for the mod giving user choice of job names;~)
Are the logs rotated and so forth?
Could each job line on the interface include a URL to 'its' log?
Any chance that Backup2 might include some incremental or
otherwise rdiff sort of functionality? My site suffers massive hits
appropriate to the unnecessary duplication in day-to-day backups.
----best wishes, Robert