Any more suggestions on the below query please.

I want to know the difference between normal and roll forward mode of
recovery log

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
Mark Stapleton
Sent: Wednesday, October 01, 2008 5:34 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Antwort: Re: Recover log Mode...

It won't do you any good to change log modes at the time of a disaster.
The recovery log must be in rollforward mode since the last database
backup in order for there to be any content to the log.

--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Kiran
> Sent: Tuesday, September 30, 2008 11:24 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Antwort: Re: Recover log Mode...
>
> Thanks for the information.
>
> But My idea is just to change the mode of recovery log to roll forward
> for
> point- in-time recovery in terms of database corruption situation
only.
>
> And I will do my dbbackup's and extending of db and log will be
> manual,not
> automation.
>
> As you said I run daily incremental backups for 6 million files and I
> will
> have daily full backup of db backup which my environment needs.
>
> Suggest me.
>
> 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 TSM
> Sent: Tuesday, September 30, 2008 8:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Antwort: Re: Recover log Mode...
>
> be vary careful about activation of rollforward
>
> it depends on your tsm server environment, but backup of lets say 4 to
> 5
> million objects may fill up log and
> your system triggers dbbackup or log-spaceexpansion.
>
>
> - define dbbackuptrigger (incr and full) and spacetriggers
>       - incr dbbackup on disk (2 or 3 before getting to full backup
> deviceclass)
>       - full on tape
> - maximum size of log is 13500 MB, do not define maximum size for log,
> you
> may need some additional space, if log
>   runs unexpectly full
>
> with best regards
> stefan savoric
>
>
> Disclaimer:
> This email message (including attachments if any) may contain
> privileged, proprietary, confidential information, which may be exempt
> from any kind of disclosure whatsoever and is intended solely for the
> use of addressee (s). If you are not the intended recipient, kindly
> inform us by return e-mail and also kindly disregard the contents of
> the e-mail, delete the original message and destroy any copies thereof
> immediately. You are notified that any dissemination, distribution or
> copying of this communication is strictly prohibited unless approved
by
> the sender.
>
> DQ Entertainment (DQE) has taken every reasonable precaution to
> minimize the risk of transmission of computer viruses with this
e-mail;
> DQE is not liable for any damage you may sustain as a result of any
> virus in this e-mail. DQE shall not be liable for the views expressed
> in the e-mail. DQE reserves the right to monitor and review the
content
> of all messages sent to or from this e-mail address


Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail address