Simulate the DR Site with the Local Site thru FTP

[login to unmask email]

Simulate the DR Site with the Local Site thru FTP
I have some typical questions regarding Disaster Recovery for which I
would require some help.

I have a setup at the DR site ( Remote Location) where we have the
similar setup with our Local Site.Last week we have taken the Installation
DUMP ( Offline ) of the Local site and Restored successfully at the DR
Site.As per our setup we have a 2 MBPS Dedicated Leased Line from our Local
site to the DR Site.
Now I would like to keep updating the DR Site from the Local Site thru
FTP.
What I have planned is to use IEBGENER to get the ARCHIVE LOGS from TAPES
to DASD.Then find the details of Archive Logs from DSNJU004 and Add this
Archive Log to the BSDS thru DSNJU003.
After this Recover the Catalogs and Directories in the order specified in
Admin Guide and then RECOVER all the Tablespaces with LOGONLY option. I
will also be FTPing the changes to DDLs and applying it at the DR Site.I am
not taking any Imagecopies to the DR Site.
My Active Logs are old.Do I have to delete the entry of Active Logs
from the BSDS at the DR site and send the Active Logs as well everytime and
update in the BSDS at the DR Site.
Could someone tell me what I am missing or what else should be taken
into consideration ?
I would greatly appreciate any Advice or Suggestions from the
list.
Thanks in Advance .

Regards
Ujjal Bhattacharya
CDB



[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to ujjwal@LOT.TATASTEEL.COM)
One thing, and I sure there are many, you need to look at is the LOGONLY
recovery. I have been told by IBM that several tables in the DB2 directory
CAN NOT be recovered using LOGONLY. The HPGRBRBA does not get updated for
these tables. So one, you have to recover the DB2 catalog and directory by
using image copies.

The second problem is that the HPGRBRBA does not get updated on a
consistent basis. So your recovery of the "data" tables my call for a very
old archive log. As long as you have them this is not a problem.

And to answer you question about the active logs, yes you need to delete
the current ones and create new ones during you process of recreating the
BSDS. This is an process in itself.

Hope this helps.

John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



[login to unmask email]
ASTEEL.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Simulate the DR Site with the Local
Discussion Site thru FTP
List"
<[login to unmask email]
M>


01/03/02 08:49
AM
Please respond
to "DB2 Data
Base
Discussion
List"






I have some typical questions regarding Disaster Recovery for which I
would require some help.

I have a setup at the DR site ( Remote Location) where we have the
similar setup with our Local Site.Last week we have taken the Installation
DUMP ( Offline ) of the Local site and Restored successfully at the DR
Site.As per our setup we have a 2 MBPS Dedicated Leased Line from our Local
site to the DR Site.
Now I would like to keep updating the DR Site from the Local Site thru
FTP.
What I have planned is to use IEBGENER to get the ARCHIVE LOGS from TAPES
to DASD.Then find the details of Archive Logs from DSNJU004 and Add this
Archive Log to the BSDS thru DSNJU003.
After this Recover the Catalogs and Directories in the order specified in
Admin Guide and then RECOVER all the Tablespaces with LOGONLY option. I
will also be FTPing the changes to DDLs and applying it at the DR Site.I am
not taking any Imagecopies to the DR Site.
My Active Logs are old.Do I have to delete the entry of Active Logs
from the BSDS at the DR site and send the Active Logs as well everytime and
update in the BSDS at the DR Site.
Could someone tell me what I am missing or what else should be taken
into consideration ?
I would greatly appreciate any Advice or Suggestions from the
list.
Thanks in Advance .

Regards
Ujjal Bhattacharya
CDB








Michael Murley

Re: Simulate the DR Site with the Local Site thru FTP
(in response to John_Lendman@FPL.COM)
As John said, there are many things to consider here. I'll describe one.

A LOGONLY recovery sets the HPGRBRBA value to the current RBA or LRSN when
it completes. That may cause the next run to miss log records, since it
will start at this new HPGRBRBA value. Consider this scenario, using very
small numbers to represent LRSN values (to save the eyesight of those of us
over 40 :-)

Monday: A Logonly recovery at the remote site runs through the end of the
log at LRSN 100. The current LRSN is 200, so that is what is stored in
HPGRBRBA. Meanwhile, back at the local site, log records from 101 to 199
were written.

Tuesday: A logonly recovery runs but starts at LRSN 200, skipping the log
records created from 101 to 199. That's Bad.

This problem, like many others, is worse in data sharing; time-based LRSN
values continue to ascend regardless of activity, so the value stored in
HPGRBRBA will always reflect the current time. But the problem exists in
non-data sharing as well.

Have you considered the DB2 Tracker Site feature ?

Michael Murley
BMC



-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: January 03, 2002 8:39 AM
To: [login to unmask email]
Subject: Re: Simulate the DR Site with the Local Site thru FTP


One thing, and I sure there are many, you need to look at is the LOGONLY
recovery. I have been told by IBM that several tables in the DB2 directory
CAN NOT be recovered using LOGONLY. The HPGRBRBA does not get updated for
these tables. So one, you have to recover the DB2 catalog and directory by
using image copies.

The second problem is that the HPGRBRBA does not get updated on a
consistent basis. So your recovery of the "data" tables my call for a very
old archive log. As long as you have them this is not a problem.

And to answer you question about the active logs, yes you need to delete
the current ones and create new ones during you process of recreating the
BSDS. This is an process in itself.

Hope this helps.

John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



[login to unmask email]
ASTEEL.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Simulate the DR Site
with the Local
Discussion Site thru FTP
List"
<[login to unmask email]
M>


01/03/02 08:49
AM
Please respond
to "DB2 Data
Base
Discussion
List"






I have some typical questions regarding Disaster Recovery for which I
would require some help.

I have a setup at the DR site ( Remote Location) where we have the
similar setup with our Local Site.Last week we have taken the Installation
DUMP ( Offline ) of the Local site and Restored successfully at the DR
Site.As per our setup we have a 2 MBPS Dedicated Leased Line from our Local
site to the DR Site.
Now I would like to keep updating the DR Site from the Local Site thru
FTP.
What I have planned is to use IEBGENER to get the ARCHIVE LOGS from TAPES
to DASD.Then find the details of Archive Logs from DSNJU004 and Add this
Archive Log to the BSDS thru DSNJU003.
After this Recover the Catalogs and Directories in the order specified in
Admin Guide and then RECOVER all the Tablespaces with LOGONLY option. I
will also be FTPing the changes to DDLs and applying it at the DR Site.I am
not taking any Imagecopies to the DR Site.
My Active Logs are old.Do I have to delete the entry of Active Logs
from the BSDS at the DR site and send the Active Logs as well everytime and
update in the BSDS at the DR Site.
Could someone tell me what I am missing or what else should be taken
into consideration ?
I would greatly appreciate any Advice or Suggestions from the
list.
Thanks in Advance .

Regards
Ujjal Bhattacharya
CDB













[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to Michael Murley)
Thanx a lot to both John & Michael for your timely suggestions.
So the Active Logs and the old Archive Logs have to be deleted in the
BSDS at the Remote Site and new Active Logs have to be defined in the BSDS
at the Remote Site thru DSNJU003.
From your conclusion Recovering Catalogs and Directories from the
Archive Logs will have Inconsistent Results since there are few Directory
Tables that the HPGRBRBA which RECOVERY LOGONLY uses as the Starting Point
is not kept up-to-date.So the Current Image Copies of the Catalogs and
Directories has to be FTPed at the Remote site with the Archive Logs to
Recover the Catalogs and Directory.
For eg If there are 10 Archive Logs generated in a day and if I send one
by one to Remote Site then with each Archive Log I will have to send the
Current ImageCopy of the Catalog and Directory ( Assuming I am applying
one Archive Log at a time).
Could you clarify this because if this is true then I will have no option
but go for the Tracker Site ?
Michael,Could your Clarify a little more about your Example of
Logonly Recovery for Monday and Tuesday where I am missing the log records
created between 100 - 199 . Because SYSLGRNX contains the LOG RBA ranges of
all the Instances of a Tablespace when that Tablespace was in Update
mode.So I should find all those RBAs in the Archive Logs of 100-199
whenever the Tablespace was open for Update.
Does IBM recommend not to use RECOVER LOGONLY for Directory
Tablespaces?
Thanks in Anticipation. Any other suggestions are also welcome.

Regards
Ujjal Bhattacharya
CDB








"Murley,
Michael" To: [login to unmask email]
<Michael_Murle cc:
[login to unmask email]> Subject: Re: Simulate the DR Site with the
Sent by: DB2 Local Site thru FTP
Data Base
Discussion
List
<[login to unmask email]
M>


01/03/02 10:02
PM
Please respond
to DB2 Data
Base
Discussion
List






As John said, there are many things to consider here. I'll describe one.

A LOGONLY recovery sets the HPGRBRBA value to the current RBA or LRSN when
it completes. That may cause the next run to miss log records, since it
will start at this new HPGRBRBA value. Consider this scenario, using very
small numbers to represent LRSN values (to save the eyesight of those of us
over 40 :-)

Monday: A Logonly recovery at the remote site runs through the end of the
log at LRSN 100. The current LRSN is 200, so that is what is stored in
HPGRBRBA. Meanwhile, back at the local site, log records from 101 to 199
were written.

Tuesday: A logonly recovery runs but starts at LRSN 200, skipping the log
records created from 101 to 199. That's Bad.

This problem, like many others, is worse in data sharing; time-based LRSN
values continue to ascend regardless of activity, so the value stored in
HPGRBRBA will always reflect the current time. But the problem exists in
non-data sharing as well.

Have you considered the DB2 Tracker Site feature ?

Michael Murley
BMC



-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: January 03, 2002 8:39 AM
To: [login to unmask email]
Subject: Re: Simulate the DR Site with the Local Site thru FTP


One thing, and I sure there are many, you need to look at is the LOGONLY
recovery. I have been told by IBM that several tables in the DB2 directory
CAN NOT be recovered using LOGONLY. The HPGRBRBA does not get updated for
these tables. So one, you have to recover the DB2 catalog and directory by
using image copies.

The second problem is that the HPGRBRBA does not get updated on a
consistent basis. So your recovery of the "data" tables my call for a very
old archive log. As long as you have them this is not a problem.

And to answer you question about the active logs, yes you need to delete
the current ones and create new ones during you process of recreating the
BSDS. This is an process in itself.

Hope this helps.

John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



[login to unmask email]
ASTEEL.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Simulate the DR Site
with the Local
Discussion Site thru FTP
List"
<[login to unmask email]
M>


01/03/02 08:49
AM
Please respond
to "DB2 Data
Base
Discussion
List"






I have some typical questions regarding Disaster Recovery for which I
would require some help.

I have a setup at the DR site ( Remote Location) where we have the
similar setup with our Local Site.Last week we have taken the Installation
DUMP ( Offline ) of the Local site and Restored successfully at the DR
Site.As per our setup we have a 2 MBPS Dedicated Leased Line from our Local
site to the DR Site.
Now I would like to keep updating the DR Site from the Local Site thru
FTP.
What I have planned is to use IEBGENER to get the ARCHIVE LOGS from TAPES
to DASD.Then find the details of Archive Logs from DSNJU004 and Add this
Archive Log to the BSDS thru DSNJU003.
After this Recover the Catalogs and Directories in the order specified in
Admin Guide and then RECOVER all the Tablespaces with LOGONLY option. I
will also be FTPing the changes to DDLs and applying it at the DR Site.I am
not taking any Imagecopies to the DR Site.
My Active Logs are old.Do I have to delete the entry of Active Logs
from the BSDS at the DR site and send the Active Logs as well everytime and
update in the BSDS at the DR Site.
Could someone tell me what I am missing or what else should be taken
into consideration ?
I would greatly appreciate any Advice or Suggestions from the
list.
Thanks in Advance .

Regards
Ujjal Bhattacharya
CDB








the










[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to ujjwal@LOT.TATASTEEL.COM)
You stated this:

For eg If there are 10 Archive Logs generated in a day and if I send one
by one to Remote Site then with each Archive Log I will have to send the
Current ImageCopy of the Catalog and Directory ( Assuming I am applying
one Archive Log at a time).

And I beleive this is true, because you have to recover the Catalog and
Directory with Image copies.

You Stated This:

Does IBM recommend not to use RECOVER LOGONLY for Directory
Tablespaces?

This is the recommendation that I received from IBM Development when I ask
this question.


John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



Michael Murley

Re: Simulate the DR Site with the Local Site thru FTP
(in response to John_Lendman@FPL.COM)
You are correct that SYSLGRNX contains all the log ranges when the space was
in update mode. But the starting point to apply log records in a LOGONLY
recovery is determined by HPGRBRBA, not SYSLGRNX. If HPGRBRBA is set to the
current RBA in the remote system, any log records with RBAs lower than that
value will not be applied to the space in a subsequent LOGONLY run at the
remote system. Those updates will be represented in SYSLGRNX, but the
RECOVER LOGONLY utility will never see them because it starts the LOGAPPLY
process at HPGRBRBA.

I suggest that you open a question with IBM to see what they say about using
RECOVER LOGONLY for this sort of incremental migration of log records.

Michael Murley
BMC

-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: January 04, 2002 7:09 AM
To: [login to unmask email]
Subject: Re: Simulate the DR Site with the Local Site thru FTP


Thanx a lot to both John & Michael for your timely suggestions.
So the Active Logs and the old Archive Logs have to be deleted in the
BSDS at the Remote Site and new Active Logs have to be defined in the BSDS
at the Remote Site thru DSNJU003.
From your conclusion Recovering Catalogs and Directories from the
Archive Logs will have Inconsistent Results since there are few Directory
Tables that the HPGRBRBA which RECOVERY LOGONLY uses as the Starting Point
is not kept up-to-date.So the Current Image Copies of the Catalogs and
Directories has to be FTPed at the Remote site with the Archive Logs to
Recover the Catalogs and Directory.
For eg If there are 10 Archive Logs generated in a day and if I send one
by one to Remote Site then with each Archive Log I will have to send the
Current ImageCopy of the Catalog and Directory ( Assuming I am applying
one Archive Log at a time).
Could you clarify this because if this is true then I will have no option
but go for the Tracker Site ?
Michael,Could your Clarify a little more about your Example of
Logonly Recovery for Monday and Tuesday where I am missing the log records
created between 100 - 199 . Because SYSLGRNX contains the LOG RBA ranges of
all the Instances of a Tablespace when that Tablespace was in Update
mode.So I should find all those RBAs in the Archive Logs of 100-199
whenever the Tablespace was open for Update.
Does IBM recommend not to use RECOVER LOGONLY for Directory
Tablespaces?
Thanks in Anticipation. Any other suggestions are also welcome.

Regards
Ujjal Bhattacharya
CDB








"Murley,
Michael" To: [login to unmask email]
<Michael_Murle cc:
[login to unmask email]> Subject: Re: Simulate the DR
Site with the
Sent by: DB2 Local Site thru FTP
Data Base
Discussion
List
<[login to unmask email]
M>


01/03/02 10:02
PM
Please respond
to DB2 Data
Base
Discussion
List






As John said, there are many things to consider here. I'll describe one.

A LOGONLY recovery sets the HPGRBRBA value to the current RBA or LRSN when
it completes. That may cause the next run to miss log records, since it
will start at this new HPGRBRBA value. Consider this scenario, using very
small numbers to represent LRSN values (to save the eyesight of those of us
over 40 :-)

Monday: A Logonly recovery at the remote site runs through the end of the
log at LRSN 100. The current LRSN is 200, so that is what is stored in
HPGRBRBA. Meanwhile, back at the local site, log records from 101 to 199
were written.

Tuesday: A logonly recovery runs but starts at LRSN 200, skipping the log
records created from 101 to 199. That's Bad.

This problem, like many others, is worse in data sharing; time-based LRSN
values continue to ascend regardless of activity, so the value stored in
HPGRBRBA will always reflect the current time. But the problem exists in
non-data sharing as well.

Have you considered the DB2 Tracker Site feature ?

Michael Murley
BMC



-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: January 03, 2002 8:39 AM
To: [login to unmask email]
Subject: Re: Simulate the DR Site with the Local Site thru FTP


One thing, and I sure there are many, you need to look at is the LOGONLY
recovery. I have been told by IBM that several tables in the DB2 directory
CAN NOT be recovered using LOGONLY. The HPGRBRBA does not get updated for
these tables. So one, you have to recover the DB2 catalog and directory by
using image copies.

The second problem is that the HPGRBRBA does not get updated on a
consistent basis. So your recovery of the "data" tables my call for a very
old archive log. As long as you have them this is not a problem.

And to answer you question about the active logs, yes you need to delete
the current ones and create new ones during you process of recreating the
BSDS. This is an process in itself.

Hope this helps.

John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



[login to unmask email]
ASTEEL.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Simulate the DR Site
with the Local
Discussion Site thru FTP
List"
<[login to unmask email]
M>


01/03/02 08:49
AM
Please respond
to "DB2 Data
Base
Discussion
List"






I have some typical questions regarding Disaster Recovery for which I
would require some help.

I have a setup at the DR site ( Remote Location) where we have the
similar setup with our Local Site.Last week we have taken the Installation
DUMP ( Offline ) of the Local site and Restored successfully at the DR
Site.As per our setup we have a 2 MBPS Dedicated Leased Line from our Local
site to the DR Site.
Now I would like to keep updating the DR Site from the Local Site thru
FTP.
What I have planned is to use IEBGENER to get the ARCHIVE LOGS from TAPES
to DASD.Then find the details of Archive Logs from DSNJU004 and Add this
Archive Log to the BSDS thru DSNJU003.
After this Recover the Catalogs and Directories in the order specified in
Admin Guide and then RECOVER all the Tablespaces with LOGONLY option. I
will also be FTPing the changes to DDLs and applying it at the DR Site.I am
not taking any Imagecopies to the DR Site.
My Active Logs are old.Do I have to delete the entry of Active Logs
from the BSDS at the DR site and send the Active Logs as well everytime and
update in the BSDS at the DR Site.
Could someone tell me what I am missing or what else should be taken
into consideration ?
I would greatly appreciate any Advice or Suggestions from the
list.
Thanks in Advance .

Regards
Ujjal Bhattacharya
CDB








the















[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to Michael Murley)
Thanks a lot once again to both of you John and Michael for your valuable
contribution.
Also I have tested the RECOVERY LOGONLY OPTION and both of you are
Absolulety Right that I will miss the Archive Logs .I updated a table and
took a Quiesce it updated the HPGRBRBA VALUE then I did a Load Replace it
again updated the HPGRBRBA value and when I started Recovering it was using
that RBA mentioned in HPGRBRBA as a Starting Point.So I have no option but
to FTP the latest Imagecopies too.
Now Michael & John ,Do I have to delete and define the Active Logs at
the Remote Site and if yes then Could I have a clarification on the
STARTRBA and ENDRBA value of the new defined Active Logs to be Applied at
the Remote site when I add the Archive Logs to the BSDS at the Remote site.
For Eg
If I am applying two Archive Logs to the BSDS at the Remote Site
Archive Logs Start RBA End RBA
Arch1 1 100
Arch2 101 200

Then Should My Active Logs at the Remote Site be this
Active Logs Start RBA End RBA
Act1 201 300
Act2 301 400
Act3 401 500

If the RBA value is 0159BAF2E795 then I add 1 to BAF2E795 and get the
next RBA value as 0159BAF2E796.But I am not sure of when this 0159 changes
or what is this value.Could you clarify this ?

Thanks in Anticipation.

Regards
Ujjal Bhattacharya
CDB



[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to ujjwal@LOT.TATASTEEL.COM)
This gets complicated, but here it goes.

Yes you have to delete the active logs. Now when you are doing the recovery
with the archive logs, you have also done a conditional restart to DB2
first. The ENDRBA that you put in the control cards for the conditional
restart will determine what RBA is now written to the new active logs. So
the way I do my conditional restart is I take the HIGH RBA written on the
last archive log and add hex 1000 , This is the same archive log that I
have to add back to the BSDS, because the last one is never in the BSDS.
That way the RBA's flow from the last one that your are using to recover
with and the new active log with now have the next higher RBA.

Hope this helps.

John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



[login to unmask email]
ASTEEL.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Re: Simulate the DR Site with the
Discussion Local Site thru FTP
List"
<[login to unmask email]
M>


01/08/02 09:31
AM
Please respond
to "DB2 Data
Base
Discussion
List"






Thanks a lot once again to both of you John and Michael for your valuable
contribution.
Also I have tested the RECOVERY LOGONLY OPTION and both of you are
Absolulety Right that I will miss the Archive Logs .I updated a table and
took a Quiesce it updated the HPGRBRBA VALUE then I did a Load Replace it
again updated the HPGRBRBA value and when I started Recovering it was using
that RBA mentioned in HPGRBRBA as a Starting Point.So I have no option but
to FTP the latest Imagecopies too.
Now Michael & John ,Do I have to delete and define the Active Logs at
the Remote Site and if yes then Could I have a clarification on the
STARTRBA and ENDRBA value of the new defined Active Logs to be Applied at
the Remote site when I add the Archive Logs to the BSDS at the Remote site.
For Eg
If I am applying two Archive Logs to the BSDS at the Remote Site
Archive Logs Start RBA End RBA
Arch1 1 100
Arch2 101 200

Then Should My Active Logs at the Remote Site be this
Active Logs Start RBA End RBA
Act1 201 300
Act2 301 400
Act3 401 500

If the RBA value is 0159BAF2E795 then I add 1 to BAF2E795 and get the
next RBA value as 0159BAF2E796.But I am not sure of when this 0159 changes
or what is this value.Could you clarify this ?

Thanks in Anticipation.

Regards
Ujjal Bhattacharya
CDB








[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to John_Lendman@FPL.COM)
John,
Thanks a lot.
You have said that the last Archive Log is not there in the BSDS .As
long as I update the BSDS with Archive Logs one after another there is no
question of missing the last Archive Log.Please correct me if I am wrong
because I would like to know of a scenario where I will miss any of the
Archive Log, provided my BSDS is ok.
Could you clarify the CRCR because I am still not very clear with the
CRCR .What will happen if I bring DB2 up without a Crestart ?
Thanks.

Regards
Ujjal Bhattacharya



[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to ujjwal@LOT.TATASTEEL.COM)
The missing archive log that I was talking about is because when you take a
backup of the archive log you also get a back up of the BSDS. This backup
of the BSDS is what you use when you rebuild the BSDS for recovery. The
copy of the archive log that goes with that backup is not in the BSDS
because it was just created when you created the backup. Therefore when you
are rebuild the BSDS you need to add this archive log back in to the BSDS.
I do not think you will miss any archive logs doing it this way.

As for the conditional restart, this is what tells DB2 what to backout, if
there was an in-flight threads and to what point you want DB2 to be in
order for you to do your recovery. With out a conditional restart, DB2
will try to bring every thing current and you have just deleted all the
active logs, so I believe it will fail on the restart. You know that you
can control the conditional restart by setting the ENDRBA at the point you
want DB2 to resume processing. Also you might want to read about the
conditional restart in the Database Admin guide.

Hope this helps.

John C. Lendman
DBA
[login to unmask email]
(561) 694-5085
Beeper FPL 7413



[login to unmask email]
ASTEEL.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Re: Simulate the DR Site with the
Discussion Local Site thru FTP
List"
<[login to unmask email]
M>


01/09/02 10:07
AM
Please respond
to "DB2 Data
Base
Discussion
List"






John,
Thanks a lot.
You have said that the last Archive Log is not there in the BSDS .As
long as I update the BSDS with Archive Logs one after another there is no
question of missing the last Archive Log.Please correct me if I am wrong
because I would like to know of a scenario where I will miss any of the
Archive Log, provided my BSDS is ok.
Could you clarify the CRCR because I am still not very clear with the
CRCR .What will happen if I bring DB2 up without a Crestart ?
Thanks.

Regards
Ujjal Bhattacharya








[login to unmask email]

Re: Simulate the DR Site with the Local Site thru FTP
(in response to John_Lendman@FPL.COM)
First of let me thank you for all the suggestions you have given and it
helped me a lot.You are very right that if I extract the BSDS from the
latest Archive Log it will not have an entry of that Archive Log in that
BSDS.

Thanks a lot once again.

Regards
Ujjal Bhattacharya