8i physical standby : Managed recovery across WAN - painless??
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: 8i physical standby : Managed recovery across WAN - painless??

  1. #1
    Join Date
    Oct 2002
    Posts
    807

    8i physical standby : Managed recovery across WAN - painless??

    I've got a customer on 8i (700Gb) that wants a standby on a remote location (across the WAN..far far away).

    While I've implemented several standbys across the WAN on 9i (with managed recovery and LGWR XptMode), and earlier versions (8i, 7.3.4) by manually transporting logs via scripts; I have never used "managed recovery on a 8i database” (with a default ARCH Xptmode; since there’s no concept of SRLs and LGWR Xptmodes in 8i). I was wondering if anyone could share their experience how well this performs - on a somewhat active (100Meg/min) reasonably big database across a flaky WAN. While 9i handles managed recovery pretty well, I don't know about 8i.

    How well does 8i handle network interrupts? Say the RFS fails, does it automatically retry transmitting logs that failed after a certain time (reopen clause)? Or does it involve taking care of it manually (copying the failed logs), and restarting the "managed recovery" everytime?

    I’m aware of how 8i managed recovery is “supposed to work” on paper..I’m looking for opinions from folks who manage a standby environment (8i) across the WAN. How painless is 8i managed recovery?

    Thanks, Anand

  2. #2
    Join Date
    Oct 2002
    Posts
    807
    Is there a concept of GAP resolution (or something akin to FAL) in 8i at all?? From all the documentation that I've read, there is nothing that takes care of GAP resolution in 8i. What was the point in introducing "managed recovery" in 8i? It was a 'half-baked' feature..

  3. #3
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Originally posted by Axr2
    Is there a concept of GAP resolution (or something akin to FAL) in 8i at all??
    No, that is a feature that was not available before 9i.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  4. #4
    Join Date
    Oct 2002
    Posts
    807
    Do you know if 8i supports SSH / Tunneling with data compression? I assume yes - since it ought to be database version/release independent..

    Hope you get my drift - I'm trying to push a ton of redo across the WAN. While I can manually manage such a standby (using scripts), I'm trying to see if I can somehow get away with Managed recovery..

  5. #5
    Join Date
    Mar 2004
    Location
    IA USA
    Posts
    257
    Originally posted by Axr2
    Is there a concept of GAP resolution (or something akin to FAL) in 8i at all??
    In Oracle8i, you have to manually monitor gaps and
    then manually copy those archived gap logs to the standby.

  6. #6
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    Originally posted by Axr2
    Do you know if 8i supports SSH / Tunneling with data compression? I assume yes - since it ought to be database version/release independent..

    Hope you get my drift - I'm trying to push a ton of redo across the WAN. While I can manually manage such a standby (using scripts), I'm trying to see if I can somehow get away with Managed recovery..
    define a ton? I'm just curious, we're doing about 15gb a day in redo pushing to the stby
    I'm stmontgo and I approve of this message

  7. #7
    Join Date
    Oct 2002
    Posts
    807
    controlfile_record_keep_time is set to 30.

    Based on the last month's v$log_history, min redo generated 23G, max=75G. Avg=40G.

    Keep in mind - WAN. Over 4000miles.

    PS : In your case, do you enable data compression?
    Last edited by Axr2; 05-20-2004 at 06:49 PM.

  8. #8
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    Originally posted by Axr2
    controlfile_record_keep_time is set to 30.

    Based on the last month's v$log_history, min redo generated 23G, max=75G. Avg=40G.

    Keep in mind - WAN. Over 4000miles.

    PS : In your case, do you enable data compression?
    no compression, it sort of just works out for us, we run rac with each node doing about 7 or 8gb and it taking 45 mins to push a 250mg log. We may not always be within 1 log on the standby but by the end of the day we are all caught up
    I'm stmontgo and I approve of this message

  9. #9
    Join Date
    Oct 2002
    Posts
    807
    45mts for 250M. Seems a tad faster than 56Kbps! WAN again? I assume you have a ton (ton>10) of redolog groups. Surprising that you don't encounter too many network issues on such low bandwidth..

  10. #10
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    Originally posted by Axr2
    45mts for 250M. Seems a tad faster than 56Kbps! WAN again? I assume you have a ton (ton>10) of redolog groups. Surprising that you don't encounter too many network issues on such low bandwidth..
    10 groups each, i love the gap resolution, we get a network hiccup every other day that drops a log which Oracle fixes next time it generates a new arch log
    I'm stmontgo and I approve of this message

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width