Hi Andy, you are quite right, one should never ignore vendors backup requirements, I agree with you this vere a bad idea. Maybe having been misunderstood, I will repeat myself: In addition to your statements I still propose to speak about restore requirements inspite of backup requirements whenever possible. As trivial and natural this change sounds to be, it is a major paradigm change which easily leads to better understanding of real requirements, even in the case of experienced users and vendors. Can you suggest/imagine any backup requirement where there is no restore requirement behind it? And be they implicit/instictive only, restore requirements are what enforces all backups. So why most of us always speak about backup requirements but almost never about restore requirements? For me this is a historical misconception only. Restore requirements enforce backup recommendations, the opposite is not true at all, there is a one-way dependency between those two. Backup requirements defined per se easily turn to be either superfluos or even insufficient when later cross-checked against actual restore requirements. regards Juraj Salak P.S. by the way - *SM is one of very few products which support - through management classes - this way of thinkink -----Ursprüngliche Nachricht----- Von: Andy Raibeck [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 27. April 2001 16:34 An: [EMAIL PROTECTED] Betreff: Re: AW: DSM.OPT override question. If the product's vendor is making a recommendation about how to back up (or how not to back up) their product, it's probably a good idea to heed that recommendation. You do not want to be in a position where you need to restore, and the vendor can not help because you did not follow their recommended backup procedure. That said, it would be a good idea to ask the vendor why they make that recommendation, so that you can evaluate its technical merits. In this case, the vendor may have a very good reason for recomending against incremental backups; on the other hand, perhaps they do not understand what is meant by "incremental" backup, so again, a discussion as to why they make the recommendation is a good idea, so that all parties understand the issues. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "The command line is your friend" sal Salak Juraj <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/26/2001 11:06:16 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: AW: DSM.OPT override question. 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
