|
Re: [ADSM-L] TSM Database Backup Trigrer...
2008-10-24 05:49:30
Look at the "h define dbb", you can only specify a devclass, so a
scratch volume would be used.
(Note that you could choose different devclasses for fulls and
incremental : tape devclass for fulls, and file devclass for
incrementals is the idea...).
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
Kiran a écrit :
Thanks for the information, But when db backup triggers automatically db backup
in which tape it will write the database??
Regards,
Kiran M
DQ ENTERTAINMENT LTD
kiran AT dqentertainment DOT com
Mobile :+919246395809,+919849725836
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Erwann Simon
Sent: Friday, October 24, 2008 2:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Database Backup Trigrer...
Hi Kiran,
Of course, enabling automatic backups of the db by a trigger does not
prevent from ding manual backups. Manual backups (or planned ones) are
still the recommanded way to backup the db. The trigger should only be a
safety valve.
It's not mandatory to define a db backup trigger when you enable the
rollforward mode of the recovery BUT it's higly advisable to do so !
Before enabling this rollforward mode, ensure that you have enough space
in you recevery log to keep all your transactions between two planned db
backups (see Q LOG F=D : Cumulative Consumption (MB) and Consumption
Reset Date/Time, and see RESET LOGCONSUMPTION command).
|
|
|
