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.

Tags: VMware

Similar Questions

  • 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.

  • 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

  • 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

  • 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.

  • OBIEE Disaster Recovery can be configured without CARS and shared storage?

    Hi people,

    As say the topic, I'm looking for advice on disaster recovery. What I find in the docs pointing me to the high availability configuration, or maybe I'm simply not find the docs I'm looking for. And it always points to the RAC, etc. of shared storage. My database is already configured to Dataguard and I want to do things this way, with a recovery site which isn't always upwards and a part of a cluster (although it's very well as long as the CAR is not involved), I'm looking for some feedback on how people do things. I have 11.1 now, but will be upgrading to 12.2 soon.  Just a straight stitch to the documentation would be useful if I'm missing just that.

    Thank you

    -Adam

    Since you have already configured Dataguard and in a DR situation, you will be switching/switch on your course in standby mode and it will active db. All this is fine. You can do the same with instances of weblogic OBIEE. You can clone your binaries installed using tools provided by Oracle cloning, or build binaries from weblogic with the accurate determination of drive on your Dr. use the pack of weblogic server and then unzip tool to archive your entire weblogic domain and it Unarchive in your prepared DR server.

    Now, you have to just challenge the hostname (s) of your domain to point to your database JDBC data sources and weblogic.

    To facilitate the task, you can change the host name used by weblogic to host alias that can be remapped in DNS during DR. Similarly, you can change the JDBC connection string so that it can automatically select the active database as long as you use a database instead of a SID service name in the connection string.

    You will need to regularly make a pack on your weblogic domain in order to maintain an up-to-date backup of your domain proximity. Similarly, if you have reports that are stored on the file system, they must also be backed up regularly so that they can be restored.

  • Difference between disaster recovery (replace the user's machine) and material migration Assistant.

    Hi all

    I worked at different scenarios for customers supported the migration of material.

    I found "Disaster recovery (replace the user's machine)" will perform the same action as the 'migration Hardware' option Assistant in common.

    Please let me know if the two are same with operations or any difference is there?

    Essentially, they do the same for the different use cases. The only difference is the default option selected for the computer name in the wizard. Migration of HW, it is 'Set Name'. In the Assistant of Dr., is "to keep the name of CVD.

  • vCloud Air - Disaster Recovery - Europe - UK

    Please can someone advise where Europe - UK datacentres are based, whereas the vCloud service Air Disaster Recovery.

    All links related to security and compliance would be welcome.

    The service is available for re - sale by any partner VMware or only those with a certain specialization / accreditation.

    Thank you

    Hi Ben,

    Answers to your questions:

    -You can see the vCloud updated map to know where on the Web site: vCloud locations - VMware vCloud Air Air

    If you need a more specific location (for put in a private line, MPLS/VPLS), you can see them here: Direct Connect - VMware vCloud Air

    -Info security & compliance is here: reports of Certifications of compliance - VMware vCloud Air the AT101 full compliance are available under NDA - you will need to contact your VMware representative for this.

    -Partners VMware must reach their hybrid Cloud competence to transact

    Hope that helps!

    Jenny

  • 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

  • Disaster recovery HFM

    We have in time real copy changes of the drive Bay to PROD server to the drive Bay PREPRODUCTION server for database servers, server FDM and Essbase servers.

    Now my question is, can the above PREPRODUCTION server that receives the data from PROD in real-time, act as a UAT Server?

    By UAT server, I mean, the developers will make changes to metadata and rules in DEV server and even load in the above mentioned PREPRODUCTION server and when successful, the same will be loaded into the Production finally.

    Now could you please tell me if the PREPRODUCTION can act as a UAT for them, as it is copied from the PROD in real-time?

    Thank you

    Siva Bhojan

    In reality, it will not work.

    Assuming that your disaster recovery application works by taking tables and copy those above, you will copy the metadata/rules with her.  If you do not copy those, then your backup is not valid for a disaseter recovery.

    Since the metadata/rules are copied from PROD, the work done by developers would be replaced.

    If your Backup DR process moves only data/logs and reconsolidate, so yes, in theory, it could work, but your DR process missing crucial files needed to make the application work.  Not to mention, there is the possibility of the backup fails when metadata is out of synce between the two.

    All in all, not something I would say.  You are better to keep separate UAT and DR.

  • Physical-TO-virtual disaster recovery

    Hi, what would you do in this scenario?

    • A heterogeneous set of physical servers (with Linux or Win) owned and operated by several customers in different locations.

    • A vSphere on a centralized site infrastructure.

    I wish I had in my infrastructure, a VM power off to each of the remote servers in physics and to keep the image of VM in phase with the remote disks.

    In the case of a remote site explodes, the corresponding virtual machines are started (automatically or manually) as a quick and effective disaster recovery solution...

    Forget the problems of network/IP of this scenario, is there a way or a 3rd party software to keep a VM'd synch with a remote server physical?

    Thank you!

    PlateSpin Protect will be repeated. You place the platespin on the physical server agent and you can replicate the server to an image file or a virtual machine. You can update the image or VM file on a regular basis. It comes from platespin powerrecon product.

    Check it out.

    http://www.PlateSpin.com/products/protect/

    Don't forget to leave some points for messages useful/correct.

  • Problems of recovery with satellite A30 303

    I launched the recovery utility, and then I selected the recovery mode in advance that my hard drive is partiotioned, and I didn't want to format the second partition where different data files were stored.
    The first recovery disc has been loaded and files have bben transferred, then when you are prompted to load the secondary drive an error message as single user are not allowed... has been shown.

    Abandonment of the utility and after rebooting I got following messages:

    Error reading registration MFT VOLUME FILE_
    Internal error 25030
    An internal inconsistency was detected
    Ok

    Then two pages of lines BACK describing the situation.
    The PC unbootable.

    Hello

    This first time that perform you the installation of recovery with comes from Toshiba Recovery CD? If this isn't the case, it is the first time that this problem occurred?

  • Satellite A300 - how to use the recovery with external DVD drive disc?

    Hello

    I bought a toshiba Satellite A300 - 15 d

    FTM the tsscorp drive that is installed in the camera no longer works (does not detect any type of media what so ever). ) need to recover the laptop, so I used a USB DVD drive to boot from the restore disc, but after that the charges of recovery console it says waiting for media in the f: drive, which is the tsscorp drive although I used an external drive to load the disc.

    What files should I edit to make it to load from the drive externally and if this isn't the solution, what do I do?

    Thanks in advance

    Hey Buddy,

    Unfortunately I think that it of not possible to use the recovery with external CD/DVD drive disc. Therefore, place the internal for use the recovery disc.
    You can get a new drive to an authorized service provider.

    But if the original OS from Toshiba is installed, you can use the function of disk recovery HARD reinstall Windows as well. Go to the advanced boot menu (F8) and select Repair my computer :)

  • Can I combine the recovery with other Partition?

    Recently, I upgraded my Dell Inspiron to Windows 7 with the upgrade in free option.  However, I was wondering if there was a way to merge the recovery with the primary partition partition so that I can use this space with the main partition.  Any ideas?

    I don't think so, the extended Volume space can be merged to the main partition.
    Acronis Disk Director Suite allows you to merge... I had ealier. -Ramesh Kumar http://www.WindowsValley.com

Maybe you are looking for