Conference cookie::archive_backup

>1).  The documentation states that you can only have up to 8 objects per 
>save request.  What governs this restriction?  Is this just for DCL or for 
>GUI too.  Customer said he put in 10 and it took it.

8 is DCL restriction. See 361.4

>2).  Is there a way to turn-off cataloging altogether?  Customer wanted 
>to be able to only have it keep certain information during saves which 
>we know can't be done.  Kind of like a brief listing.

There is a maintenance logical which can be turned on, but we sure don't 
recommend the customer to use it for production environment.  Without
cataloging, archive backup product is not really valuable, right? 

>3).  Can you switch the scheduler job from detached mode to batch mode?  
>It appears that we get a RNF (Record not found) error when doing this.

We have never tried it here. We don't support it.  Do it at your own risk
type of things.  Do we gain anything from making it in batch mode?  In the
future, we probably have to get rid of DECscheduler altogether, because
CA owns it now. Then we *probably* will use batch queue mechanism (like the
one done for ABS OMT).  

>4).  If we use the DAILY_FULL_WEEKLY scheduling interval, what is the best 
>way to have it start
>on another day after its in the middle of the interval.  In other words, 
>we've started this running
>with the FULL on Sunday, get one DAILY done on Monday and decide 
>we want to restart the interval
>on Wednesday.  Do we use the /START_TIME?  If so, will it restart at 
>the beginning of the interval
>with a FULL and is Tuesdays incremental dropped?

I don't think we have a readily available mechanism to do what is said here.
Let me think about it. Someone else may have creative solutions???

>5).  The customer wants to use the SIMULTANEOUS sequence_option 
>(even though its not recommended, of
>course).  What is this going to do for him?  What he'd like to do is 
>have backups to different objects
>going on to different jobs from the same SAVE request.  
>This possible or is something single threaded
>(besides the SLS/MDMS RQ process) that it can't be done.

Simultaneous options is not implemented yet (in the release notes).  When it
is implemented, it releases all threads for the save simultaneously, which
may put the system under resource constraints....

I did not quite understand what exactly was asked by " What he'd like to do is 
have backups to different objects
going on to different jobs from the same SAVE request".  Can you give an
example?

A request from me ....

Please use 80 column width, so that we can read the entire notes without
going into the wide screen mode....


Masami

Greetings...

Just when you think you know it all, them customers start reading the docs and
ask more questions 8*).

Heres what we got stuck on:

1).  The documentation states that you can only have up to 8 objects per save
request.  What governs this restriction?  Is this just for DCL or for GUI too. 
Customer said he put in 10 and it took it.

2).  Is there a way to turn-off cataloging altogether?  Customer wanted to be
able to only have it keep certain information during saves which we know can't
be done.  Kind of like a brief listing.

3).  Can you switch the scheduler job from detached mode to batch mode?  It
appears that we get a RNF (Record not found) error when doing this.

4).  If we use the DAILY_FULL_WEEKLY scheduling interval, what is the best way
to have it start on another day after its in the middle of the interval.  In
other words, we've started this running with the FULL on Sunday, get one DAILY
done on Monday and decide we want to restart the interval on Wednesday.  Do we
use the /START_TIME?  If so, will it restart at the beginning of the interval
with a FULL and is Tuesdays incremental dropped?

5).  The customer wants to use the SIMULTANEOUS sequence_option (even though
its not recommended, of course).  What is this going to do for him?  What he'd
like to do is have backups to different objects going on to different jobs from
the same SAVE request.  This possible or is something single threaded  (besides
the SLS/MDMS RQ process) that it can't be done.

Appreciate the help.  This is Glaxco ... big SLS user now and would be a good
reference shop if we can get'em running.  We're looking at sending out 2.1 to
soon.

Ted

>Simultaneous options is not implemented yet (in the release notes).  When it
>is implemented, it releases all threads for the save simultaneously, which
>may put the system under resource constraints....
>
>I did not quite understand what exactly was asked by " What he'd like to do is 
>have backups to different objects
>going on to different jobs from the same SAVE request".  Can you give an
>example?

Let me rephrase this....Customer is backing up 3 disks to a TL820 with 3
drives in it.  He wants to use only 1 save request.  When the save request
kicks off it will start on the first disk to the first tape drive.  It then
starts the second disk on drive 2 and so on.  It would have to create a 
3 tape volume set but all 3 drives get used at the same time.  Sounds like
this is what you are going to do.  

Ted

    
    Your description is correct about simultaneous.  That's the intention.
    Since it's not implemented (or working), I cannot say for sure if it
    will work that way when it's done in the future....
    
    You have to set #of drives field in execution env to allow maximum #
    of save to have enough # of drives for simultaneous operation.
    
    Masami