{"id":6882,"date":"2016-04-12T08:39:28","date_gmt":"2016-04-12T06:39:28","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/"},"modified":"2016-04-12T08:39:28","modified_gmt":"2016-04-12T06:39:28","slug":"dbvisit-standby-version-7-auf-windows-server-2012-r2","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/","title":{"rendered":"Dbvisit Standby Version 7 auf Windows Server 2012 R2"},"content":{"rendered":"<h2>Ausgangslage<\/h2>\n<p>Wie gut l\u00e4sst sich mit Oracle Standard Edition unter Windows eine Hochverf\u00fcgbarkeitsl\u00f6sung aufbauen?<\/p>\n<p>Die Basis, zwei Windows Server 2012 R2, Oracle Standard Edition und Dbvisit Standby.<\/p>\n<p>Die eingesetzte Version Dbvisit Standby 7.0.48.15006.<\/p>\n<p>Die eingesetzte Oracle Version\u00a012.1.0.2.0.<\/p>\n<h2>Installation<\/h2>\n<p>Die Windows Installation ist Standard, nur die beiden Server m\u00fcssen, zwecks Namensaufl\u00f6sung im Hosts File(C:\\Windows\\System32\\drivers\\etc\\hosts) unter Windows eingetragen werden.<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">192.168.198.129 node01.localdomain node01 NODE01\n192.168.198.130 node02.localdomain node02 NODE02<\/pre>\n<p>Der zweite Schritt, die Installation der Oracle Software. Als erstes m\u00fcssen zwei User(oracle, OraSys) erstellt werden:<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">\u00a0<a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6643\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44.png\" alt=\"2016-01-18_09h55_44\" width=\"501\" height=\"131\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Wichtig, der Oracle User muss in der lokalen Administrator Gruppe sein!<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Nun erfolgt die Oracle Software Installation. Bei der Oracle Software Installation, habe ich in diesem Beispiel auch gerade die Datenbank erstellt. Vorsicht bei der SID, hier sollten Grossbuchstaben verwendet werden. Zwar funktioniert es auch mit Kleinbuchstaben, jedoch muss beim erstellen des Service auf dem Node02, beim Befehl oradim zwingend Grossbuchstaben verwendet werden. Nach der Installation haben wir zus\u00e4tzliche lokale Gruppen erhalten:<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h56_59.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6644\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h56_59.png\" alt=\"2016-01-18_09h56_59\" width=\"565\" height=\"312\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Wichtig, die Oracle Software muss auf beiden Servern installiert werden.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Als n\u00e4chster Schritt, wird Dbvisit Standby installiert. Auf dem Node01(Primary) gibt es nichts besonderes zu beachten, die Installation erfolgt sehr gut gef\u00fchrt. Hier ist nichts besonderes zu beachten, ausser der Konfiguration der Firewall. Hier m\u00fcssen auf beiden Servern die beiden Ports, TCP 7890(dbvnet Interkommunikation zwischen den Nodes), TCP 8081(HTTP f\u00fcr das Web_Interface) ge\u00f6ffnet werden.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Die Installation der Dbvisit Standby auf dem Node02, da gibt es Punkte zu beachten. Das es auf dem Standby(Node02) keine Datenbank gibt, muss nach der Installation der DBvisit Software mit dem Befehl:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">oradim -new -sid ORCL -startmode m<\/pre>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Dadurch wird ein Service erstellt, der ben\u00f6tigt wird um die Datenbank Instanz auf dem Node02 zu erstellen. Dieser Service startet nach einen Neustart auch die entsprechende Datenbank wieder.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">\u00a0<a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_10h21_48.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6648\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_10h21_48.png\" alt=\"2016-01-18_10h21_48\" width=\"554\" height=\"577\" \/><\/a><\/p>\n<h2 class=\"brush: actionscript3; gutter: true; first-line: 1\">Konfiguration<\/h2>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Als n\u00e4chsten Schritt, kann mit der Konfiguration von Dbvisit gestartet werden.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Dazu gibt es zwei M\u00f6glichkeiten, die erste ist \u00fcber eine sehr \u00fcbersichtliche Web-Oberfl\u00e4che. Die URL lautet http:\/\/node01.localdomain:8081.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_10h25_03.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6649\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_10h25_03.png\" alt=\"2016-01-18_10h25_03\" width=\"841\" height=\"630\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Die zweite M\u00f6glichkeit ist eine Text basierte Konfiguration auf der Konsole:<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">\u00a0<a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_10h28_13.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6651\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_10h28_13.png\" alt=\"2016-01-18_10h28_13\" width=\"840\" height=\"807\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Die\u00a0beiden M\u00f6glichkeiten Dbvisit Standby zu Konfigurieren (Konsole oder Web-Oberfl\u00e4che), sieht unter Windows identisch aus wie unter Linux.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Am Ende der Konfiguration, wir ein Konfigurationsfile(DDC, Dbvisit Database Configuration) erstellt, in dem die Parameter f\u00fcr beide Server(Primary und Standby), das Synchronisieren zwischen den beiden, Mail-Alarmierung, Archivelog Management auf beiden Nodes und noch einiges mehr festgehalten wird. Dbvisit transferiert die Konfiguration auch auf den Standby Server. Die gesamte Kommunikation zwischen den Servern(Primary und Standby) erfolgt durch den Dbvisit eigenen Service(Dbvnet). Dazu musste auf beiden Servern (Node01, Node02) jeweils die Firewall f\u00fcr den Port TCP 7890 ge\u00f6ffnet werden.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Ist die Konfiguration abgeschlossen, kann auf beide Arten(Text basiert oder Web-Oberfl\u00e4che) die Erstellung der Standby Datenbank gestartet werden.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Dbvisit f\u00fchrt diesen Schritt in wenigen Minuten vollst\u00e4ndig und automatisiert durch. Dieser Prozess kann jeweils\u00a0im Web-Interface\u00a0oder in der textbasierten Version verfolgt werden.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Ist das erstellen der Standby Database auf dem Node02 abgeschlossen, muss noch die Synchronisation durchgef\u00fchrt werden. Dazu gibt\u00a0wieder entweder das Web-Interface oder die textbasierte Oberfl\u00e4che. Gestartet wird\u00a0auf dem Node01:<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_13h00_03.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6657\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_13h00_03.png\" alt=\"2016-01-18_13h00_03\" width=\"634\" height=\"853\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">oder die Text-Konsole, als Beispiel auf dem Node02.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_13h02_28.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6658\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_13h02_28.png\" alt=\"2016-01-18_13h02_28\" width=\"838\" height=\"583\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Um das zu automatisieren wird noch ein Task ben\u00f6tigt, damit regelm\u00e4ssig die Synchronisation startet.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Das kann mittels dem Task Scheduler konfiguriert werden:<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_13h10_10.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-6660\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_13h10_10.png\" alt=\"2016-01-18_13h10_10\" width=\"837\" height=\"479\" \/><\/a><\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Damit w\u00e4re die Konfiguration abgeschlossen.<\/p>\n<h2 class=\"brush: actionscript3; gutter: true; first-line: 1\">Graceful Switchover (Cli)<\/h2>\n<p>Nun wollen wir den Switchover, jeweils durch das Web-Interface bzw. durch die Textkonsole untersuchen.<\/p>\n<p>Um einen Graceful Switchover durchzuf\u00fchren, muss die automatische Synchronisation angehalten werden.<\/p>\n<p>Folgende Befehle sollten durchgef\u00fchrt werden:<\/p>\n<pre>Node01: dbvisit orcl<\/pre>\n<pre>Node02: dbvisit orcl<\/pre>\n<pre>Node01: dbv_oraStartStop switchover orcl 1111<\/pre>\n<pre>Node02: dbv_oraStartStop switchover orcl 1111<\/pre>\n<p>Die beiden ersten Befehle stellen manuel sicher das Primary und Standby m\u00f6glichst synchron sind.<\/p>\n<p>Die beiden letzten Befehle l\u00f6sen den Graceful Switchover aus.<\/p>\n<p>Die Ausgabe an der Konsole des Node01 sieht dann folgendermassen aus:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">C:\\Program Files (x86)\\Dbvisit\\Standby&gt;dbv_oraStartStop switchover orcl 1111\n=============================================================\nDbvisit Standby Database Technology (7.0.48.15006) (pid 1392)\ndbv_oraStartStop started on NODE01: Mon Jan 18 13:24:12 2016 ()\n=============================================================\n\n=============================================================\nGraceful Switchover starting on Primary Database orcl.\nTimestamp: 201601181324.\n\n&gt;&gt;&gt; Database orcl will be shutdown and restarted &lt;&lt;&lt;\nEnsure Dbvisit is no longer scheduled.\n\nObtaining archive log gap....\nContacting Standby Database orcl on NODE02...\nNext standby sequence required for recovery (434) for thread 1.\n\nArchive Log Gap for thread 1 is: 0. This is correct to continue.\n\nPlease enter unique key to begin graceful switchover for database orcl.\nThe same key must be entered on both primary and standby server.\n\nPlease start command: dbv_oraStartStop switchover orcl\non NODE02 if not already started.\n\nBatch key will be used: 1111\nKey 1111 entered.\n\nContacting NODE02 to ensure the same unique key is entered for orcl.\nWaiting for Key 1 on NODE02...\nCheckpoint 1 completed. Key found on NODE02\nWaiting for Checkpoint 2 on NODE02...\nCheckpoint 2 completed. Key found on NODE02\nWaiting for Checkpoint 3 on NODE02...\nCheckpoint 3 completed. Key found on NODE02\nShutting down regular Database orcl...\nRegular Database orcl shutdown successfully.\nWindows Service OracleServiceorcl already started.\nStarting Regular Database orcl...\nRegular Database orcl started restrict.\nPerforming Oracle Checkpoint.\n    Waiting 3 seconds for log switch completion...\n\nCreating standby control file as 'C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvi\nsit.1111.orcl.standbycontrolfile'...\nWaiting for Checkpoint 4 on NODE02...\nCheckpoint 4 completed. Key found on NODE02\nCopying new archives for orcl to NODE02...\nCompressing  O1_MF_1_434_C9SPG2XB_.ARC...\n  &gt; Transferring 'O1_MF_1_434_C9SPG2XB_.ARC.gz' to server NODE02:7890\n    Progress: 0%...20%...40%...60%...80%...100% [4989 KB\/s] - done.\nCompressing  O1_MF_1_435_C9SPJL2H_.ARC...\n  &gt; Transferring 'O1_MF_1_435_C9SPJL2H_.ARC.gz' to server NODE02:7890\n    Progress: 0%...20%...40%...60%...80%...100% [27154 KB\/s] - done.\nShutting down regular Database orcl...\nRegular Database orcl shutdown successfully.\nCopying redo logs ... this may take a while...\nCompressing  X.dbvisit.1111.orcl.redo_1.log...\n  &gt; Transferring 'X.dbvisit.1111.orcl.redo_1.log.gz' to server NODE02:7890\n    Progress: 0%...20%...40%...60%...80%...100% [195731 KB\/s] - done.\nCompressing  X.dbvisit.1111.orcl.redo_2.log...\n  &gt; Transferring 'X.dbvisit.1111.orcl.redo_2.log.gz' to server NODE02:7890\n    Progress: 0%...20%...40%...60%...80%...100% [223546 KB\/s] - done.\nCompressing  X.dbvisit.1111.orcl.redo_3.log...\n  &gt; Transferring 'X.dbvisit.1111.orcl.redo_3.log.gz' to server NODE02:7890\n    Progress: 0%...20%...40%...60%...80%...100% [193141 KB\/s] - done.\nWaiting for Checkpoint 5 on NODE02...\nCheckpoint 5 completed. Key found on NODE02\nBacking up current control files for orcl NODE01...\nDatabase orcl on NODE01 is already down. No action taken.\nWindows Service OracleServiceorcl already started.\nStarting Regular Database orcl...\nRegular Database orcl started nomount.\nControl file backed up as C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.1111\n.orcl.controlfile.\nShutting down standby Database orcl...\nStandby Database orcl shutdown successfully.\nWaiting for Checkpoint 6 on NODE02...\nCheckpoint 6 completed. Key found on NODE02\nWaiting for Checkpoint 7 on NODE02...\nCheckpoint 7 completed. Key found on NODE02\nWaiting for Checkpoint 8 on NODE02...\nCheckpoint 8 completed. Key found on NODE02\nWaiting for Checkpoint 9 on NODE02...\nCheckpoint 9 completed. Key found on NODE02\nWaiting for Checkpoint 10 on NODE02...\nCheckpoint 10 completed. Key found on NODE02\nWaiting for Checkpoint 11 on NODE02...\nCheckpoint 11 completed. Key found on NODE02\nWaiting for Checkpoint 12 on NODE02...\nCheckpoint 12 completed. Key found on NODE02\nDatabase orcl on NODE01 is already down. No action taken.\nWindows Service OracleServiceorcl already started.\nStarting Regular Database orcl...\nRegular Database orcl started nomount.\nSTANDBY control file(s) restored from C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.\ndbvisit.1111.orcl.standbycontrolfile.\nShutting down standby Database orcl...\nStandby Database orcl shutdown successfully.\nWindows Service OracleServiceorcl already started.\nStarting Standby Database orcl...\nStandby Database orcl started .\nWaiting for Checkpoint 13 on NODE02...\nCheckpoint 13 completed. Key found on NODE02\nWaiting for Checkpoint 14 on NODE02...\nCheckpoint 14 completed. Key found on NODE02\nFile C:\\Program Files (x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env copied to\nC:\\Program Files (x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env.201601181324.\nDbvisit Database configuration (DDC) file C:\\Program Files\n(x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env has been updated and variables have been\n\nreversed between primary and standby server.\n\nSOURCE=NODE02 DESTINATION=NODE01.\n\nWaiting for Checkpoint 15 on NODE02...\nCheckpoint 15 completed. Key found on NODE02\nUncompressing O1_MF_1_434_C9SPG2XB_.ARC.gz...\nUncompressing O1_MF_1_435_C9SPJL2H_.ARC.gz...\nWaiting for Checkpoint 16 on NODE02...\nCheckpoint 16 completed. Key found on NODE02\nWaiting for Checkpoint 17 on NODE02...\nCheckpoint 17 completed. Key found on NODE02\nWaiting for Checkpoint 18 on NODE02...\nCheckpoint 18 completed. Key found on NODE02\n\nGraceful switchover completed.\n\nThis database (orcl) is now a standby database.\n\nTo keep this new standby database in synch,\nreschedule Dbvisit as per normal:\n        dbvisit orcl\n=============================================================\ndbv_oraStartStop ended on NODE01: Mon Jan 18 13:32:13 2016\n=============================================================<\/pre>\n<pre><\/pre>\n<p>Die Ausgabe an der Konsole des Node02:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">C:\\Program Files (x86)\\Dbvisit\\Standby&gt;dbv_oraStartStop switchover orcl 1111\n=============================================================\nDbvisit Standby Database Technology (7.0.48.15006) (pid 1748)\ndbv_oraStartStop started on NODE02: Mon Jan 18 13:24:48 2016 ()\n=============================================================\n\n=============================================================\nGraceful Switchover starting on Standby Database orcl.\nTimestamp: 201601181324.\nDatabase orcl will be shutdown and restarted!\nEnsure Dbvisit is no longer scheduled.\n\nPlease enter unique key to begin graceful switchover for database orcl.\nThe same key must be entered on both primary and standby server.\n\nPlease start command: dbv_oraStartStop switchover orcl\non NODE01 if not already started.\n\nBatch key will be used: 1111\nKey 1111 entered.\n\nContacting NODE01 to ensure the same unique key is entered for orcl.\nWaiting for Key 1 on NODE01...\nCheckpoint 1 completed. Key found on NODE01\nWaiting for Checkpoint 2 on NODE01...\nCheckpoint 2 completed. Key found on NODE01\nWaiting for Checkpoint 3 on NODE01...\nCheckpoint 3 completed. Key found on NODE01\nTempfiles dropped.\nWaiting for Checkpoint 4 on NODE01...\nCheckpoint 4 completed. Key found on NODE01\nShutting down standby Database orcl...\nStandby Database orcl shutdown successfully.\nWaiting for Checkpoint 5 on NODE01...\nCheckpoint 5 completed. Key found on NODE01\nUncompressing 1_434_898595433.arc.gz...\nUncompressing 1_435_898595433.arc.gz...\nUncompressing X.dbvisit.1111.orcl.redo_1.log.gz...\nUncompressing X.dbvisit.1111.orcl.redo_2.log.gz...\nUncompressing X.dbvisit.1111.orcl.redo_3.log.gz...\nWaiting for Checkpoint 6 on NODE01...\nCheckpoint 6 completed. Key found on NODE01\nWaiting for Checkpoint 7 on NODE01...\nCheckpoint 7 completed. Key found on NODE01\nBacking up current control files for orcl NODE02...\nDatabase orcl on NODE02 is already down. No action taken.\nWindows Service OracleServiceorcl already started.\nStarting Standby Database orcl...\nStandby Database orcl started nomount.\nControl file backed up as C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.1111\n.orcl.stdby_ctl_bck.\nShutting down standby Database orcl...\nStandby Database orcl shutdown successfully.\nWaiting for Checkpoint 8 on NODE01...\nCheckpoint 8 completed. Key found on NODE01\nWindows Service OracleServiceorcl already started.\nStarting Standby Database orcl...\nStandby Database orcl started nomount.\nPRIMARY control file(s) restored from C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.\ndbvisit.1111.orcl.controlfile.\nMount Database orcl...\nDatabase orcl mounted.\nCopying redo log C:\\Program Files (x86)\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.11\n11.orcl.redo_1.log to C:\\oradata\\ORCL\\onlinelog\\redo_1_1.log\nFile C:\\FAST_RECOVERY_AREA\\ORCL\\ONLINELOG\\O1_MF_1_C729GQGG_.LOG renamed to C:\\or\nadata\\ORCL\\onlinelog\\redo_1_1.log.\n\nCopying redo log C:\\Program Files (x86)\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.11\n11.orcl.redo_1.log to C:\\oradata\\ORCL\\onlinelog\\redo_1_2.log\nFile C:\\ORADATA\\ORCL\\ONLINELOG\\O1_MF_1_C729GPX3_.LOG renamed to C:\\oradata\\ORCL\\\nonlinelog\\redo_1_2.log.\n\nCopying redo log C:\\Program Files (x86)\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.11\n11.orcl.redo_2.log to C:\\oradata\\ORCL\\onlinelog\\redo_2_1.log\nFile C:\\FAST_RECOVERY_AREA\\ORCL\\ONLINELOG\\O1_MF_2_C729GR73_.LOG renamed to C:\\or\nadata\\ORCL\\onlinelog\\redo_2_1.log.\n\nCopying redo log C:\\Program Files (x86)\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.11\n11.orcl.redo_2.log to C:\\oradata\\ORCL\\onlinelog\\redo_2_2.log\nFile C:\\ORADATA\\ORCL\\ONLINELOG\\O1_MF_2_C729GQTN_.LOG renamed to C:\\oradata\\ORCL\\\nonlinelog\\redo_2_2.log.\n\nCopying redo log C:\\Program Files (x86)\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.11\n11.orcl.redo_3.log to C:\\oradata\\ORCL\\onlinelog\\redo_3_1.log\nFile C:\\FAST_RECOVERY_AREA\\ORCL\\ONLINELOG\\O1_MF_3_C729GRY2_.LOG renamed to C:\\or\nadata\\ORCL\\onlinelog\\redo_3_1.log.\n\nCopying redo log C:\\Program Files (x86)\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.11\n11.orcl.redo_3.log to C:\\oradata\\ORCL\\onlinelog\\redo_3_2.log\nFile C:\\ORADATA\\ORCL\\ONLINELOG\\O1_MF_3_C729GRMB_.LOG renamed to C:\\oradata\\ORCL\\\nonlinelog\\redo_3_2.log.\n\nWaiting for Checkpoint 9 on NODE01...\nCheckpoint 9 completed. Key found on NODE01\nRecovering new primary database...\nCatalog archivelog 'C:\\dbvisit_archdest\\orcl\\1_434_898595433.arc'...\nCatalog archivelog 'C:\\dbvisit_archdest\\orcl\\1_435_898595433.arc'...\nCompleted.\nWaiting for Checkpoint 10 on NODE01...\nCheckpoint 10 completed. Key found on NODE01\nArchive log all for Database orcl...\nCompleted.\nTempfiles dropped.\nWaiting for Checkpoint 11 on NODE01...\nCheckpoint 11 completed. Key found on NODE01\nOpen Database orcl...\nDatabase orcl opened.\nWaiting for Checkpoint 12 on NODE01...\nCheckpoint 12 completed. Key found on NODE01\nWaiting for Checkpoint 13 on NODE01...\nCheckpoint 13 completed. Key found on NODE01\nWaiting for Checkpoint 14 on NODE01...\nCheckpoint 14 completed. Key found on NODE01\nFile C:\\Program Files (x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env copied to\nC:\\Program Files (x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env.201601181324.\nDbvisit Database configuration (DDC) file C:\\Program Files\n(x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env has been updated and variables have been\n\nreversed between primary and standby server.\n\nSOURCE=NODE02 DESTINATION=NODE01.\n\nWaiting for Checkpoint 15 on NODE01...\nCheckpoint 15 completed. Key found on NODE01\nTempfiles created.\n\nFORCE LOGGING is turned on in the primary database orcl on NODE02.\nWaiting for Checkpoint 16 on NODE01...\nCheckpoint 16 completed. Key found on NODE01\nCompressing  1_434_898595433.arc...\nCompressing  1_435_898595433.arc...\nWaiting for Checkpoint 17 on NODE01...\nCheckpoint 17 completed. Key found on NODE01\nWaiting for Checkpoint 18 on NODE01...\nCheckpoint 18 completed. Key found on NODE01\n\nGraceful switchover completed.\n\nThis database (orcl) is now the primary database.\n\nYou may consider re-creating a password file to make sure all sysdba passwords are preserved.\nTo keep the standby database on NODE01 in synch with this primary database,\nreschedule Dbvisit as per normal:\n        dbvisit orcl\n=============================================================\ndbv_oraStartStop ended on NODE02: Mon Jan 18 13:32:11 2016\n=============================================================<\/pre>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Somit haben die beiden Nodes die Rolle getauscht. Die Datenbank orcl ist nun als primary auf dem Node02 und die Standby befindet sich auf dem Node01.<\/p>\n<p class=\"brush: actionscript3; gutter: true; first-line: 1\">Um den originalen Zustand wieder herzustellen, gehen wir wieder zur\u00fcck. Dieses mal mit dem Web-Interface.<\/p>\n<h2 class=\"brush: actionscript3; gutter: true; first-line: 1\">Graceful Switchover (Web Interface)<\/h2>\n<p>Die Dbvisit Web-Oberfl\u00e4che ist sehr \u00fcbersichtliche. Ich verbinde mich auf den Node01 um dort die Operationen zu starten.<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h35_10.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8023\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h35_10.png\" alt=\"2016-04-11_09h35_10\" width=\"645\" height=\"142\" \/><\/a><\/p>\n<p>Ja, klar! Diese Operationen sind nur auf dem prim\u00e4ren Node erlaubt, und das ist der Node02 nach dem letzten Switchover.<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h28_35.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8024\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h28_35.png\" alt=\"2016-04-11_09h28_35\" width=\"639\" height=\"289\" \/><\/a><\/p>\n<p>Schon besser, damit habe ich den Switchover von Node02 zur\u00fcck auf Node01 auf dem Node02 gestartet. Wieder wird ein eindeutiger Key verwendet um sicherzustellen, dass genau dieser Prozess weitergef\u00fchrt werden soll, sobald ich den Key auch auf dem Node01 eingegeben habe.<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h27_24.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8025\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h27_24.png\" alt=\"2016-04-11_09h27_24\" width=\"640\" height=\"531\" \/><\/a><\/p>\n<p>Ist die Eingabe erfolgt, geht es weiter im Prozess des Switchovers.<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h44_34.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8026\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_09h44_34.png\" alt=\"2016-04-11_09h44_34\" width=\"603\" height=\"342\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>Verl\u00e4uft alles korrekt, so ist zum Abschluss, gesamter Log:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">=============================================================\nGraceful Switchover starting on Primary Database orcl.\nTimestamp: 201604110926.\n\n&gt;&gt;&gt; Database orcl will be shutdown and restarted &lt;&lt;&lt;\nEnsure Dbvisit is no longer scheduled.\n\nObtaining archive log gap....\nContacting Standby Database orcl on NODE01...\nNext standby sequence required for recovery (445) for thread 1.\n\nArchive Log Gap for thread 1 is: 0. This is correct to continue. \n\nPlease enter unique key to begin graceful switchover for database orcl. \nThe same key must be entered on both primary and standby server. \n\nPlease start command: dbv_oraStartStop.exe switchover orcl \non NODE01 if not already started. \n\nBatch key will be used: 1122 \nKey 1122 entered. \n\nContacting NODE01 to ensure the same unique key is entered for orcl. \nWaiting for Key 1 on NODE01... \nCheckpoint 1 completed. Key found on NODE01 \nWaiting for Checkpoint 2 on NODE01... \nCheckpoint 2 completed. Key found on NODE01 \nWaiting for Checkpoint 3 on NODE01... \nCheckpoint 3 completed. Key found on NODE01 \nShutting down regular Database orcl... \nRegular Database orcl shutdown successfully. \nWindows Service OracleServiceorcl already started. \nStarting Regular Database orcl... \nRegular Database orcl started restrict. \nPerforming Oracle Checkpoint.  \n\tWaiting 3 seconds for log switch completion...\n\nCreating standby control file as 'C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\n\\orcl\\X.dbvisit.1122.orcl.standbycontrolfile'... \nWaiting for Checkpoint 4 on NODE01... \nCheckpoint 4 completed. Key found on NODE01 \nCopying new archives for orcl to NODE01... \nCompressing O1_MF_1_445_CJPNKFTH_.ARC... \n\tTransferring 'O1_MF_1_445_CJPNKFTH_.ARC.gz' to server NODE01:7890\n\tProgress: 0%...20%...40%...60%...80%...100% [38631 KB\/s] \nCompressing O1_MF_1_446_CJPNMY6F_.ARC... \n\tTransferring 'O1_MF_1_446_CJPNMY6F_.ARC.gz' to server NODE01:7890\n\tProgress: 0%...20%...40%...60%...80%...100% [99472 KB\/s] \nShutting down regular Database orcl...\nRegular Database orcl shutdown successfully.\nCopying redo logs ... this may take a while... \nCompressing X.dbvisit.1122.orcl.redo_1.log... \n\tTransferring 'X.dbvisit.1122.orcl.redo_1.log.gz' to server NODE01:7890\n\tProgress: 0%...20%...40%...60%...80%...100% [239504 KB\/s] \nCompressing X.dbvisit.1122.orcl.redo_2.log... \n\tTransferring 'X.dbvisit.1122.orcl.redo_2.log.gz' to server NODE01:7890\n\tProgress: 0%...20%...40%...60%...80%...100% [66125 KB\/s] \nCompressing X.dbvisit.1122.orcl.redo_3.log...\n\tTransferring 'X.dbvisit.1122.orcl.redo_3.log.gz' to server NODE01:7890\n\tProgress: 0%...20%...40%...60%...80%...100% [232851 KB\/s] \nWaiting for Checkpoint 5 on NODE01... \nCheckpoint 5 completed. Key found on NODE01 \nBacking up current control files for orcl NODE02... \nDatabase orcl on NODE02 is already down. No action taken. \nWindows Service OracleServiceorcl already started. \nStarting Regular Database orcl... \nRegular Database orcl started nomount. \nControl file backed up as C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\\orcl\\X.dbvisit.1122.orcl.controlfile. \nShutting down standby Database orcl... \nStandby Database orcl shutdown successfully. \nWaiting for Checkpoint 6 on NODE01... \nCheckpoint 6 completed. Key found on NODE01 \nWaiting for Checkpoint 7 on NODE01... \nCheckpoint 7 completed. Key found on NODE01 \nWaiting for Checkpoint 8 on NODE01... \nCheckpoint 8 completed. Key found on NODE01 \nWaiting for Checkpoint 9 on NODE01... \nCheckpoint 9 completed. Key found on NODE01 \nWaiting for Checkpoint 10 on NODE01... \nCheckpoint 10 completed. Key found on NODE01 \nWaiting for Checkpoint 11 on NODE01... \nCheckpoint 11 completed. Key found on NODE01 \nWaiting for Checkpoint 12 on NODE01... \nCheckpoint 12 completed. Key found on NODE01 \nDatabase orcl on NODE02 is already down. No action taken. \nWindows Service OracleServiceorcl already started. \nStarting Regular Database orcl... \nRegular Database orcl started nomount. \nSTANDBY control file(s) restored from C:\\PROGRA~2\\Dbvisit\\standby\\tmp\\GS\n\\orcl\\X.dbvisit.1122.orcl.standbycontrolfile. \nShutting down standby Database orcl... \nStandby Database orcl shutdown successfully. \nWindows Service OracleServiceorcl already started. \nStarting Standby Database orcl... \nStandby Database orcl started . \nWaiting for Checkpoint 13 on NODE01... \nCheckpoint 13 completed. Key found on NODE01 \nWaiting for Checkpoint 14 on NODE01... \nCheckpoint 14 completed. Key found on NODE01 \nFile C:\\Program Files (x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env copied to \nC:\\Program Files (x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env.201604110926. \nDbvisit Database configuration (DDC) file C:\\Program Files \n(x86)\\Dbvisit\\standby\\conf\\dbv_orcl.env has been updated and variables have \nbeen reversed between primary and standby server. \n\nSOURCE=NODE01 DESTINATION=NODE02. \n\nWaiting for Checkpoint 15 on NODE01... \nCheckpoint 15 completed. Key found on NODE01 \nUncompressing O1_MF_1_445_CJPNKFTH_.ARC.gz... \nUncompressing O1_MF_1_446_CJPNMY6F_.ARC.gz... \nWaiting for Checkpoint 16 on NODE01... \nCheckpoint 16 completed. Key found on NODE01 \nWaiting for Checkpoint 17 on NODE01... \nCheckpoint 17 completed. Key found on NODE01 \nWaiting for Checkpoint 18 on NODE01... \nCheckpoint 18 completed. Key found on NODE01 \n\nGraceful switchover completed. \n\nThis database (orcl) is now a standby database. \nTo keep this new standby database in synch, \nreschedule Dbvisit as per normal: \ndbvisit orcl<\/pre>\n<p>Wie im Log zu sehen ist, ist der Switchover erfolgreich gewesen und die Datenbank l\u00e4uft nun wieder auf dem prim\u00e4ren Node01.<\/p>\n<p>Bei den Varianten eines Switchovers wir grunds\u00e4tzlich unterschieden zwischen einem Kontrollierten Switchover (Graceful Switchover) und einem richtigen Failover, nach einem Ausfall des Prim\u00e4ren Servers.<\/p>\n<h2>Failover<\/h2>\n<p>Den ersten Fall haben wir nun bereits durchgespielt, jetz m\u00f6chte ich noch den Failover nach einem Ausfall des prim\u00e4ren Servers sehen:<\/p>\n<p>Dazu stoppe ich den prim\u00e4ren Server Node01 und verbinde mich auf das Web-Interface des Node02:<\/p>\n<p>Jetzt gehe ich unter HOME-&gt;RUN-&gt;RUN INTERACTIVE auf den Standby Server und w\u00e4hle dort Activate aus:<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_10h20_38.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8031\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_10h20_38.png\" alt=\"2016-04-11_10h20_38\" width=\"632\" height=\"397\" \/><\/a><\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_10h23_04.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8033\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_10h23_04.png\" alt=\"2016-04-11_10h23_04\" width=\"633\" height=\"129\" \/><\/a><\/p>\n<p>Somit erzwinge ich die Standby Database die Rolle als prim\u00e4re Database zu \u00fcbernehmen! Dabei gibt es keinen Weg mehr zur\u00fcck zur alten prim\u00e4ren Datenbank auf dem Node01!<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_10h26_22.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-8034\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-04-11_10h26_22.png\" alt=\"2016-04-11_10h26_22\" width=\"643\" height=\"778\" \/><\/a><\/p>\n<p>Somit haben wir jetzt keine Standby Datenbank mehr, diese muss nun neu aus der aktuellen prim\u00e4ren Datenbank auf dem Node02 erstellt werden.<\/p>\n<p>Damit die Standby neu erstellt werden kann, muss sie zuerst gestoppt werden auf dem Node01, danach kann eine neue Standby erstellt werden, diese Aufgabe kann Dbvisit Standby vollst\u00e4ndig \u00fcbernehmen. Achtung, nicht vergessen auf dem alten prim\u00e4ren Server Node01, m\u00fcssen alle alten Datenbankfiles gel\u00f6scht werden, bevor der Prozess zur Erstellung der Standby Datenbank gestartet wird.<\/p>\n<h2>Fazit<\/h2>\n<p>Der Einsatz des Produktes Dbvisit Standby eignet sich ausgezeichnet um eine Hochverf\u00fcgbarkeitsl\u00f6sung basierend auf Oracle Standardedition zu erstellen. Es ist nicht m\u00f6glich eine 0 Downtime L\u00f6sung zu erstellen, jedoch kann eine RTO von &lt; 10 Minuten erreicht werden. Die RPO nahe\u00a00. In einem Worstcase, k\u00f6nnen je nach Konfiguration auch kleinere Werte erreicht werden. Das Produkt Dbvisit arbeitet auch auch unter Windows zuverl\u00e4ssig und ist \u00fcber eine Web-Oberfl\u00e4che sehr gut zu bedienen. Damit ist es eine gute Alternative, unter Linux oder Windows wenn eine Oracle Enterprise Edition zum Einsatz kommt um Hochverf\u00fcgbare Datenbanken zu betreiben.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ausgangslage Wie gut l\u00e4sst sich mit Oracle Standard Edition unter Windows eine Hochverf\u00fcgbarkeitsl\u00f6sung aufbauen? Die Basis, zwei Windows Server 2012 R2, Oracle Standard Edition und Dbvisit Standby. Die eingesetzte Version Dbvisit Standby 7.0.48.15006. Die eingesetzte Oracle Version\u00a012.1.0.2.0. Installation Die Windows Installation ist Standard, nur die beiden Server m\u00fcssen, zwecks Namensaufl\u00f6sung im Hosts File(C:\\Windows\\System32\\drivers\\etc\\hosts) unter Windows [&hellip;]<\/p>\n","protected":false},"author":27,"featured_media":6898,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[732,733,459,509],"type_dbi":[],"class_list":["post-6882","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","category-database-management","tag-dbvisit-standby-version-7","tag-hochverfugbarkeit","tag-oracle-standard-edition","tag-windows-server-2012-r2"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Dbvisit Standby Version 7 auf Windows Server 2012 R2 - dbi Blog<\/title>\n<meta name=\"description\" content=\"Erstellung einer Hochverf\u00fcgbarkeitsl\u00f6sung mit Dbvisit, basierend auf Oracle Standardedition unter Windows.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dbvisit Standby Version 7 auf Windows Server 2012 R2\" \/>\n<meta property=\"og:description\" content=\"Erstellung einer Hochverf\u00fcgbarkeitsl\u00f6sung mit Dbvisit, basierend auf Oracle Standardedition unter Windows.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-04-12T06:39:28+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"501\" \/>\n\t<meta property=\"og:image:height\" content=\"131\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Dbvisit Standby Version 7 auf Windows Server 2012 R2\",\"datePublished\":\"2016-04-12T06:39:28+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\"},\"wordCount\":1113,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png\",\"keywords\":[\"Dbvisit Standby Version 7\",\"Hochverf\u00fcgbarkeit\",\"Oracle Standard Edition\",\"Windows Server 2012 R2\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\",\"name\":\"Dbvisit Standby Version 7 auf Windows Server 2012 R2 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png\",\"datePublished\":\"2016-04-12T06:39:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"Erstellung einer Hochverf\u00fcgbarkeitsl\u00f6sung mit Dbvisit, basierend auf Oracle Standardedition unter Windows.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png\",\"width\":501,\"height\":131},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Dbvisit Standby Version 7 auf Windows Server 2012 R2\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Dbvisit Standby Version 7 auf Windows Server 2012 R2 - dbi Blog","description":"Erstellung einer Hochverf\u00fcgbarkeitsl\u00f6sung mit Dbvisit, basierend auf Oracle Standardedition unter Windows.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/","og_locale":"en_US","og_type":"article","og_title":"Dbvisit Standby Version 7 auf Windows Server 2012 R2","og_description":"Erstellung einer Hochverf\u00fcgbarkeitsl\u00f6sung mit Dbvisit, basierend auf Oracle Standardedition unter Windows.","og_url":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/","og_site_name":"dbi Blog","article_published_time":"2016-04-12T06:39:28+00:00","og_image":[{"width":501,"height":131,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png","type":"image\/png"}],"author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Dbvisit Standby Version 7 auf Windows Server 2012 R2","datePublished":"2016-04-12T06:39:28+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/"},"wordCount":1113,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png","keywords":["Dbvisit Standby Version 7","Hochverf\u00fcgbarkeit","Oracle Standard Edition","Windows Server 2012 R2"],"articleSection":["Database Administration &amp; Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/","url":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/","name":"Dbvisit Standby Version 7 auf Windows Server 2012 R2 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png","datePublished":"2016-04-12T06:39:28+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"Erstellung einer Hochverf\u00fcgbarkeitsl\u00f6sung mit Dbvisit, basierend auf Oracle Standardedition unter Windows.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2016-01-18_09h55_44-1.png","width":501,"height":131},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standby-version-7-auf-windows-server-2012-r2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Dbvisit Standby Version 7 auf Windows Server 2012 R2"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/6882","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=6882"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/6882\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/6898"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=6882"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=6882"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=6882"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=6882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}