DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: Setting up Data Guard over very slow connection

  1. #1
    Join Date
    Jul 2017
    Posts
    2

    Setting up Data Guard over very slow connection

    While trying to Setup Data Guard involving a remote host, it happens that after Initial instantiation a failure occurs on the standby DB during the recovery Phase because archivelogs are missing, since they can't be kept that Long (they were deleted due to space constraints).

    But since there is enough space on the standby side (at the remote host), I thought that if Transport of archivelogs to the standby host would be enabled just Prior to instantiation, then after datafiles were copied, recovery would not fail and the standby DB would be far behind but would catch up with Primary. Recovery Speed is high enough using local archivelogs.

    How can I enable automatic redolog Transport to a diskgroup in another Cluster?

    Usually, an additional archivelog_destination_n is enabled for Synchronisation in a Data Guard Environment, but this Transport only Begins *after* instantiation (afaik), and then it is too late because at this time some archivelogs were already deleted.

    The key Point is how to keep archivelogs generated during instantiation of the standby DB and how to make them available to the standby DB at the recovery phase.

    Thanks for your advice
    Fritz

  2. #2
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,166
    It sounds like you need to add more disk space to your production database server,
    or at least clean up space. The RMAN command below will ensure that every archive
    log has been applied to every standby database and backed up twice before being deleted.
    You want to make sure that this is possible. which means you need more disk space for prod.

    Code:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 2 TIMES TO DISK;

  3. #3
    Join Date
    Jul 2017
    Posts
    2
    Yes it sounds like that. But that does not address the question. Adding storage is not an option. Besides that, your CONFIGURE command would cause more space consumption without keeping the archivelogs longer, which is my actual Problem.

  4. #4
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,166
    Right. But you need everything to be backed up at least 1 time before you delete the archive logs.
    You can run archive log only backups during the day to free space. You can try growing the size
    of the online redo and adding more online redo log groups. This will reduce the number of log
    switches and keep more redo online.

    Code:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO DISK;

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