IDS and TSM
Posted in 2005
Topics: Installation, Setup & Upgrades, Logging & Checkpoints
hi, i've installed TSM to backup our systems, and i'd like to use it for backing up IDS. i've setup all correctly ans it works fine. i just want to know how to manage the logical logs ? my logical logs are backed up, but must i write a script to delete the backed up logs when necessary ? thanks.
Yeap. 1) Say, back up your logical logs to disk file, then backup up that same file to TSM at any time(s). Yes, you need some scripting to manage all the stuff. 2) If you need a full "on line" solution, you should take a look at Tivoli Data Protecion for Informix. Check: http://www-306.ibm.com/software/tivoli/products/storage-mgr-db/ Hope it helps. -----Mensaje original----- De: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] En nombre de Franck ABELLI Enviado el: Miércoles, 27 de Abril de 2005 12:54 p.m. Para: ids@iiug.org Asunto: IDS and TSM [4835] hi, i've installed TSM to backup our systems, and i'd like to use it for backing up IDS. i've setup all correctly ans it works fine. i just want to know how to manage the logical logs ? my logical logs are backed up, but must i write a script to delete the backed up logs when necessary ? thanks. AVISO LEGAL: Esta información es privada y confidencial y está dirigida únicamente a su destinatario. Si usted no es el destinatario original de este mensaje y por este medio pudo acceder a dicha información por favor elimine el mensaje. La distribución o copia de este mensaje está estrictamente prohibida. Esta comunicación es sólo para propósitos de información y no debe ser considerada como propuesta, aceptación ni como una declaración de voluntad oficial de REPSOL YPF S.A. y/o subsidiarias y/o afiliadas. La transmisión de e-mails no garantiza que el correo electrónico sea seguro o libre de error. Por consiguiente, no manifestamos que esta información sea completa o precisa. Toda información está sujeta a alterarse sin previo aviso. This information is private and confidential and intended for the recipient only. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and shall not be regarded neither as a proposal, acceptance nor as a statement of will or official statement from REPSOL YPF S.A. and/or subsidiaries and/or affiliates. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Hi, on IDS side you do not need to do additional things. Once logical logs are backed up they are eligible for cyclical overwriting and thus they will be re-used. On Storage Manager (SM) side things are usually handled by a concept called "expiration policy". This can be rather elaborate and how you define and implement it depends on your requirements and on the capabilities of the SM in use. I do not know TSM well enough to explain what is possible here and how to do it. Generally the expiration policy defines, how long backups need to be kept on backup media before the media becomes eligible for re-use (overwriting existing backup data which has expired). The SM will then "automatically" expire things according to the defined policy. For IDS you should at least keep in mind, that you should keep all the log files that are necessary for restore of the physical dbspace backups. Now that again depends on the physical backups themselves: E.g. - for restore of a "whole system backup" you do not need any logical logs. However, if you want to roll forward transactions that were done after the whole system backup, you need the logs that were backed up afterwards. - for restore of a non-"whole system backup" you always need logical logs to restore to a consistent system. Even logs that were backed up BEFORE the physical dbspace backup was done may be needed (to be able to rollback open transactions that started before the physical backup). Apart from this it usually is also possible with SMs to manually expire backup objects. Actual 'delete' (like "rm") usually is not necessary. All the above applies when you backup the logical logs directly to the SM. If you are doing things differently (i.e. some manual backup to file and later manual backing up the file to SM), then you have to figure out something yourself ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management forum.subscriber@iiug.org wrote on 27.04.2005 17:53:56: > hi, > i've installed TSM to backup our systems, > and i'd like to use it for backing up IDS. > i've setup all correctly ans it works fine. > i just want to know how to manage the logical logs ? > my logical logs are backed up, but must i write a script > to delete the backed up logs when necessary ? > > thanks.
Related threads
- Re: Re: Crash course for an Oracle DBA
- Re: IDS 7.30 do not start - NT
- Re: IDS 10 erratic run times
- Client SDK