RESTORE SECONDARY HDR LET INCONSISTENT CHUNKS
HI EVERYBODY!
I HAD A PROBLEM WITH A HDR SECONDARY SERVER A WEEK AGO. THEN, WE PEROFORMED A
RESTORE (BACKUP FROM PRIMARY TO ARCHIVE, FTP TO SECONDARY, ONSTAT -P
SECONDARY),THEN WE CONFIGURED THE PAIR (ONMODE -D), THE ONLINE.LOG SEEMS NOT
RECORD AN ERROR WHILE WAS IN PHYSICAL RECOVERY AND THEN LOGICAL RECOVERY...
BUT IN THE OUTPUT OF ONSTAT -D (SECONDARY) IT SHOWS THE DBSPACES IN LOGICAL
RECOVERY AND THE CHUNKS LIKE INCONSISTENT,.... IS IT NORMAL?
IF NOT... WHAT CAN I DO?
THANKS IN ADVANCED.
Dbspaces
address number flags fchunk nchunks pgsize flags owner name
c00000007e059028 1 0x40801 1 1 2048 NL B informix rootdbs
c00000007f1e0e68 2 0x40801 2 4 2048 NL B informix datos
c00000007f1df848 3 0x40801 6 7 16384 NL B informix datos1
c00000007f1df9e0 4 0x40801 9 1 2048 NL B informix datos2
c00000007f1dfb78 5 0x42001 10 1 2048 N TB informix temp1
c00000007f1dfd10 6 0x42001 11 1 2048 N TB informix temp2
c00000007f1e1028 7 0x42001 12 1 2048 N TB informix temp3
c00000007f1e11c0 8 0x42001 13 1 2048 N TB informix temp4
c00000007f1e1358 9 0x40801 14 2 2048 NL B informix logs
9 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages flags pathname
c00000007e0591c0 1 1 0 3000000 980207 PI-B /dev/espacio01
c00000007f1e14f0 2 2 0 5000000 414 PI-B /dev/espacio02
c00000007f1e16d8 3 2 0 5000000 1517386 PI-B /dev/espacio03
c00000007f1e18c0 4 2 0 5000000 4999997 PI-B /dev/espacio04
c00000007f1e1aa8 5 2 0 5000000 4999997 PI-B /dev/espacio05
c00000007f1e1c90 6 3 0 625000 2835 PI-B /dev/espacio06
c00000007f1e3028 7 3 0 625000 6247 PI-B /dev/espacio07
c00000007f1e3210 8 3 0 625000 6247 PI-B /dev/espacio08
c00000007f1e33f8 9 4 0 5000000 3650502 PI-B /dev/espacio09
c00000007f1e35e0 10 5 0 2500000 2499947 PO-B /dev/espacio10
c00000007f1e37c8 11 6 0 2500000 2499947 PO-B /dev/espacio11
c00000007f1e39b0 12 7 0 2500000 2499947 PO-B /dev/espacio12
c00000007f1e3b98 13 8 0 2500000 2499947 PO-B /dev/espacio13
c00000007f1e3d80 14 9 0 5000000 19947 PI-B /dev/espacio14
c00000007f1e4028 15 9 0 5000000 979997 PI-B /dev/espacio15
c00000007f1e4210 16 3 0 625000 48161 PI-B /dev/espacio16
ONLINE.LOG SECONDARY SERVER:
Mon May 25 01:07:00 2009
12:23:50 IBM Informix Dynamic Server Started.
12:23:50 shmctl: errno = 12
12:23:50 Shared memory segment 0xc00000000131d000 could not be forced resident.
Mon May 25 12:23:53 2009
12:23:53 Event alarms enabled. ALARMPROG = '/usr/informix/etc/alarmprogram.sh'
12:23:53 Booting Language <c> from module <>
12:23:53 Loading Module <CNULL>
12:23:53 Booting Language <builtin> from module <>
12:23:53 Loading Module <BUILTINNULL>
12:23:53 Warning: CONSOLE = /usr/informix/tmp/online.con open failed. Redirecti
ng output to '/dev/null'.
12:23:53 Affinitied VP 1 to phys proc 0
12:23:53 Affinitied VP 3 to phys proc 1
12:23:53 Affinitied VP 4 to phys proc 2
12:23:53 Affinitied VP 5 to phys proc 3
12:23:58 DR: DRAUTO is 3 (CMSM)
12:23:58 DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)
12:23:58 Fast poll /dev/poll enabled.
12:23:58 IBM Informix Dynamic Server Version 11.50.FC3 Software Serial Numb
er AAA#B000000
12:23:59 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.
12:23:59 Started 2 B-tree scanners.
12:23:59 B-tree scanner threshold set at 5000.
12:23:59 B-tree scanner range scan size set to -1.
12:23:59 B-tree scanner ALICE mode set to 6.
12:23:59 B-tree scanner index compression level set to med.
12:23:59 DR: Reservation of the last logical log for log backup turned on
12:23:59 Data replication type and state information reset. To start DR, use
the 'onmode -d' command and wait for the pair to be operational,
before shutting down the database server
12:23:59 Dataskip is now OFF for all dbspaces
12:23:59 Restartable Restore has been ENABLED
12:23:59 Recovery Mode
12:24:00 Physical Restore of rootdbs, datos, datos1, datos2, logs started.
12:24:02 Checkpoint Completed: duration was 0 seconds.
12:24:02 Mon May 25 - loguniq 2452, logpos 0xb7d018, timestamp: 0x505a0c0d Inte
rval: 13813
12:24:02 Maximum server connections 0
12:24:02 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, P
log used 0, Llog used 0
12:33:10 Checkpoint Completed: duration was 0 seconds.
12:33:10 Mon May 25 - loguniq 2452, logpos 0xb7d018, timestamp: 0x505a0c23 Inte
rval: 13814
......
13:11:02 Maximum server connections 0
13:18:32 DR: Local and Remote server type and/or last change(LC) incompatible
[Local type: Invalid, LC: DR has not been initialized.]
[Remote type: Primary, LC: ]
13:18:43 DR: Local and Remote server type and/or last change(LC) incompatible
[Local type: Invalid, LC: DR has not been initialized.]
[Remote type: Primary, LC: ]
13:18:55 DR: Local and Remote server type and/or last change(LC) incompatible
[Local type: Invalid, LC: DR has not been initialized.]
[Remote type: Primary, LC: ]
13:19:02 DR: Reservation of the last logical log for log backup turned off
13:19:02 DR: new type = secondary, primary server name = alpha_pri
13:19:02 DR: Trying to connect to primary server = alpha_pri
13:19:06 DR: Secondary server connected
13:19:06 DR: Secondary server needs failure recovery
13:19:07 DR: Failure recovery from disk in progress ...
13:19:07 Logical Recovery Started.
13:19:07 10 recovery worker threads will be started.
13:19:07 Start Logical Recovery - Start Log 2452, End Log ?
13:19:07 Starting Log Position - 2452 0xb7d018
13:19:07 Clearing the physical and logical logs has started
13:21:46 Cleared 21478 MB of the physical and logical logs in 159 seconds
13:21:50 Started processing open transactions on secondary during startup
13:21:50 Finished processing open transactions on secondary during startup.
13:21:52 Checkpoint Completed: duration was 0 seconds.
13:21:52 Mon May 25 - loguniq 2452, logpos 0xcee018, timestamp: 0x5069eb4f Inte
rval: 13818
13:22:01 Logical Log 2452 Complete, timestamp: 0x511f54da.
13:22:03 B-tree scanners disabled.
13:22:04 DR: HDR secondary server operational
13:22:05 Checkpoint Completed: duration was 0 seconds.
13:22:05 Mon May 25 - loguniq 2453, logpos 0xa018, timestamp: 0x511f5513 Interv
al: 13829
13:22:05 Maximum server connections 0
13:22:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, P
log used 58, Llog used 0
13:23:57 CM:Connection manager hp90000 registered with the server
13:24:02 CM:Connection manager hp90002 registered with the server
13:37:26 Checkpoint Completed: duration was 0 seconds.
13:37:26 Mon May 25 - loguniq 2453, logpos 0x13aa018, timestamp: 0x512a848f Int
erval: 13830
JESSICA FLORES wrote:
> HI EVERYBODY!
>
> I HAD A PROBLEM WITH A HDR SECONDARY SERVER A WEEK AGO. THEN, WE PEROFORMED A
> RESTORE (BACKUP FROM PRIMARY TO ARCHIVE, FTP TO SECONDARY, ONSTAT -P
> SECONDARY),THEN WE CONFIGURED THE PAIR (ONMODE -D), THE ONLINE.LOG SEEMS NOT
> RECORD AN ERROR WHILE WAS IN PHYSICAL RECOVERY AND THEN LOGICAL RECOVERY...
> BUT IN THE OUTPUT OF ONSTAT -D (SECONDARY) IT SHOWS THE DBSPACES IN LOGICAL
> RECOVERY AND THE CHUNKS LIKE INCONSISTENT,.... IS IT NORMAL?
>
> IF NOT... WHAT CAN I DO?
> THANKS IN ADVANCED.
>
> Dbspaces
> address number flags fchunk nchunks pgsize flags owner name
> c00000007e059028 1 0x40801 1 1 2048 NL B informix rootdbs
> c00000007f1e0e68 2 0x40801 2 4 2048 NL B informix datos
> c00000007f1df848 3 0x40801 6 7 16384 NL B informix datos1
> c00000007f1df9e0 4 0x40801 9 1 2048 NL B informix datos2
> c00000007f1dfb78 5 0x42001 10 1 2048 N TB informix temp1
> c00000007f1dfd10 6 0x42001 11 1 2048 N TB informix temp2
> c00000007f1e1028 7 0x42001 12 1 2048 N TB informix temp3
> c00000007f1e11c0 8 0x42001 13 1 2048 N TB informix temp4
> c00000007f1e1358 9 0x40801 14 2 2048 NL B informix logs
> 9 active, 2047 maximum
>
> Chunks
> address chunk/dbs offset size free bpages flags pathname
> c00000007e0591c0 1 1 0 3000000 980207 PI-B /dev/espacio01
> c00000007f1e14f0 2 2 0 5000000 414 PI-B /dev/espacio02
> c00000007f1e16d8 3 2 0 5000000 1517386 PI-B /dev/espacio03
> c00000007f1e18c0 4 2 0 5000000 4999997 PI-B /dev/espacio04
> c00000007f1e1aa8 5 2 0 5000000 4999997 PI-B /dev/espacio05
> c00000007f1e1c90 6 3 0 625000 2835 PI-B /dev/espacio06
> c00000007f1e3028 7 3 0 625000 6247 PI-B /dev/espacio07
> c00000007f1e3210 8 3 0 625000 6247 PI-B /dev/espacio08
> c00000007f1e33f8 9 4 0 5000000 3650502 PI-B /dev/espacio09
> c00000007f1e35e0 10 5 0 2500000 2499947 PO-B /dev/espacio10
> c00000007f1e37c8 11 6 0 2500000 2499947 PO-B /dev/espacio11
> c00000007f1e39b0 12 7 0 2500000 2499947 PO-B /dev/espacio12
> c00000007f1e3b98 13 8 0 2500000 2499947 PO-B /dev/espacio13
> c00000007f1e3d80 14 9 0 5000000 19947 PI-B /dev/espacio14
> c00000007f1e4028 15 9 0 5000000 979997 PI-B /dev/espacio15
> c00000007f1e4210 16 3 0 625000 48161 PI-B /dev/espacio16
>
> ONLINE.LOG SECONDARY SERVER:
>
> Mon May 25 01:07:00 2009
>
> 12:23:50 IBM Informix Dynamic Server Started.
> 12:23:50 shmctl: errno = 12
> 12:23:50 Shared memory segment 0xc00000000131d000 could not be forced
> resident.
>
> Mon May 25 12:23:53 2009
>
> 12:23:53 Event alarms enabled. ALARMPROG =
'/usr/informix/etc/alarmprogram.sh'
> 12:23:53 Booting Language <c> from module <>
> 12:23:53 Loading Module <CNULL>
> 12:23:53 Booting Language <builtin> from module <>
> 12:23:53 Loading Module <BUILTINNULL>
> 12:23:53 Warning: CONSOLE = /usr/informix/tmp/online.con open failed.
> Redirecti
> ng output to '/dev/null'.
> 12:23:53 Affinitied VP 1 to phys proc 0
> 12:23:53 Affinitied VP 3 to phys proc 1
> 12:23:53 Affinitied VP 4 to phys proc 2
> 12:23:53 Affinitied VP 5 to phys proc 3
> 12:23:58 DR: DRAUTO is 3 (CMSM)
> 12:23:58 DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)
> 12:23:58 Fast poll /dev/poll enabled.
> 12:23:58 IBM Informix Dynamic Server Version 11.50.FC3 Software Serial Numb
> er AAA#B000000
> 12:23:59 IBM Informix Dynamic Server Initialized -- Shared Memory
Initialized.
>
> 12:23:59 Started 2 B-tree scanners.
> 12:23:59 B-tree scanner threshold set at 5000.
> 12:23:59 B-tree scanner range scan size set to -1.
> 12:23:59 B-tree scanner ALICE mode set to 6.
> 12:23:59 B-tree scanner index compression level set to med.
> 12:23:59 DR: Reservation of the last logical log for log backup turned on
> 12:23:59 Data replication type and state information reset. To start DR, use
>
> the 'onmode -d' command and wait for the pair to be operational,
>
> before shutting down the database server
>
> 12:23:59 Dataskip is now OFF for all dbspaces
> 12:23:59 Restartable Restore has been ENABLED
> 12:23:59 Recovery Mode
> 12:24:00 Physical Restore of rootdbs, datos, datos1, datos2, logs started.
>
> 12:24:02 Checkpoint Completed: duration was 0 seconds.
> 12:24:02 Mon May 25 - loguniq 2452, logpos 0xb7d018, timestamp: 0x505a0c0d
> Inte
> rval: 13813
>
> 12:24:02 Maximum server connections 0
> 12:24:02 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0,
> P
> log used 0, Llog used 0
>
> 12:33:10 Checkpoint Completed: duration was 0 seconds.
> 12:33:10 Mon May 25 - loguniq 2452, logpos 0xb7d018, timestamp: 0x505a0c23
> Inte
> rval: 13814
>
> .......
>
> 13:11:02 Maximum server connections 0
> 13:18:32 DR: Local and Remote server type and/or last change(LC) incompatible
>
> [Local type: Invalid, LC: DR has not been initialized.]
>
> [Remote type: Primary, LC: ]
>
> 13:18:43 DR: Local and Remote server type and/or last change(LC) incompatible
>
> [Local type: Invalid, LC: DR has not been initialized.]
>
> [Remote type: Primary, LC: ]
>
> 13:18:55 DR: Local and Remote server type and/or last change(LC) incompatible
>
> [Local type: Invalid, LC: DR has not been initialized.]
>
> [Remote type: Primary, LC: ]
>
> 13:19:02 DR: Reservation of the last logical log for log backup turned off
> 13:19:02 DR: new type = secondary, primary server name = alpha_pri
> 13:19:02 DR: Trying to connect to primary server = alpha_pri
> 13:19:06 DR: Secondary server connected
> 13:19:06 DR: Secondary server needs failure recovery
>
> 13:19:07 DR: Failure recovery from disk in progress ...
> 13:19:07 Logical Recovery Started.
> 13:19:07 10 recovery worker threads will be started.
> 13:19:07 Start Logical Recovery - Start Log 2452, End Log ?
> 13:19:07 Starting Log Position - 2452 0xb7d018
> 13:19:07 Clearing the physical and logical logs has started
> 13:21:46 Cleared 21478 MB of the physical and logical logs in 159 seconds
> 13:21:50 Started processing open transactions on secondary during startup
> 13:21:50 Finished processing open transactions on secondary during startup.
> 13:21:52 Checkpoint Completed: duration was 0 seconds.
> 13:21:52 Mon May 25 - loguniq 2452, logpos 0xcee018, timestamp: 0x5069eb4f
> Inte
> rval: 13818
>
> 13:22:01 Logical Log 2452 Complete, timestamp: 0x511f54da.
> 13:22:03 B-tree scanners disabled.
> 13:22:04 DR: HDR secondary server operational
> 13:22:05 Checkpoint Completed: duration was 0 seconds.
> 13:22:05 Mon May 25 - loguniq 2453, logpos 0xa018, timestamp: 0x511f5513
> Interv
> al: 13829
>
> 13:22:05 Maximum server connections 0
> 13:22:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0,
> P
> log used 58, Llog used 0
>
> 13:23:57 CM:Connection manager hp90000 registered with the server
> 13:24:02 CM:Connection manager hp90002 registered with the server
> 13:37:26 Checkpoint Completed: duration was 0 seconds.
> 13:37:26 Mon May 25 - loguniq 2453, logpos 0x13aa018, timestamp: 0x512a848f
> Int
> erval: 13830
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Please don't shout -
Jessica:
On an HDR Secondary node, the server is in a simulated recovery state s=
o
it is normal to see the chunks as inconsistent and the dbspaces in
logical recovery mode.
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
=
From: "JESSICA FLORES" <jessytapoli@hotmail.com> =
=
To: ids@iiug.org =
=
Date: 05/26/2009 03:45 PM =
=
Subject: RESTORE SECONDARY HDR LET INCONSISTENT CHUNKS [15840] =
=
Sent by: ids-bounces@iiug.org =
=
HI EVERYBODY!
I HAD A PROBLEM WITH A HDR SECONDARY SERVER A WEEK AGO. THEN, WE PEROFO=
RMED
A
RESTORE (BACKUP FROM PRIMARY TO ARCHIVE, FTP TO SECONDARY, ONSTAT -P
SECONDARY),THEN WE CONFIGURED THE PAIR (ONMODE -D), THE ONLINE.LOG SEEM=
S
NOT
RECORD AN ERROR WHILE WAS IN PHYSICAL RECOVERY AND THEN LOGICAL RECOVER=
Y...
BUT IN THE OUTPUT OF ONSTAT -D (SECONDARY) IT SHOWS THE DBSPACES IN LOG=
ICAL
RECOVERY AND THE CHUNKS LIKE INCONSISTENT,.... IS IT NORMAL?
IF NOT... WHAT CAN I DO?
THANKS IN ADVANCED.
Dbspaces
address number flags fchunk nchunks pgsize flags owner name
c00000007e059028 1 0x40801 1 1 2048 NL B informix rootdbs
c00000007f1e0e68 2 0x40801 2 4 2048 NL B informix datos
c00000007f1df848 3 0x40801 6 7 16384 NL B informix datos1
c00000007f1df9e0 4 0x40801 9 1 2048 NL B informix datos2
c00000007f1dfb78 5 0x42001 10 1 2048 N TB informix temp1
c00000007f1dfd10 6 0x42001 11 1 2048 N TB informix temp2
c00000007f1e1028 7 0x42001 12 1 2048 N TB informix temp3
c00000007f1e11c0 8 0x42001 13 1 2048 N TB informix temp4
c00000007f1e1358 9 0x40801 14 2 2048 NL B informix logs
9 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages flags pathname
c00000007e0591c0 1 1 0 3000000 980207 PI-B /dev/espacio01
c00000007f1e14f0 2 2 0 5000000 414 PI-B /dev/espacio02
c00000007f1e16d8 3 2 0 5000000 1517386 PI-B /dev/espacio03
c00000007f1e18c0 4 2 0 5000000 4999997 PI-B /dev/espacio04
c00000007f1e1aa8 5 2 0 5000000 4999997 PI-B /dev/espacio05
c00000007f1e1c90 6 3 0 625000 2835 PI-B /dev/espacio06
c00000007f1e3028 7 3 0 625000 6247 PI-B /dev/espacio07
c00000007f1e3210 8 3 0 625000 6247 PI-B /dev/espacio08
c00000007f1e33f8 9 4 0 5000000 3650502 PI-B /dev/espacio09
c00000007f1e35e0 10 5 0 2500000 2499947 PO-B /dev/espacio10
c00000007f1e37c8 11 6 0 2500000 2499947 PO-B /dev/espacio11
c00000007f1e39b0 12 7 0 2500000 2499947 PO-B /dev/espacio12
c00000007f1e3b98 13 8 0 2500000 2499947 PO-B /dev/espacio13
c00000007f1e3d80 14 9 0 5000000 19947 PI-B /dev/espacio14
c00000007f1e4028 15 9 0 5000000 979997 PI-B /dev/espacio15
c00000007f1e4210 16 3 0 625000 48161 PI-B /dev/espacio16
ONLINE.LOG SECONDARY SERVER:
Mon May 25 01:07:00 2009
12:23:50 IBM Informix Dynamic Server Started.
12:23:50 shmctl: errno =3D 12
12:23:50 Shared memory segment 0xc00000000131d000 could not be forced
resident.
Mon May 25 12:23:53 2009
12:23:53 Event alarms enabled. ALARMPROG =3D
'/usr/informix/etc/alarmprogram.sh'
12:23:53 Booting Language <c> from module <>
12:23:53 Loading Module <CNULL>
12:23:53 Booting Language <builtin> from module <>
12:23:53 Loading Module <BUILTINNULL>
12:23:53 Warning: CONSOLE =3D /usr/informix/tmp/online.con open failed.=
Redirecti
ng output to '/dev/null'.
12:23:53 Affinitied VP 1 to phys proc 0
12:23:53 Affinitied VP 3 to phys proc 1
12:23:53 Affinitied VP 4 to phys proc 2
12:23:53 Affinitied VP 5 to phys proc 3
12:23:58 DR: DRAUTO is 3 (CMSM)
12:23:58 DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)
12:23:58 Fast poll /dev/poll enabled.
12:23:58 IBM Informix Dynamic Server Version 11.50.FC3 Software Serial =
Numb
er AAA#B000000
12:23:59 IBM Informix Dynamic Server Initialized -- Shared Memory
Initialized.
12:23:59 Started 2 B-tree scanners.
12:23:59 B-tree scanner threshold set at 5000.
12:23:59 B-tree scanner range scan size set to -1.
12:23:59 B-tree scanner ALICE mode set to 6.
12:23:59 B-tree scanner index compression level set to med.
12:23:59 DR: Reservation of the last logical log for log backup turned =
on
12:23:59 Data replication type and state information reset. To start DR=
,
use
the 'onmode -d' command and wait for the pair to be operational,
before shutting down the database server
12:23:59 Dataskip is now OFF for all dbspaces
12:23:59 Restartable Restore has been ENABLED
12:23:59 Recovery Mode
12:24:00 Physical Restore of rootdbs, datos, datos1, datos2, logs start=
ed.
12:24:02 Checkpoint Completed: duration was 0 seconds.
12:24:02 Mon May 25 - loguniq 2452, logpos 0xb7d018, timestamp: 0x505a0=
c0d
Inte
rval: 13813
12:24:02 Maximum server connections 0
12:24:02 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
ked
0,
P
log used 0, Llog used 0
12:33:10 Checkpoint Completed: duration was 0 seconds.
12:33:10 Mon May 25 - loguniq 2452, logpos 0xb7d018, timestamp: 0x505a0=
c23
Inte
rval: 13814
.......
13:11:02 Maximum server connections 0
13:18:32 DR: Local and Remote server type and/or last change(LC)
incompatible
[Local type: Invalid, LC: DR has not been initialized.]
[Remote type: Primary, LC: ]
13:18:43 DR: Local and Remote server type and/or last change(LC)
incompatible
[Local type: Invalid, LC: DR has not been initialized.]
[Remote type: Primary, LC: ]
13:18:55 DR: Local and Remote server type and/or last change(LC)
incompatible
[Local type: Invalid, LC: DR has not been initialized.]
[Remote type: Primary, LC: ]
13:19:02 DR: Reservation of the last logical log for log backup turned =
off
13:19:02 DR: new type =3D secondary, primary server name =3D alpha_pri
13:19:02 DR: Trying to connect to primary server =3D alpha_pri
13:19:06 DR: Secondary server connected
13:19:06 DR: Secondary server needs failure recovery
13:19:07 DR: Failure recovery from disk in progress ...
13:19:07 Logical Recovery Started.
13:19:07 10 recovery worker threads will be started.
13:19:07 Start Logical Recovery - Start Log 2452, End Log ?
13:19:07 Starting Log Position - 2452 0xb7d018
13:19:07 Clearing the physical and logical logs has started
13:21:46 Cleared 21478 MB of the physical and logical logs in 159 secon=
ds
13:21:50 Started processing open transactions on secondary during start=
up
13:21:50 Finished processing open transactions on secondary during star=
tup.
13:21:52 Checkpoint Completed: duration was 0 seconds.
13:21:52 Mon May 25 - loguniq 2452, logpos 0xcee018, timestamp: 0x5069e=
b4f
Inte
rval: 13818
13:22:01 Logical Log 2452 Complete, timestamp: 0x511f54da.
13:22:03 B-tree scanners disabled.
13:22:04 DR: HDR secondary server operational
13:22:05 Checkpoint Completed: duration was 0 seconds.
13:22:05 Mon May 25 - loguniq 2453, logpos 0xa018, timestamp: 0x511f551=
3
Interv
al: 13829
13:22:05 Maximum server connections 0
13:22:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
ked
0,
P
l
$ONCONFIG
while
DRINTERVAL > 0 is asynchronous, the secondary server's chunk always PI(except
tempdbs).
DRINTERVAL = 0 is synchronous.