not a direct help for your OPT problem
but a general though about misconception
it has been caused by:
Much too often we speak - with our
vendors and bosses and customers as well -
about backup requirements.
NOBODY HAS ANY BACKUP REQUIREMENTS,
WE ALL DO ONLY HAVE RESTORE REQUIREMENTS.
The backup is only a way to accomplish it,
backup is only a tool and maybe a method,
but not our target.
If you happen to make your vendor understand this,
the chances are better he will not matter
what name of backup - incremental or selective - you use.
regards
Juraj Salak
-----Urspr�ngliche Nachricht-----
Von: Alan Davenport [mailto:[EMAIL PROTECTED]]
Gesendet am: Donnerstag, 26. April 2001 21:03
An: [EMAIL PROTECTED]
Betreff: DSM.OPT override question.
One of our vendors insists that their product cannot be backed up
incrementally and insists a selective backup is required. We've
explained that a point in time restore is possible from incremental
backups however they still insist that is no good.
We've included their directory in our include/exclude list for the node
bound the the management class that has been set up especially for this
product's backups. The problem I'm having is that we have to use
preschedule/postschedule commands to shut down and restart the database
before/after the backups. We do not want to shut down the database for
the normal nightly incremental backup for the node.
I swear I read someplace that is possible to override the default
DSM.OPT file for a backup schedule for a command line but I cannot
remember where or how to do this. Can anyone help please?
I would like to have the dir in question excluded from the normal
incremental backup and for the selective backup include the needed
pre/post schedule commands and the directory in question with an include
statement.
Al
