Hello Victor, >1) For a real system, the docs advice to use AutoLog On. Can this backups >be taken to an external backup like a tape, or does this imposes overheads >to the system?
If you make sure, that the database finished creation of the log backup files in question, e.g. by stoping AutoLog or by switching to another Log Backup Medium (pointing to another location), you can do whatever fits your backup scheme. From that point on it are just files. >1.1) Case AutoLog is on, is there any need to take interactive log >backups? No. >2) In a recovery procedure, which log backups do we need to recover? Do we >need to know exactly one which was taken before the recovered >complete/incremental backup? The database kernel will respond with an error, if you try to restore a not matching log backup. So if you are not going to look into the backup history or into the label of the backups, you have to test the available backups until you finally find the first matching log backup. >2.1) Do we need to execute a recover_start for each log version file? Or >is this procedure automatic after the recover_start of the first version? See 2.2. >2.2) According to the doc "Backup and Recovery with the Database Manager >CLI:...", in a Recovery procedure, after the recovery of the version 001 of >the Logs (recover_start logsave LOG 001), a recover_replace and a >recover_ignore are executed: > - recover_start logsave LOG 001 > - recover_replace logsave /usr/sapdb/log 002 > - recover_ignore >2.2.1) What's does recover_replace and recover_ignore? >2.2.2) What does it really means the "Media change" of the log backup on >the recovery process? recover_start logsave LOG 001 -> /usr/sapdb/log.001 is recovered recover_replace logsave /usr/sapdb/log 002 ->/usr/sapdb/log.002 is recovered recover_replace logsave ... 003 -> ....003 is recovered ... recover_ignore <- only needed if no log information can be found on the log volume. >3) Should each backup use a different medium, or can a medium hold more >than one backup (of the same type)? A medium is basically a combination of a logical name, a file system path and the device type. If your backup medium points to a tape, you should replace the tape, otherwise the previous backup is overwritten. If your medium points to a file and is not for Log backups, you can make a backup only, if the file does not exist or if you specify the overwrite flag of the medium. If your medium points to a file and is for log backups, you can reuse it without hesitation, as a increasing number is added to the file name. >4) Is it possible to archive version files with the dbmcli, or any other >SAP client? Currently only, if you use an external backup tool like NetWorker, TSM, Backint for Oracle or Backint for SAP DB. Best Regards, Tilo Heinrich SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
