#Multi_Backer update
6 messages in this thread
Attention to those of you who may be using Multi_Backer V 1.0, the
Quarterback macro I wrote to speed up multi-disk backups to tape.
My upgrade to QB 6.0 just came in the mail and I've found a few
differences between QB version 6.0 and version 5.0.4 that impact
Multi_Backer.
First, there is a new backup option which can be set to either "Complete"
or "Selective". For QB 6.0 the default seems to be "Complete" but to make
Multi_Backer work you need to set "Selective". The best way to do this is
to add this line to the Multi_Backer macro:
SetBackupOptions Selective
Add it after line 96 which is "SetBackupOptions VerifyDataOff".
Second, QB 6.0 now expects you to put your QB macros into the drawer
"Macros" which is in the QB drawer. That is what you can do with your
macros like Daily_1, Daily_2 and Weekly, but don't put Multi_Backer in
there. When a QB macro calls another ARexx macro, ARexx will not look for
the macro in the "Macros" drawer. So you need to leave the Multi_Backer
macro in the same drawer as Quarterback.
I will be uploading a new version of Multi_Backer (MLTBAK.LHA) in a few
weeks after I have verified that there are no other hidden problems.
//
\X/ Amiga or bust! Gary Bonnstetter, Bonnsoft
Gerald,
have you tried using the multiple directory assign feature of AmigaDOS
2.1? I've got my c:, l:, devs:, rexx:, etc. ad nauseum spread across
three directories and I haven't seen ARexx choke.
It goes like this:
Assign Rexx: Sys:Rexx Sys:Rexx/Keep Sys:Rexx/New
It works like a champ. BTW, the neat thing with the above example is
that all the new stuff, if you use the assigned name, ends up in the
Rexx:New directory. I move it after it proves safe.
Brian
bjbart@watserv.ucr.edu
Brian,
I have thought about using the multiple assign feature but I haven't
gotten around to trying it yet.
The problem I was pointing out was mostly a documentation problem though.
I had described an easy way to install my Multi_Backer macros and the new
Quarterback now uses a different directory setup.
I had told Multi_Backer users to put all of the Multi_Backer macros in the
Quarterback directory, then the new Quarterback 6.0 came out with it's new
Macros directory. And the new QB said to put all your QB macros in their
new Macros directory. But the second part of two part macros like
Multi_Backer cannot go into the Macros directory because ARexx will not
look in the Macros directory without doing something extra like what you
suggest.
So now I need to update my Multi_Backer installation documentation to
describe how to make Multi_Backer work with QB v5 or v6. I've seen enough
questions on the nets from people who cannot get normal assigns to work,
so I'm not sure I want to suggest using a multiple assign for REXX:.
//
\X/ Amiga or bust! Gary Bonnstetter, Bonnsoft
Gary,
as always, it is up to the author. I do suggest that you give thought
to mentioning directory paths. It seems strange that many programs are
wandering off into requiring seperate ARexx macro directories when one of
the guiding principles of ARexx is interprogram communication. It would
be difficult to construct scripts that call one another if one has to
recall that the QB ARexx scripts are in the macros directory of whereever
Quarterback lives while XYZ's scripts are in the Scripts directory of
where XYZ lives. If we are going to strew this code all over God's
creation, at least use directory paths to link them into a chain.
Just a thought.
Brian
bjbart@watserv.ucr.edu
Gary,
Do you have a sample QB macro that untags certian files/directories before
it performs a backup?
Also, QB 5.0.2 hung when it hit a drawer with hard links in it (even when
the drawer was not selected for backup. Have you encountered anything
like this before?
Jim Philippou
Gary,
I haven't looked at your "Multi_Backer" macro, but just in case you didn't know
about it you can use the "ProgVersion" AREXX command in Quarterback to
determine which version of Quarterback you are running under, and take
appropriate steps depending upon the version. That way you can have one macro
execute differently on different versions of Quarterback.
Also, the SetBackupOptions command can take multiple parameters. For example,
you can use a single line to set two options:
SetBackupOptions Selective VerifyDataOff
(Alternatively, you could set the backup type to Complete, and not execute the
"Proceed" command when running under Quarterback 6.0 or later, since the file
selection display will be bypassed in that case.)
We debated here when we added the Complete/Selective option whether or not to
make Selective the default (giving backwards compatibility to AREXX users) or
Complete the default (which would be more convenient to non-AREXX users). In
the end we decided to make the Complete the default, even though it would cause
minor problems with existing AREXX macros, since most of our users don't use
the AREXX feature of Quarterback.
The switch to a separate "Macros" drawer was a much-requested feature, and
helps tremendously to reduce the clutter in the Quarterback directory.
I regret the problems these changes caused you. Just wanted to let you know
that they were not done lightly–they were both done for a reason.
James Bayless
Central Coast Software
A division of New Horizons Software, Inc.