Disaster recovery with replication for VSphere

Am just test VSphere 5 of replication. with a couple of test VMs

The replication process works very well

What I want to know is the process to recover a VM replicated to new hardware in the case of the complete failure of the original host and/or data store

In essence, disaster recovery.

Are there other parts (software), that I need to take the replica VMDK and files related to re - create a new virtual machine on a new host

Steve

Yes, because it will be all your hard and .vmx files.

Tags: VMware

Similar Questions

Restore with replication of vSphere

Hello
We use SRM 5.1 with replication of vSphere.
I'm trying to get a rough idea of how long a reprotect operation would take after a failover, especially synchronization of storage.
The manual says that:

"The full synchronization that appears especially in the stages of recovery performs control totals, and only a small amount of data is transferred over the network."
However in my testing this step still seems to take a long time to complete. For a person of 50 GB, it takes 40 minutes. My question is: what is the bottleneck here and I can speed things up?
In a live scenario, I have much larger comments VMs and I fear that a reprotect could take days to synchronize the storage.
Thank you
Steve

The full synchronization bed basically just for the disk data and checksum data. It also makes requests to read the data and return a set of checksums remotely. He would only send the data if the checksums do not match. Thus, assuming that not many disk changed, there is very little except checksum travel over the network. So you will respect especially how fast you can read files vmdk on both sites and to a lesser extent by the latency of the network between the sites, and, of course, if the link between the sites remains upward.

Check if the link to the sites is good. Get often ignored or not connections are limited somehow? The latency is extremely high, as hundreds of milliseconds? This can slow things down.

On the source site, make sure that the storage is not overloaded with other work. In the case of NAS/ISCSI, check also that there is no other work of network hogging bandwidth. Sometimes, there are periodic offers on secondary sites, like backups, and that people often forget this can be a lot of resources.

On the destination site, carry out similar checks and make sure that the server VR is to get a reasonable amount of network and CPU resources.

Disaster recovery with different ASM starts

Hi@all,
in fact, I'm testing a scenario of recovery after a disaster. To an Oracle Linux 6 Server with installed grid below 12 c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 instance of database) I'm doing a recovery after a disaster. But I'm unleashed by the restoration and recovery of the database. The problem here is that ASM diskgroup name has changed. As you read I also changed the physical server, but I think that should not be a problem.
To the old server, I have two ASM starts '+ DATA' and '+ FRA_1', to the new, they are called '+ DATA_SRVNAME' and '+ FRA_SRVNAME '. I already changed the startup in spfile parameter, but now after restoring the controlfile RMAN has directions to the old diksgroup:
```
RMAN> report schema;


using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name SID


List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1    0        SYSTEM               ***     +DATA/SID/datafile/system.438.816606399
```
So I tried three ways. First was rename data file name:
```
ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';
```
Then had to set the newname in RMAN:
```
set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';
```
And the second was to recreate the controlfile with
```
CREATE CONTROLFILE REUSE DATABASE "SID" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 1
    MAXLOGHISTORY 1815
LOGFILE
  GROUP 1 ('+DATA__SRVNAME', '+FRA_SRVNAME')  SIZE 1024M,
DATAFILE
  '+DATASRVNAME/SID/datafile/system.438.816606399',
CHARACTER SET AL32UTF8;
```
But the three methods gave me the error that the file data to the new location is not available (for example):
```
ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist
```
So now my question: how am I able to say the controlfile or the database to use the another diskgroup in ASM?
I know, the simplest way would be to create a diskgroup + DATA and do the restore / recovery, but on the new server, I have no more storage to assign to a new diskgroup, and because there are running other forums I would'nt change ASM starts.
Do you have anny solution?
A big thank you and best regards,
Dave

Please try this

RMAN > run

{

the value of newname for datafile 1 to "+ DATA_SRVNAME";

restore data file 1;

switch datafile 1;

recover datafile 1;

}

Did you create + diskgroup DATA_SRVNAME?

and

Oracle Database Disaster Recovery SAN replication consistency

Hi all
just a quick question after a long search and not yet knowing the answer.
What technology or configuration do I need make the eve of Oracle DB compatible on asynchronous SAN replication between cities?
The version is Oracle Standard Edition 11 g, then the enterprise like DataGuard and GoldenGate features aren't possible?
Entire database replication Oracle Streams don't work?

Hello

You can do it yourself (as everyone else used to do many years ago), to a product like dbvisit which is popular in this space (never used, but I heard good things about this). Streams can do it, but I think he uses triggers rather than redo log mining so he can have more impact on the source system.

SAN replication is possible but probably very expensive and you should be sure it correctly handles oracle blocks - the seller must be able to tell if it is certified or not.

See you soon,.

Rich

Disaster recovery with Ghettovcb on EXSI

Hello team,
I started working with EXSI and the backup and restore of virtual machine through ghettoVCB successfully completed.
But I got over a spot...
situation is something like:
1. what got esxi crashed then how to quickly recover the new esxi?
2 and if the new exsi is created then the new deployment of the backup of virtual machine on exsi?
The team please provide guidelines about this situation...

Thank you

Hi sumitanand,

It is technically possible to clone partitions starting ESXi? Maybe you can, but you should never do that.

As Phatsta mentioned already install a new host is done in a very short period of time (depending on your hardware you can minutes)

In addition, you can indeed do a boot from the disk backup (or just install on USB and do that 2 times on different USB sticks) however...

What happens if your host is completely dead? You get a new server with different hardware... and specific drivers from different vendors? Your cloned image does not work, then, as the excellent.

In addition, using a cloned image of ESXi is completely supported.

If you want to save configuration ESXi host using something like this:

PowerCLI: ESXi 5.0 / 5.1 ESXi backup host & restore the usefulness of GUI - VI - Toolkit

and then apply to your freshly installed ESXi host.

--

Wil

Disaster recovery with VM

I saw that many people use VM to use as backups of physical servers and thinking of doing the same thing. However, once I've virtualized all of my servers does make sense to keep the original servers at all? Should I just move in a completely VM server environment?

The only reason to keep the physical servers would be to conduct a v2P if you had a problem with an application or piece of software, and that the seller required that demonstrate you that occur the same problem on a physical server as opposed to a virtual machine.

If you have verified that all your software is virtualized supported and/or you agree to the policies of support of suppliers such as MS and understand the implications of my first point, there is very little interest to maintain the servers.

The other thing to consider is a virtual machine can still be fired using the VMware software, Quest, Veaam, doubletake... etc - so if you still need DR a virtual machine is a server easier to deal with and to bring to a physical server.

Problem with different ASM disaster recovery start - new

Hello together,

I had an old net here about it but now will not solve the problem with the points in the old thread. Here's the old: https://community.oracle.com/thread/3608049?start=0 & tstart = 0

I'm doing a disaster recovery with the 'apex11A' on a new server database, which has an another ASM starts. The old man starts is '+ DGA112_1' and '+ FRA112_1', newcomers are called '+ DATA_QUM169' and '+ FRA_QUM169 '. I changed the settings in the spfile restored by writing in a pfile file and creating the spfile from pfile.

I tried in several ways. First lay the new ASM with RMAN to the course:

run
{
SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

Then I tried it in RMAN by defining the new ASM for each data file:

run
{
SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

Then I tried the bot in one:

run
{
SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

Whenever I get one

Starting restore at 03-FEB-16
using channel ORA_DISK_1


creating datafile file number=1 name=+DATA_QUM169
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/03/2016 16:20:41
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'

The backuppiece which I bring are correctly defined with

RMAN> catalog backuppiece '/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1', '/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1';


cataloged backup piece
backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1 RECID=3779 STAMP=902851052
cataloged backup piece
backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1 RECID=3780 STAMP=902851052


RMAN> list backup;




List of Backup Sets
===================




BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3779    52.61M     DISK        00:00:00     03-FEB-16
        BP Key: 3779   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145340
        Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1


  List of Archived Logs in backup set 3779
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    24285   11073415926066 03-FEB-16 11073416327345 03-FEB-16
  1    24286   11073416327345 03-FEB-16 11073416678326 03-FEB-16


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3780    Full    813.86M    DISK        00:00:00     03-FEB-16
        BP Key: 3780   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145042
        Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1
  List of Datafiles in backup set 3780
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/system.1423.788355253
  2       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/sysaux.1422.788355259
  3       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/undotbs1.1359.788355263
  4       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/users.1362.788355273
  5       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4.1369.788356305
  6       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4_files.1366.788356317
  7       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms_archiv.1358.788357229
  8       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/planwerte.1357.788357243
  9       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_prod.1352.788456613
  10      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais.1353.788456763
  11      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms.1354.788456995
  12      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/externe_wirk.1355.788457525
  13      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2mt.1356.788458151
  14      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_read.1351.788458291
  15      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329
  16      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657
  17      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/macmon.1340.788458691
  18      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais_read.1339.788458725
  19      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2srm.266.788458799
  20      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859
  21      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/quickcheck.1338.788458887
  22      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/switch.1337.788459139
  23      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/veit_r.1333.788459167
  24      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/test-btdb.1298.795097725
  25      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11dev.986.874230931
  26      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11devbt.985.874230963
  27      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hrbew.1083.851007823
  28      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/optimadata.1032.865951029

I also tried to put the new ASM SQL:

SQL*Plus: Release 11.2.0.4.0 Production on Wed Feb 3 16:04:05 2016


Copyright (c) 1982, 2013, Oracle.  All rights reserved.




Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Automatic Storage Management and OLAP options


SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 1 - new file '+DATA_QUM169' not found
ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 2 - new file '+DATA_QUM169' not found
ORA-01110: data file 2: '+DGA112_1/apex11a/datafile/sysaux.1422.788355259'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 3 - new file '+DATA_QUM169' not found
ORA-01110: data file 3: '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 4 - new file '+DATA_QUM169' not found
ORA-01110: data file 4: '+DGA112_1/apex11a/datafile/users.1362.788355273'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 5 - new file '+DATA_QUM169' not found
ORA-01110: data file 5: '+DGA112_1/apex11a/datafile/apex4.1369.788356305'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 6 - new file '+DATA_QUM169' not found
ORA-01110: data file 6: '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 7 - new file '+DATA_QUM169' not found
ORA-01110: data file 7: '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 8 - new file '+DATA_QUM169' not found
ORA-01110: data file 8: '+DGA112_1/apex11a/datafile/planwerte.1357.788357243'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 9 - new file '+DATA_QUM169' not found
ORA-01110: data file 9: '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 10 - new file '+DATA_QUM169' not found
ORA-01110: data file 10: '+DGA112_1/apex11a/datafile/mais.1353.788456763'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 11 - new file '+DATA_QUM169' not found
ORA-01110: data file 11: '+DGA112_1/apex11a/datafile/mms.1354.788456995'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 12 - new file '+DATA_QUM169' not found
ORA-01110: data file 12:
'+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 13 - new file '+DATA_QUM169' not found
ORA-01110: data file 13: '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 14 - new file '+DATA_QUM169' not found
ORA-01110: data file 14: '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 15 - new file '+DATA_QUM169' not found
ORA-01110: data file 15: '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 16 - new file '+DATA_QUM169' not found
ORA-01110: data file 16: '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 17 - new file '+DATA_QUM169' not found
ORA-01110: data file 17: '+DGA112_1/apex11a/datafile/macmon.1340.788458691'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 18 - new file '+DATA_QUM169' not found
ORA-01110: data file 18: '+DGA112_1/apex11a/datafile/mais_read.1339.788458725'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 19 - new file '+DATA_QUM169' not found
ORA-01110: data file 19: '+DGA112_1/apex11a/datafile/mais2srm.266.788458799'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 20 - new file '+DATA_QUM169' not found
ORA-01110: data file 20:
'+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 21 - new file '+DATA_QUM169' not found
ORA-01110: data file 21: '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 22 - new file '+DATA_QUM169' not found
ORA-01110: data file 22: '+DGA112_1/apex11a/datafile/switch.1337.788459139'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 23 - new file '+DATA_QUM169' not found
ORA-01110: data file 23: '+DGA112_1/apex11a/datafile/veit_r.1333.788459167'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 24 - new file '+DATA_QUM169' not found
ORA-01110: data file 24: '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 25 - new file '+DATA_QUM169' not found
ORA-01110: data file 25: '+DGA112_1/apex11a/datafile/apex11dev.986.874230931'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 26 - new file '+DATA_QUM169' not found
ORA-01110: data file 26: '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 27 - new file '+DATA_QUM169' not found
ORA-01110: data file 27: '+DGA112_1/apex11a/datafile/hrbew.1083.851007823'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 28 - new file '+DATA_QUM169' not found
ORA-01110: data file 28: '+DGA112_1/apex11a/datafile/optimadata.1032.865951029'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form

But my new database will not set the new ASM and I have no why.

The db_create_file_dest parameter is set correctly, so I think that:

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_create_file_dest                  string      +DATA_QUM169

I forgot something? Would be nice to get help ...

A big thank you and best regards,

David

Your data checkpoint SCN file are in the LOW and HIGH range of the SNA for SEQUENCE 24286.

Therefore, your UNTIL clause should be 24287 SEQUENCE up to THAT.

Hemant K Collette

Can we create a Vlan without SRM for disaster recovery testing

We are working on plans for our recovery after disaster in our VMWare environment. We have a recovery Site which has a NETAPP file server we reproduce our VM data warehouse and SQL data. We have no RS, but must be able to test if possible disaster recovery with Production upwards. Is it possible to configure a VLAN and do a test isolated Dr. without SRM? Thank you

Welcome to the VMware communities forum.

You can create a VLAN without SRM. You will need to properly set up your network hardware, and then you add new virtual machine port groups to your ESXi hosts. You can then save the virtual machines by giving them a different name and starts in isolation. When you attempt to save the virtual machines they will always have a reference for the port VM production group so you'll want to make sure you update you turn on.

Move cluster configured with replication SRM and Vsphere

All,
We go 2 groups in the near future to achieve a geographical distance between the 2 sites.
A cluster is equipped with VMware 5.0 replication SRM and vSphere and the other cluster running VMware 5.5 and SRM in combination with replication of vSphere.
What is the best way to move these clusters, I must stop the replication or interrupt the replication process and are these action to perform on SRM or we need to perform any action on the virtual machine itself?
I read that a stop is setting the State to not configured including destroy all files in the target directory.
Does anyone have an experience by physically moving a cluster managed by SRM (and replication of vSphere)
Any help is welcome
Thank you
Gerbert Coolen

Just pause replication before stop you the VR device on the site target/DR. stop vs break with vSphere replication - VMware vSphere Blog - Articles from VMware

SRM using the issue of replication VRMS vSphere

Hi guys,.
Basically normally when using vsphere replication, if you lose the VRM, then you cannot recover your virtual machines.
'With the VRMS device in offline mode, it is not possible to recover virtual machines with vSphere replication. There are some items of third person out there that suggest that it is possible to manually change the files to the target location that make up the replica and recover a virtual machine. "While this is possible, I do not recommend relying on this method of recovery, because it's a very manual process and, above all, not supported by VMware "
vSphere replication device failure and recovery prevention | VMware vSphere Blog - VMware Blogs
Am I right in thinking that when you use SRM with replication of vsphere, this isn't a problem that you can 'force' recovery with MRS... .where is it always going to be a problem?
This is a question published iI in Re: 1 primary replication running unit and 1 device running the module
Cheers for the help guys!

As Martin mentioned in the other thread, VR (and SRM when using VR) require work VRMS at the location of the target/recovery. To clarify your statement, read: "when using vsphere replication, if you lose the VRMS on the site of your target/recovery , then you cannot recover your virtual machines.

With MRS is still a problem, but normally if your production site is affected it will not be an impact on VRM on the recovering site you will always be able to recover. Enforcement is where any operation is attempted on a protected site, so it's really for a different use case.

Does that answer your question?

vCloud Air Disaster Recovery - vSphere replication of specific records

In the most recent documentation for vSphere replication, the ability to select specific disks when you replicate a single workload is described:
Documentation Centre of vSphere 5.5
However, in the videos of vCloud Air DR, this option is not currently available. Is - this specific to Air DR vCloud or some videos of previous versions?
vCloud Air Disaster Recovery: configuration of the Virtual Machine replication - YouTube

Answer: No.

http://vjourneyman.com/replicating-to-vCloud-air-Dr

Requirements for vSphere remote site replication

I run 3 Enterprise 5.5 x vSphere hosts in A Site with vCenter. I want to add a new host in a remote site and configure vSphere replication between them. Issues related to the:
- Do I need to vCenter in slot 2?
- If vCenter Site of A is the Site management and hosts of the Site B and Site A goes down, vSphere replicated VMs can be restarted to Site B without problem?
- Is there a risk to not have a vCenter dedicated to Site B on the changeover plan?
Thank you
-Matt

Hello

(A) If you have vCenter in slot 2, you will need to deploy device VR and match two VR UI sites.

In the case where something happens to site A, losing vCenter and/or VR device, you can use vCenter and VR device to site B to perform a recovery after disaster and put in place the VMS to site B, inside of vCenter inventory B.

(B) If you have no server vCenter in slot 2:

1. There is no need to deploy handset unit of VR (embedded DB for server VRMS + VR + VRMS) for site B.

2. you can deploy additional device VR-server only for site B, so that the replication traffic goes directly from the source ESXi to the correct server in VR.

3. If the disaster arrives at the site, you must have vCenter Server and VRM in the combined unit of VR upward and running order to use the VR UI to perform a disaster recovery. If vCenter Server or VRMS manage warehouses of data target is corrupted/lost, the only way to recover after a disaster is to consolidate recovery replica logs manually rename and replicated configuration files and hope that consolidated records represent a coherent source VM instance. This procedure is subject, not officially supported, and care must be taken when building the redo logs, in order to ensure the consistency of the data in the disks of the virtual machine, not some partial block updates.

Kind regards

Martin

Go with SRM or replication of VSphere

Hi all
I'm looking for a review here.
In our current environment, 600 more VM is get replicated to disaster recovery site using third-party replication tool. As we intend to upgrade our whole environment to vSphere 5.1, we intend to use the replication of vSphere. We do not plan to use SRM at this point.
We have two Vcenters, one for the env Prod and other for Dr. approx. We have our replication go on a dedicated channel for OC / 24.
We are not woried about the Automation and do not come back to this point, MRS is not a choice at this point.
Questions.
1. with the limitation of 500 rehearsals (employment) for the unit of replication VSphere, ho we satisfy our need of 600 replications?
2. can we use vSphere several devices of replication on each site (by vcenter) without using SRM?
3. If it says 500 is the maximum supported, loads of work how I can configure on device for proper operation.
4. should I consider SRM in this stadium? If yes why?
Appreciate your help in this regard.
Thank you
Dembélé

I see, but I guess that at least for a start and a conecpt evidence of the use of VR, a single VRS is enough. In addition, you can always high-end to SRM later and get better performance with the deployment of new technologies...

Procedures and guidelines for Disaster Recovery (DR)

Hi all
Our TI auditor asked me to submit/provide procedures for guidelines for disaster recovery.
I tried Google, but the process docs seem so vast and complex.
We have a dataguard configuration. Can I give him to the contrary the docs on how to recover/restore using Data Guard?
Can you share me link to good documentation on the recovery?
Thank you
Petra k.

> We have a dataguard configuration

Generally, the documentation is created with the Setup program. Documentation describing the configuration. Documentation detailing the procedures for different situations. Documentation that lists the commands to use and the expected responses for commands. Documentation that indicates the error handling methods if you try the commands.

Your dataguard configuration is incomplete without these documents.

Hemant K Collette

who can help me with "insufficient resources to meet the level of failover configured for vSphere HA.

Hello world
We tried to gif a 14GB of ram and make server complete a booking for her.
This is a server for the exams and the vendor told us to do.
I can't any more then 5500MB reservation on it, when I anymore that I get
"Insufficient resources to meet the level of failover configured for vSphere HA.
We have:
2 X 5.1 ESXi hosts
Each host has
2 x processors (8 Cores each) with HT active.
255,75 GB of Ram
vSphere HA has been activated.
Admission control policy is enabled and that the ability to failover is 1 host.
What is the problem here?
Thank you
Ernst.

Admission control policy is all about to give you the kind of guarantee that if the host failure happens then there will be enough resources to perform the successful failover.

in simple terms, it comes to reserve the resources of failover.

I would recommend going through the notion of vSphere HA, reduced control policy the following document.

https://pubs.VMware.com/vSphere-60/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-60-availability-Guide.PDF

From the Page number 22, the details that you need to study is given. Focus especially on part calculations Slot size of it.

in your case you HA vSphere with number of failure of host to tolerate as admission control strategy defined.

This means system will calculate CPU and memory slots out of the resources in your cluster, and the total number of units, it will keep some resources like reserved for failover, and others will be available to be used. It all depends on how much failure of hosts that you want to tolerate.

now in your case, if you try to increase booking one of the virtual machine, which will then affect the number of locations in your environment, and so reserved ability to failover is violated, the system will not let you do what you want to do. As the energy on a virtual machine, or growing booking a powered VM etc..

If you find that you have enough resources in your cluster and due to some virtual machines with very large cpu or memory reservation, number of places is less than you can still manage the settings some advanced in vSphere HA configuration, but I strongly recommend, try to take the help of someone who has done it before.

also try to go through other admission control strategies which are explained in the document for more inputs.

Disaster recovery with replication for VSphere

Similar Questions

Maybe you are looking for