9.2.0.6 RMAN Disaster recovery issue

Our production database crashed and we are doing DR on a new host.
We dont have any catalog database and we dont use controlfile autobackup.
We just do a full backup including controlfile and also archive logs
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
run {
allocate channel d1 type disk;
backup database format '/data/TESTDB/rman/testdb_bk_%s_%p_%t' include current controlfile;
backup archivelog all format '/data/TESTDB/rman/testdb_al_%s_%p_%t' delete input;
release channel d1;
We copied these backup pieces to the new host and tried the following way to restore the database.
startup nomount
rman
connect target /
RMAN> set DBID 2507695351;
executing command: SET DBID
RMAN> run
2> {
3> allocate channel d1 type disk;
4> restore controlfile from '/data/TESTDB/rman/testdb_bk_2_1_724368405';
5> }
allocated channel: d1
channel d1: sid=12 devtype=DISK
Starting restore at 14-JUL-10
channel d1: restoring controlfile
channel d1: restore complete
replicating controlfile
input filename=/data/TESTDB/cntrl01.dbf
output filename=/data/TESTDB/cntrl02.dbf
output filename=/data/TESTDB/cntrl03.dbf
Finished restore at 14-JUL-10
released channel: d1
exit
sqlplus '/ as sysdba'
shutdown immediate;
startup mount;
RMAN> run
2> {
3> allocate channel d1 type disk;
4> restore database;
5> }
using target database controlfile instead of recovery catalog
allocated channel: d1
channel d1: sid=12 devtype=DISK
Starting restore at 15-JUL-10
released channel: d1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/15/2010 00:03:18
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
We are using 9.2.0.6 on LINUX
The list backup commands too return EMPTY
RMAN> list backup;
RMAN> list backup of database;
---Any ideas ?
Srinivas

I am also uploading the logfile of the backup job of the source database
RMAN> run
2> {
3> allocate channel d1 type disk;
4> backup database format '/data/TESTDB/rman/testdb_bk_%s_%p_%t' include current controlfile;
5> backup archivelog all format '/data/TESTDB/rman/testdb_al_%s_%p_%t' delete input;
6> release channel d1;
7> }
allocated channel: d1
channel d1: sid=17 devtype=DISK
Starting backup at 14-JUL-10
channel d1: starting full datafile backupset
channel d1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00001 name=/data/TESTDB/system01.dbf
input datafile fno=00002 name=/data/TESTDB/undotbs01.dbf
channel d1: starting piece 1 at 14-JUL-10
channel d1: finished piece 1 at 14-JUL-10
piece handle=/data/TESTDB/rman/testdb_bk_2_1_724368405 comment=NONE
channel d1: backup set complete, elapsed time: 00:00:01
Finished backup at 14-JUL-10
Starting backup at 14-JUL-10
current log archived
channel d1: starting archive log backupset
channel d1: specifying archive log(s) in backup set
input archive log thread=1 sequence=3 recid=1 stamp=724368322
input archive log thread=1 sequence=4 recid=2 stamp=724368406
channel d1: starting piece 1 at 14-JUL-10
channel d1: finished piece 1 at 14-JUL-10
piece handle=/data/TESTDB/rman/testdb_al_3_1_724368406 comment=NONE
channel d1: backup set complete, elapsed time: 00:00:02
channel d1: deleting archive log(s)
archive log filename=/data/TESTDB/arch/archTESTDB_3.arc recid=1 stamp=724368322
archive log filename=/data/TESTDB/arch/archTESTDB_4.arc recid=2 stamp=724368406
Finished backup at 14-JUL-10
released channel: d1
RMAN> exit

Similar Messages

  • RMAN backup and restore for Disaster Recovery

    Hi Guys,
    I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
    Starting restore at 21-SEP-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
    ystem01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
    ysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
    ndotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
    sers01.dbf
    channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
    a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
    channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
    upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
    Finished restore at 21-SEP-11
    Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
    a/FORUMS/backupset/
    whereas my latest backups are stored at a different location.
    I am executing following steps at the RMAN prompt on hosta and hostb:
    hosta (production site)
    backup as compressed backupset database plus archivelog
    backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
    backup spfile
    hostb (Disaster site)
    set dbid=13732232063
    startup force nomount
    restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
    shutdown immediate
    /* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
    startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
    restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
    /* restart rman here */
    quit
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
    /* call the next two commands on run */
    restore database;
    recover database;
    alter database open resetlogs
    quit
    Any help will be greatly appreciated.
    Thanks,
    Rajesh

    Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
    I take backup on Host A using:
    rman target /
    backup as compressed backupset database plus archivelog;
    backup spfile;
    quit;
    I restore the backup on Host B using:
    set dbid=13732232063;
    startup force nomount;
    restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
    shutdown immediate;
    startup force nomount;
    restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
    quit;
    /* restart rman here */
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset' noprompt;
    restore database;
    recover database;
    alter database open resetlogs;
    quit;
    I take another backup on Host A using (notice no spfile backup this time):
    backup as compressed backupset database plus archivelog;
    quit;
    I restore the database on Host B using:
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
    recover database;
    alter database open;
    quit;
    Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
    RMAN> list backup of database;
    using target database control file instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    89 Full 261.87M DISK 00:01:37 28-SEP-11
    BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
    Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
    8T171638_787g77rx_.bkp
    List of Datafiles in backup set 89
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    97 Full 259.16M DISK 00:00:00 28-SEP-11
    BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
    7
    Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
    TAG20110928T183527787lv0nb_.bkp
    List of Datafiles in backup set 97
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
    Output of list backup (done after restoring the control file)
    RMAN> list backup;
    BS Key Size Device Type Elapsed Time Completion Time
    87 89.20M DISK 00:00:26 28-SEP-11
    BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
    List of Archived Logs in backup set 87
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 34 1302253 20-SEP-11 1306439 20-SEP-11
    1 35 1306439 20-SEP-11 1307647 20-SEP-11
    1 36 1307647 20-SEP-11 1307701 20-SEP-11
    1 37 1307701 20-SEP-11 1311393 20-SEP-11
    1 38 1311393 20-SEP-11 1311511 20-SEP-11
    1 39 1311511 20-SEP-11 1332479 20-SEP-11
    1 40 1332479 20-SEP-11 1344418 20-SEP-11
    1 41 1344418 20-SEP-11 1350409 20-SEP-11
    1 42 1350409 20-SEP-11 1350449 20-SEP-11
    1 43 1350449 20-SEP-11 1350854 21-SEP-11
    1 44 1350854 21-SEP-11 1350895 21-SEP-11
    1 45 1350895 21-SEP-11 1353114 21-SEP-11
    1 46 1353114 21-SEP-11 1353254 21-SEP-11
    1 47 1353254 21-SEP-11 1353865 21-SEP-11
    1 48 1353865 21-SEP-11 1353988 21-SEP-11
    1 49 1353988 21-SEP-11 1375403 21-SEP-11
    1 50 1375403 21-SEP-11 1376149 21-SEP-11
    1 51 1376149 21-SEP-11 1376206 21-SEP-11
    1 52 1376206 21-SEP-11 1376246 21-SEP-11
    1 53 1376246 21-SEP-11 1379990 21-SEP-11
    1 54 1379990 21-SEP-11 1380229 21-SEP-11
    1 55 1380229 21-SEP-11 1380266 21-SEP-11
    1 56 1380266 21-SEP-11 1380528 21-SEP-11
    1 57 1380528 21-SEP-11 1380724 21-SEP-11
    1 58 1380724 21-SEP-11 1380861 21-SEP-11
    1 59 1380861 21-SEP-11 1381033 21-SEP-11
    1 60 1381033 21-SEP-11 1381077 21-SEP-11
    1 61 1381077 21-SEP-11 1402243 22-SEP-11
    1 62 1402243 22-SEP-11 1423341 22-SEP-11
    1 63 1423341 22-SEP-11 1435456 22-SEP-11
    1 64 1435456 22-SEP-11 1454415 23-SEP-11
    1 65 1454415 23-SEP-11 1490903 23-SEP-11
    1 66 1490903 23-SEP-11 1491266 23-SEP-11
    1 67 1491266 23-SEP-11 1491347 23-SEP-11
    1 68 1491347 23-SEP-11 1492761 23-SEP-11
    1 69 1492761 23-SEP-11 1492891 23-SEP-11
    1 70 1492891 23-SEP-11 1493678 23-SEP-11
    1 71 1493678 23-SEP-11 1493704 23-SEP-11
    1 72 1493704 23-SEP-11 1494741 23-SEP-11
    1 73 1494741 23-SEP-11 1494790 23-SEP-11
    1 74 1494790 23-SEP-11 1510154 23-SEP-11
    1 75 1510154 23-SEP-11 1514286 23-SEP-11
    1 76 1514286 23-SEP-11 1531967 24-SEP-11
    1 77 1531967 24-SEP-11 1543266 24-SEP-11
    1 78 1543266 24-SEP-11 1558427 24-SEP-11
    1 79 1558427 24-SEP-11 1566924 24-SEP-11
    1 80 1566924 24-SEP-11 1578292 24-SEP-11
    1 81 1578292 24-SEP-11 1596894 25-SEP-11
    BS Key Size Device Type Elapsed Time Completion Time
    88 84.03M DISK 00:00:30 28-SEP-11
    BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
    List of Archived Logs in backup set 88
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 82 1596894 25-SEP-11 1609028 25-SEP-11
    1 83 1609028 25-SEP-11 1622303 25-SEP-11
    1 84 1622303 25-SEP-11 1626430 25-SEP-11
    1 85 1626430 25-SEP-11 1634486 25-SEP-11
    1 86 1634486 25-SEP-11 1648398 25-SEP-11
    1 87 1648398 25-SEP-11 1669259 26-SEP-11
    1 88 1669259 26-SEP-11 1686820 26-SEP-11
    1 89 1686820 26-SEP-11 1686959 26-SEP-11
    1 90 1686959 26-SEP-11 1689168 26-SEP-11
    1 91 1689168 26-SEP-11 1704759 26-SEP-11
    1 92 1704759 26-SEP-11 1719597 27-SEP-11
    1 93 1719597 27-SEP-11 1740407 27-SEP-11
    1 94 1740407 27-SEP-11 1750125 27-SEP-11
    1 95 1750125 27-SEP-11 1765592 27-SEP-11
    1 96 1765592 27-SEP-11 1781498 28-SEP-11
    1 97 1781498 28-SEP-11 1802311 28-SEP-11
    1 98 1802311 28-SEP-11 1811009 28-SEP-11
    1 99 1811009 28-SEP-11 1813811 28-SEP-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    89 Full 261.87M DISK 00:01:37 28-SEP-11
    BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
    List of Datafiles in backup set 89
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

  • Not able to create disaster recovery VMM -- ovm pool / repository ownership issue

    I have installed VMM and VMS and create a server pool with 3.0.2 version.
    To test disaster recovery, I rebuild the VMM with the old UUID by
    runInstaller.sh --uuid 0004fb00000100002ae.....
    and restore the repository database.
    The new VMM (same IP as old one) can recognize the VMS but can not complete the clone process. Couple hours later, all VMSs reboot and the event showed: server cluster is down. After that, I can clone the VM from template as before. But I when I use "Edit the server pool" to assign Master Server, it show:
    OVMRU_000039E Cannot perform operations. Server pool: VMSP1, is owned by another manager.
    How to query the owner of Server pool and how to fix?
    Thanks,
    Shun-Jee Liu

    More information:
    .ovspoolfs:
    OVS_POOLFS_UUID=0004fb00000500002db902059c9fb1d6
    OVS_POOLFS_NFSBASE_UUID=
    OVS_POOLFS_MGR_UUID=0004fb00000100002ae......
    OVS_POOLFS_VERSION=3.0
    OVS_POOLFS_POOL_UUID=0004fb00000200006908301358c88ab9
    OVS_POOLFS_LUN_UUID=3600144f03837090000004ebe8dab0001
    OVS_POOLFS_MGR_UUID matches the UUID in OVM Manager. Have no idea about OVS_POOLFS_UUID.
    Shun-Jee Liu

  • Need recommentation to setup Disaster recovery site

    Hi All,
    1.What are the basic things we need to analyze before we recommend the business to go for oracle Dataguard for DR setup?
    2. Do you know any technology that will replicate the schema from one datacenter[one primary database ] to another datacenter [secondary or replication database]?
    3. What are the various option to configure the disaster recovery plan at schema level?
    Thanks

    Hello;
    1.What are the basic things we need to analyze before we recommend the business to go for oracle Dataguard for DR setup?Network - bandwidth requirements. How much Redo do you generate? How far away is the standby site? ( proposed network bandwidth and latency )
    Power - UPS requirements ( how will you monitor the standby site )
    RMAN requirements - Where would you backup? At the primary site or the standby site? If Standby what is the cost of extra equipment? How far away should the standby site be?
    Business needs for data ( 24/7, 6 to 6 Monday - Friday etc ) This would help determine a possible protection mode and what switchover failover options you might need.
    Allowed downtime if any ( patches, upgrades etc)
    How much data loss can be tolerated if you have network, hardware issues? For Primary site? If standby site is lost?
    The idea is to develop a plan that meets your business needs.
    2. Do you know any technology that will replicate the schema from one datacenter[one primary database ] to another datacenter [secondary or replication database]?Data Guard Logical Standby since you pick what you want to apply
    Data Pump will also work
    3. What are the various option to configure the disaster recovery plan at schema level?Going to depend upon how much protect the business requires. If all you want is a copy then Data Pump might work.
    If you require zero data loss then Data Guard is the way to go.
    Frankly I would not use a Logical Standby, I would use a physical standby so I could switchover.
    A Logical Standby is a nice idea, but a physical gives you an exact copy and I believe is much easier to maintain.
    Best Regards
    mseberg

  • Is anyone doing disaster recovery for a J2EE application?

    We generally use database log shipping to maintain a standby database for our ABAP instances.  We can successfully fail over our production application to our disaster recovery site with no real issues.  With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
    hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
    fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
    we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
    Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them?  Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
    Regards,
    David Hull
    The Walt Disney Company

    I haven't done this personally, but I do have some experience with these issues in different HA environments.
    To your first point:  You can change the hostname, note 757692 tells you exactly how to do it.  However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP."  When it says "supported by SAP" I think it means SAP the company, not SAP's software.  So I would contact SAP to see if this configuration would be covered under your service agreement.  Then you have to think about whether you want to do something that isn't "officially supported" by SAP.  Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
    To your second point:  As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same.  I don't think they are hostname or fqdn dependant.  For BSPs I would think they would still work as long as they use relative paths rather than absolute paths.  And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
    Again, I haven't done what you're describing myself.  This is just based on my HA experiences.
    Hope this helps a little,
    Glenn

  • SharePoint 2010 backup and restore to test SharePoint environment - testing Disaster recovery

    We have a production SharePoint 2010 environment with one Web/App server and one SQL server.   
    We have a test SharePoint 2010 environment with one server (Sharepoint server and SQL server) and one AD (domain is different from prod environment).  
    Servers are Windows 2008 R2 and SQL 2008 R2.
    Versions are the same on prod and test servers.  
    We need to setup a test environment with the exact setup as production - we want to try Disaster recovery. 
    We have performed backup of farm from PROD and we wanted to restore it on our new server in test environment.Backup completed successfully with no errors.
    We have tried to restore the whole farm from that backup on test environment using Central administration, but we got message - restore failed with errors.
    We choosed NEW CONFIGURATION option during restore, and we set new database names... 
    Some of the errors are:
    FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: The specified user or domain group was not found.
    Warning: Cannot restore object User Profile Service Application because it failed on backup.
    FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    Verbose: Starting object: WSS_Content_IT_Portal.
    Warning: [WSS_Content_IT_Portal] A content database with the same ID already exists on the farm. The site collections may not be accessible.
    FatalError: Object WSS_Content_IT_Portal failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: The specified component exists. You must specify a name that does not exist.
    Warning: [WSS_Content_Portal] The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
    RESTORE DATABASE is terminating abnormally.
    FatalError: Object Portal - 80 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    ArgumentException: The IIS Web Site you have selected is in use by SharePoint.  You must select another port or hostname.
    FatalError: Object Access Services failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: Object parent could not be found.  The restore operation cannot continue.
    FatalError: Object Secure Store Service failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: The specified component exists. You must specify a name that does not exist.
    FatalError: Object PerformancePoint Service Application failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: Object parent could not be found.  The restore operation cannot continue.
    FatalError: Object Search_Service_Application_DB_88e1980b96084de984de48fad8fa12c5 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    Aborted due to error in another component.
    Could you please help us to resolve these issues?  

    I'd totally agree with this. Full fledged functionality isn't the aim of DR, getting the functional parts of your platform back-up before too much time and money is lost.
    Anything I can add would be a repeat of what Jesper has wisely said but I would very much encourage you to look at these two resources: -
    DR & back-up book by John Ferringer for SharePoint 2010
    John's back-up PowerShell Script in the TechNet Gallery
    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles:
    CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

  • SharePoint 2013 Search - Disaster Recovery Restore

    Hello,
    We are setting up a new SharePoint 2013 with a separate Disaster Recovery farm as a hot-standby.  In a DR scenario, we want to restore all content and service app databases to the new farm, then fix any configuration issues that might arise due to changes
    in server names, etc...
    The issue we're running into is the search service components are still pointing to the production servers even though they're in the new farm with completely different server names.  This is expected, so we're preparing a PowerShell script to remove
    then re-create the search components as needed.  The problem is that all the commands used to apply the new search topology won't function because they can't access the administration component (very frustrating).  It appears we're in a chicken &
    egg scenario - we can't change the search topology because we don't have a working admin component, but we can't fix the admin component because we can't change the search topology.
    The scripts below are just some of the things we've tried to fix the issue:
    $sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
    $local = Get-SPEnterpriseSearchServiceInstance -Local;
    $topology = New-SPEnterpriseSearchTopology -SearchApplication $sa;
    New-SPEnterpriseSearchAdminComponent -SearchTopology $topology -SearchServiceInstance $local;
    New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
    New-SPEnterpriseSearchCrawlComponent -SearchTopology $topology -SearchServiceInstance $local;
    New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
    New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
    New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $local -IndexPartition 0 -RootDirectory "D:\SP_Index\Index";
    $topology.Activate();
    We get this message:
    Exception calling "Activate" with "0" argument(s): "The search service is not able to connect to the machine that 
    hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a' 
    in search application 'Search Service Application' is in a good state and try again."
    At line:11 char:1
    + $topology.Activate();
    + ~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : InvalidOperationException
    Also, same as above with
    $topology.BeginActivate()
    We get no errors but the new topology is never activated.  Attempting to call $topology.Activate() within the next few minutes will result in an error saying that "No modifications to the search topology can be made because previous changes are
    being rolled back due to an error during a previous activation".
    Next I found a few methods in the object model that looked like they might do some good:
    $sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
    $topology = Get-SPEnterpriseSearchTopology -SearchApplication $sa -Active;
    $admin = $topology.GetComponents() | ? { $_.Name -like "admin*" }
    $topology.RecoverAdminComponent($admin,"server1");
    This one really looked like it worked.  It took a few seconds to run and came back with no errors.  I can even get the active list of components and it shows that the Admin component is running on the right server:
    Name ServerName
    AdminComponent1 server1
    ContentProcessingComponent1
    QueryProcessingComponent1
    IndexComponent1
    QueryProcessingComponent3
    CrawlComponent0
    QueryProcessingComponent2
    IndexComponent2
    AnalyticsProcessingComponent1
    IndexComponent3
    However, I'm still unable to make further changes to the topology (getting the same error as above when calling $topology.Activate()), and the service application in central administration shows an error saying it can't connect to the admin component:
    The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.
    Lastly, I tried to move the admin component directly:
    $sa.AdminComponent.Move($instance, "d:\sp_index")
    But again I get an error:
    Exception calling "Move" with "2" argument(s): "Admin component was moved to another server."
    At line:1 char:1
    + $sa.AdminComponent.Move($instance, "d:\sp_index")
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : OperationCanceledException
    I've checked all the most common issues - the service instance is online, the search host controller service is running on the machine, etc...  but I can't seem to get this database restored to a different farm.
    Any help would be appreciated!

    Thanks for the response Bhavik,
    I did ensure the instance was started:
    Get-SPEnterpriseSearchServiceInstance -Local
    TypeName : SharePoint Server Search
    Description : Index content and serve search queries
    Id : e9fd15e5-839a-40bf-9607-6e1779e4d22c
    Server : SPServer Name=ROYALS
    Service : SearchService Name=OSearch15
    Role : None
    Status : Online
    But after attempting to set the admin component I got the results below.
    Before setting the admin component:
    Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
    IndexLocation : E:\sp_index\Office Server\Applications
    Initialized : True
    ServerName : prodServer1
    Standalone :
    After setting the admin component:
    Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
    IndexLocation :
    Initialized : False
    ServerName :
    Standalone :
    It's shown this status for a few hours now so I don't believe it's still provisioning.  Also, the search service administration is still showing the same error:
    The search service is not able to connect to the machine that hosts the administration component. Verify that the administration
    component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.

  • Recovering lost data from a very old backup (disaster recovery)

    Hi all,
    I am trying to restore and recover data from an old DAT-72 cassette. All I know is the date when the backup was taken, that is back in November 2006. I do not know the DBID or anything else except for the date.
    To recover this, I bought an internal SCSI HP c7438a DAT-72 tape drive on eBay and installed it on a machine running Windows 2003 Server SP2. I made a fresh Oracle 11g Enterprise Edition installation. HP tape drivers have been installed and Windows sees the tape drive without problem. To act as a Media Manager, I have installed Oracle Secure Backup. Oracle Secure Backup sees the HP tape drive without problems as well.
    I have to admit my information about Oracle is not very in-depth. I read quite a lot of documents, but the more I read the more confused I become. The closest thing I can find to my situation is the following guide about disaster recovery:
    http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmrecov.htm#1007948
    I tried the suggestions in this document without success (details below).
    My questions are:
    1. Is it possible to retrieve data without knowing the DBID?
    2. If not, is it possible to figure out the DBID from the tape? I tried to use dd in cygwin, also booted with Knoppix/Debian and Ubuntu CDs to dump the contents of the tape with dd but all of them failed to see the tape device. If there is any way to dump the raw contents of the tape on Windows, I would also welcome input.
    3. Is there any way at all to recover this data from the tape given all the unknowns?
    Thanks very much in advance,
    C:\Program Files>rman target orcl
    Recovery Manager: Release 11.2.0.1.0 - Production on Sat Mar 19 15:01:28 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    target database Password:
    connected to target database: ORCL (not mounted)
    RMAN> SET DBID 676549873;
    executing command: SET DBID
    RMAN> STARTUP FORCE NOMOUNT; # rman starts instance with dummy parameter file
    Oracle instance started
    Total System Global Area 778387456 bytes
    Fixed Size 1374808 bytes
    Variable Size 268436904 bytes
    Database Buffers 503316480 bytes
    Redo Buffers 5259264 bytes
    RMAN> RUN
    2> {
    3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt;
    4> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
    DATE-1575';
    5> }
    using target database control file instead of recovery catalog
    allocated channel: t1
    channel t1: SID=63 device type=SBT_TAPE
    channel t1: Oracle Secure Backup
    Starting restore at 19-MAR-11
    channel t1: looking for AUTOBACKUP on day: 20061125
    channel t1: looking for AUTOBACKUP on day: 20061124
    channel t1: looking for AUTOBACKUP on day: 20061123
    channel t1: looking for AUTOBACKUP on day: 20061122
    channel t1: looking for AUTOBACKUP on day: 20061121
    channel t1: looking for AUTOBACKUP on day: 20061120
    channel t1: looking for AUTOBACKUP on day: 20061119
    channel t1: no AUTOBACKUP in 7 days found
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 03/19/2011 15:03:26
    RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
    RMAN>
    RMAN> RUN
    2> {
    3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt
    4> PARMS 'SBT_LIBRARY=C:\WINDOWS\SYSTEM32\ORASBT.DLL';
    5> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
    DATE-1575';
    6> }
    allocated channel: t1
    channel t1: SID=63 device type=SBT_TAPE
    channel t1: Oracle Secure Backup
    Starting restore at 19-MAR-11
    channel t1: looking for AUTOBACKUP on day: 20061125
    channel t1: looking for AUTOBACKUP on day: 20061124
    channel t1: looking for AUTOBACKUP on day: 20061123
    channel t1: looking for AUTOBACKUP on day: 20061122
    channel t1: looking for AUTOBACKUP on day: 20061121
    channel t1: looking for AUTOBACKUP on day: 20061120
    channel t1: looking for AUTOBACKUP on day: 20061119
    channel t1: no AUTOBACKUP in 7 days found
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 03/19/2011 15:04:56
    RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
    RMAN>
    -----------------------------------

    Hi 845725,
    If the backups were created with OSB might be you can query the tape with obtool.
    http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htmTo list pieces you could use <lspiece> within obtool.
    http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htm#BHBBIFFEIf this works you should be able to identify the controlfile autobackup if it has the standard naming < c-dbid-date-xx > and you than know the DBID or you are able to restore a controlfile from a backup piece in the output list.
    Might be you have to install 9i or 10g rdbms software as 11g was released a year later in 2007.
    Anyway goodluck.
    Regards,
    Tycho

  • Welcome to the SQL Server Disaster Recovery and Availability Forum

    (Edited 8/14/2009 to correct links - Paul)
    Hello everyone and welcome to the SQL Server Disaster Recovery and Availability forum. The goal of this Forum is to offer a gathering place for SQL Server users to discuss:
    Using backup and restore
    Using DBCC, including interpreting output from CHECKDB and related commands
    Diagnosing and recovering from hardware issues
    Planning/executing a disaster recovery and/or high-availability strategy, including choosing technologies to use
    The forum will have Microsoft experts in all these areas and so we should be able to answer any question. Hopefully everyone on the forum will contribute not only questions, but opinions and answers as well. I’m looking forward to seeing this becoming a vibrant forum.
    This post has information to help you understand what questions to post here, and where to post questions about other technologies as well as some tips to help you find answers to your questions more quickly and how to ask a good question. See you in the group!
    Paul Randal
    Lead Program Manager, SQL Storage Engine and SQL Express
    Be a good citizen of the Forum
    When an answer resolves your problem, please mark the thread as Answered. This makes it easier for others to find the solution to this problem when they search for it later. If you find a post particularly helpful, click the link indicating that it was helpful
    What to post in this forum
    It seems obvious, but this forum is for discussion and questions around disaster recovery and availability using SQL Server. When you want to discuss something that is specific to those areas, this is the place to be. There are several other forums related to specific technologies you may be interested in, so if your question falls into one of these areas where there is a better batch of experts to answer your question, we’ll just move your post to that Forum so those experts can answer. Any alerts you set up will move with the post, so you’ll still get notification. Here are a few of the other forums that you might find interesting:
    SQL Server Setup & Upgrade – This is where to ask all your setup and upgrade related questions. (http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads)
    Database Mirroring – This is the best place to ask Database Mirroring how-to questions. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabasemirroring/threads)
    SQL Server Replication – If you’ve already decided to use Replication, check out this forum. (http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/threads)
    SQL Server Database Engine – Great forum for general information about engine issues such as performance, FTS, etc. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/threads)
    How to find your answer faster
    There is a wealth of information already available to help you answer your questions. Finding an answer via a few quick searches is much quicker than posting a question and waiting for an answer. Here are some great places to start your research:
    SQL Server 2005 Books Onlinne
    Search it online at http://msdn2.microsoft.com
    Download the full version of the BOL from here
    Microsoft Support Knowledge Base:
    Search it online at http://support.microsoft.com
    Search the SQL Storage Engine PM Team Blog:
    The blog is located at https://blogs.msdn.com/sqlserverstorageengine/default.aspx
    Search other SQL Forums and Web Sites:
    MSN Search: http://www.bing.com/
    Or use your favorite search engine
    How to ask a good question
    Make sure to give all the pertinent information that people will need to answer your question. Questions like “I got an IO error, any ideas?” or “What’s the best technology for me to use?” will likely go unanswered, or at best just result in a request for more information. Here are some ideas of what to include:
    For the “I got an IO error, any ideas?” scenario:
    The exact error message. (The SQL Errorlog and Windows Event Logs can be a rich source of information. See the section on error logs below.)
    What were you doing when you got the error message?
    When did this start happening?
    Any troubleshooting you’ve already done. (e.g. “I’ve already checked all the firmware and it’s up-to-date” or "I've run SQLIOStress and everything looks OK" or "I ran DBCC CHECKDB and the output is <blah>")
    Any unusual occurrences before the error occurred (e.g. someone tripped the power switch, a disk in a RAID5 array died)
    If relevant, the output from ‘DBCC CHECKDB (yourdbname) WITH ALL_ERRORMSGS, NO_INFOMSGS’
    The SQL Server version and service pack level
    For the “What’s the best technology for me to use?” scenario:
    What exactly are you trying to do? Enable local hardware redundancy? Geo-clustering? Instance-level failover? Minimize downtime during recovery from IO errors with a single-system?
    What are the SLAs (Service Level Agreements) you must meet? (e.g. an uptime percentage requirement, a minimum data-loss in the event of a disaster requirement, a maximum downtime in the event of a disaster requirement)
    What hardware restrictions do you have? (e.g. “I’m limited to a single system” or “I have several worldwide mirror sites but the size of the pipe between them is limited to X Mbps”)
    What kind of workload does you application have? (or is it a mixture of applications consolidated on a single server, each with different SLAs) How much transaction log volume is generated?
    What kind of regular maintenance does your workload demand that you perform (e.g. “the update pattern of my main table is such that fragmentation increases in the clustered index, slowing down the most common queries so there’s a need to perform some fragmentation removal regularly”)
    Finding the Logs
    You will often find more information about an error by looking in the Error and Event logs. There are two sets of logs that are interesting:
    SQL Error Log: default location: C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\LOG (Note: The # changes depending on the ID number for the installed Instance. This is 1 for the first installation of SQL Server, but if you have mulitple instances, you will need to determine the ID number you’re working with. See the BOL for more information about Instance ID numbers.)
    Windows Event Log: Go to the Event Viewer in the Administrative Tools section of the Start Menu. The System event log will show details of IO subsystem problems. The Application event log will show details of SQL Server problems.

    hi,I have a question on sql database high availability. I have tried using database mirroring, where I am using sql standard edition, in this database mirroring of synchronous mode is the only option available, and it is giving problem, like sql time out errors on my applicatons since i had put in the database mirroring, as asynchronous is only available on enterprise version, is there any suggestions on this. thanks ---vijay

  • What is the quickest to upgrade disaster recovery system to NW04s in MSCS?

    Hi,
    I have an issue which I need assistance from SAP/Windows 2003 experts.
    Hope you can share your opinion on  an SAP upgrade issue we're grappling with. 
    <u><b>Objective :</b></u> Upgrade our SAP Bank Analyzer disaster recovery environment from NW04 to NW04s SR2, to be same as  production.  Both production and disaster recovery (DR) run under two node WIN2003 Enterprise MSCS.  The SAP CI usually runs on node A and Oracle 10g runs on node B.
    The Oracle software, parameters,  database files and  the SAP folder \usr\sap are  already matching. These files and folders are  on EMC mirrored disks, so this will  be automatically synchronized from production status.
    Therefore  I believe it is only the SAP software components on the local hard disks - binaries, DLLs, registry, DCOM, environment variable etc, that need to be upgraded on the two DR machines.
    For your information,  the current SAP 6.40 instance,  Oracle 10g instance, MSCS failover capability are all working in the DR environment as we just did an exercise a month ago to prove this.
    <u><b> Disaster Recovery Environment :</b></u>
    On shared drives that are synchronized between prod and DR  : SAP folder \usr\sap including the kernel binaries, Oracle parameter files, database datafiles, redologs, sapbackup etc.  
    <u><b>Issue :</b></u> What is the <b>quickest</b>  and <b>reliable</b> method to achieve the objective? Other than the SAP kernel binaries and profiles, I'm not certain what other related components are updated/replaced that are stored locally on each of the clustered machine.  
    There are three different approaches we can think of :
    1) Repeat the whole NW04s upgrade process in the DR environment. This takes several days. The exposure of not having a disaster recovery environment for several days is a minus.
                 <u><u><b>  or</b></u></u>
    2) Un-install the SAP CI and MSCS definitions. Synchronise the DR shared disks from production to have the upgraded production NW04s database contents and SAP folder \usr\sap.
    Use SAPINST to re-install either traditional CI or ASCS option 'System Copy". And then re-create the MSCS definitions for SAP CI using SAPINST again.
    The disadvantage is I can't trial this in any other of our environments. Also, we want to run with the traditional CI instead of ASCS until early next year for other reasons. So we would have to reverse the ASCS back to traditional CI with this method, by reversing the steps in OSS NOTE 101190 "Splitting CI after upgrade to 700".
                    <u><u><b>or</b></u></u>
    3) Somehow identify all the SAP components that are stored locally on each machine (eg. environment variables, registry settings, DCOM definitions, DLL in various folders). Then just copy  them from Production to DR machines or recreate them. I'm <u><b>not</b></u> confident of identifying the local SAP components. And I have not been able to find any good OSS NOTEs or forum threads on this topic. The most helpful OSS NOTE I can find is 112266  point 13 and 19.
    Thanks for any input.
    Benny Kwan

    See:
    * https://support.mozilla.com/kb/Form+autocomplete
    * Firefox > Preferences > Privacy > History: "Remember search and form history"
    * Autofill Forms: https://addons.mozilla.org/firefox/addon/autofill-forms/

  • Datafiles Mismatch in production & disaster recovery server

    Datafiles Mismatch in production & disaster recovery server though everything in sync
    We performed all the necessary prerequisites & processes related to DRS switchover successfully also our DRS server is constantly updated through logs application in mount state whan we opened DRS database in mount state it opened successfully however when we issued command
    Recover database
    It dumped with foll errors:
    ora-01122 database file 162 failed verification check
    ora-01110 data file 162 </oracle/R3P/sapdata7/r3p*****.data>
    ora-01251 unknown file header version read for file 162
    as I do not remember the exact name now
    However upon comparing the same file at production(which was now in shutdown state) the file sizes were mismatching so we went ahead to copy the datafile from production to DRS in database shutdown state at DRS through RCP utitlity of AIX 5.3 since our Operating system is AIX 5.3
    Though this remote copy was success
    we again started database in mount state & issued command
    Recover database
    But still it dump the same error but now for another datafile in DRS
    I mean I would appreciate if somebody could point out that despite our DRS was constantly being updated through our Production in terms of continuous log application before this activity logs were sync in both the systems also origlos,mirrorlogs & controlfiles were pulled from production system as it is infact the whole structure was as replica of production system , then why did datafile sizes mismatch??
    Details
    SAP version :- 4.7
    WAS :- 620
    Database :- Oracle 9.2
    Operating system :- AIX 5.3

    I am in a process of DR Planning.
    My present setup :
    O/S : HP-UX 11.31
    SAP ECC 6
    Oracle 10g Database.
    I know about dataguard and i have implemnted same on our other application but not for SAP.
    I have ame doubts and I request you to please guide me for the same.
    1. SAP License key -- it required hardware key. So will i have to generate license key another hardware key i.e. for machine where standby database.
    2. Database on standby site will be in manage recovery mode. Will I have to make any changes or any other file realted to SAP on standby host ? (some i know such as I upgrade SAP kernal, same i have to upgrade at standby host)
    Will you give me some link related to document for DR

  • Oracle EE 11.2.0.2 RMAN Duplicate interesting issue - is it a bug?

    Hi,
    Oracle EE 11.2.0.2 RHEL 5.7 x86 64-bit RACOne Node database (3 - nodes).
    I was working on a process to refresh out test environment with prod database backup from tape and i have done it many times. Most of our environment is in 10gR2 and have few on 11.2.0.2 RACOne Node databases. The recovery basics in Oracle world is to use archive log sequence + 1 (provided we know before hand the backups metadata) and it works as expected until 10g but with 11.2.0.2 RMAN duplicate, i stumbled upon an issue where RMAN is trying to restore an older controlfile auto backup and then rolling forward from there. Its easy to explain with an example..
    1) I have an archivelog backup, say sequence 20 to 30 on Feb 22nd @ 10pm and a controlfile autobackup at this time c-20120222
    2) I have a FULL backup + archive log until sequence 50 on Feb 23nd@ 6pm and a controlfile autobackup at this time  c-20120223
    3) I am using RMAN duplicate to refresh UAT with Feb 23rd backup and use "set until sequence 51 thread 1"I am using following RMAN commands to do the duplicate on UAT server (executed on UAT server)
    rman target sys/***@PROD_DB  auxiliary /
    RMAN> run
    2> {
    3> allocate auxiliary channel c1 device type disk;
    4> allocate auxiliary channel c2 device type disk;
    5> allocate auxiliary channel c3 device type disk;
    6> set until sequence 51 thread 1;
    7> duplicate target database to UAT_DB;
    8> }RMAN duplicate automates all that we do manually but the recovery mechanism is same. In the above scenario, it connects to target database, gets the backup metadata and restores controlfile from c-20120223 , restores the datafiles and recovers till sequence 50 . This has been the scenario until 10g in every RMAN duplicate process i have tried and is expected from Oracle.
    Issue:
    In 11gR2 (11.2.0.2), for the same duplicate scenario above, it is restoring the controlfile from autobackup c-20120222 and restoring the datafiles from Feb 23rd backup, recovering till sequence 50 and doing the duplicate process. The thing to note here is that the controlfile autobackup c-20120222 does not have any record of the FULL backup that occured on Feb 23 rd and since RMAN duplicate is having a connection to target database, it knows the backup metadata and hence it is able to complete the recovery.
    For clarification, Thread 1 & 2 of RAC One Node is not an issue here for sure. Did anyone experience this issue? Any insight into this would be greatly appreciated.
    Thanks,
    Shiva

    AJ,
    I have already tried that scenario, i renamed the c-20120222 and kicked off the same duplicate process but it failed and it kept on "fail-over to previous backup" which is expected. The thing is, RMAN look's for the control file autobackups from newest to oldest (unless you gave a point in time) and duplicate command is not doing it.
    Tycho,
    I agree there are new features but to support them a change in recovery mechanism is something i would disagree that Oracle would do. Active Duplication is not based on backups, so that is out of question here. For backup-based duplication, we can try with connections to target or targetless, catalog or catalogless or none. I have already given an example with the target (same with target + catalog) and i expect the same behavior with only catalog connection. Now, i have tested the example without connecting to target or catalog and below are my observations...
    For the same backups i mentioned in the very first email, i got the following info....
    rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Fri Feb 24 12:35:54 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: RMANTEST (DBID=3789692530)
    RMAN> list backup of archivelog sequence 95;
    using target database control file instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    11      2.50K      DISK        00:00:00     23-FEB-12 18:05:40
            BP Key: 11   Status: AVAILABLE  Compressed: YES  Tag: TAG20120222T094240
            Piece Name: /u01/app/oracle/exp/rmantest_stl/full_backup/rmantest_stl_0bn3upkg_1_1.arch
      List of Archived Logs in backup set 11
      Thrd Seq     Low SCN    Low Time           Next SCN   Next Time
      1    95      346280     23-FEB-12 18:05:10 346302     23-FEB-12 18:05:30I got the scn_to_timestamp for the NEXT_SCN of sequence 95, which should correpond tothe "Next Time" that is the timestamp for the Archive log sequence 96.
    SQL> select scn_to_timestamp(346302) as timestamp from dual;
    TIMESTAMP
    23-FEB-12 18.05.30.000000000 PMNow, i gave the following for targetless & catalogless duplication...
    rman auxiliary /
    RMAN> run
    2> {
    3> set until time "to_date('23-FEB-12 18:05:30','DD-MON-YY HH24:MI:SS')";
    4> duplicate database to rman01s backup location '/u01/app/oracle/exp/rmantest_stl';
    5> }RESULT: Same ISSUE but this time IT FAILED with the error i expected. It went ahead and restored the c-20120222 autobackup control file and tried to restore the datafiles but, as we
    know, this control file autobackup does not have record of Feb 23rd + archive log backup, so it FAILS. This is exactly what i told in my first email.
    Error Log File:
    contents of Memory Script:
       sql clone "alter system set  control_files =
      ''+RMAN01D_DATA/rman01s_stl1/controlfile/current.270.776081841'', ''+RMAN01D_RECO/rman01s_stl1/controlfile/current.263.776081841'' comment=
    ''Set by RMAN'' scope=spfile";
       sql clone "alter system set  db_name =
    ''RMANTEST'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile from  '/u01/app/oracle/exp/rmantest_stl/c-20120222';
       alter clone database mount;
    Errors in memory script
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01507: database not mounted
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 13371
    ORA-06512: at line 1
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/24/2012 10:18:04
    RMAN-05501: aborting duplication of target databaseSo, my next test was not to give any Point In Time, that is just issue the duplicate without SET UNIL clause and this time, and this time it behaved, it restored the control file from c-20120223 and completed the duplicate process. So what does this tell us? We cannot do a POINT IN TIME duplicate using RMAN DUPLICATE????
    rman auxiliary /
    RMAN> run
    2> {
    3> duplicate database to rman01s backup location '/u01/app/oracle/exp/rmantest_stl';
    4> }
    contents of Memory Script:
       sql clone "alter system set  control_files =
      ''+RMAN01D_DATA/rman01s_stl1/controlfile/current.270.776089489'', ''+RMAN01D_RECO/rman01s_stl1/controlfile/current.263.776089489'' comment=
    ''Set by RMAN'' scope=spfile";
       sql clone "alter system set  db_name =
    ''RMANTEST'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile from  '/u01/app/oracle/exp/rmantest_stl/c-20120223';
       alter clone database mount;
    }Just checking if anyone stumbled upon these findings. An Oracle SR is already in place, so just waiting for an update from them.
    Thanks,
    Shiva

  • Disaster Recovery from tape library!

    Hi,
    I am using oracle 10g and Backup Exec 12 as the media management software. How do i perform the disaster recovery. My entire scenario is like this:
    Server A has the DB (Database).
    Configured Backup Exec with RMAN and took full DB backup along with autobackup of controlfile to the tape.
    Server A crashes and is unusable.
    Installs Oracle on server B and needs to restore the DB on this new server.
    I know the DBID of the DB but how to configure RMAN to work with Backup Exec, so that I can restore the db from the tape library?
    When you configure the RMAN integration with Backup Exec, it finds the database running on the server and will perform the integration. But in my case, since the database does not exist, how will the Backup Exec agent configure the integration?
    How do we go about the restoration to Server B in this case?
    Thanks!

    Hi!
    I am still not able to restore the db. The scenario is like:
    Took a full database backup to tape from server A with controlfile autoconfig
    Trying to restore the db on server B. The following is the script used to restore.
    connect target /
    set dbid=152417844;
    startup nomount;
    run
    +{+
    allocate channel sbt1 type 'sbt_tape';
    SEND 'BSA_SERVICE_HOST=ipaddress,NBBSA_TOTAL_STREAMS=1';
    set controlfile autobackup format for device type 'sbt_tape' to 'cf_%F';
    restore spfile from autobackup;
    restore controlfile from autobackup;
    alter database mount;
    restore database;
    recover database;
    release channel sbt1;
    +}+
    alter database open resetlogs;
    When i try to restore, the output is:
    channel sbt1: looking for autobackup on day: 20090624
    channel sbt1: looking for autobackup on day: 20090623
    channel sbt1: looking for autobackup on day: 20090622
    channel sbt1: looking for autobackup on day: 20090621
    channel sbt1: looking for autobackup on day: 20090620
    channel sbt1: looking for autobackup on day: 20090619
    channel sbt1: looking for autobackup on day: 20090618
    channel sbt1: no autobackup in 7 days found
    released channel: sbt1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/24/2009 11:19:28
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    Please advice!
    Edited by: Libra DBA on Jun 24, 2009 1:39 PM

  • Looking for comment on disaster recovery plan

    Looking for some comment on where we are and where we’re planning on going with our Continuity of Operations / Disaster Recovery plan.
    Current setup is Oracle 10.2.0.2.0 on HP-UX Itanium 64-bit. OAS / Forms 9i on a separate HP-UX Itanium box. We do not have control over the version of Oracle or the hardware. I am pushing the powers that be on upgrading to 10.2.0.4, but am not holding my breath.
    Basic backup is threefold. DB is in archivelog mode. RMAN full backup is taken weekly. Incremental backup taken daily. These backups are to disk. In addition, a daily full-system backup (to tape) is done with the db shut down, providing a daily cold backup as well as backup of the online backups. Also daily exports – full and schema specific.
    All db files are on an HP SAN unit. SAN replication software is used to mirror all i/o to a similar unit located at a sister site. Likewise, they replicate their SAN to ours. Each site has a pair of backup servers to be used by the other site if needed. Sister site has already tested loading our backup servers, mounting the mirror of their SAN, and starting the db.
    Since sister site is a couple of hours away and crosses major network boundaries, management would like to also put up a DataGuard standby at a facility only 30 minutes away and within our own network. Plan is to host that on duplicate HP servers, but disk would be on a NAS instead of a SAN.
    I have managed a DataGuard setup, but did not create/configure it, so am now digging into the docs, starting with the DataGuard Concepts. I’ve never worked with NAS and am not clear on how it differs from SAN, and what the implications are.
    I'm looking for any comment, especially any red flags, on what I’ve described.

    Satish Kandi wrote:
    Not an expert comment on your setup but just the thoughts that came to my mind while reading this...
    1. What is the setup for backup preservation? Is it in one of the servers only? Is the backup also replicated?Belt and suspenders. The backup location on disk is part of what gets mirrored to the sister SAN. Plus, the nightly system backup to tape picks it up as well.
    2. What about OAS/Forms 9i backup? You have not mentioned anything about that.That is also mirrored to the sister SAN.
    3. What is the archive log generation frequency? Or how much data loss can you afford?A typical day will see one or two dozen archivelog files.
    >
    In addition, a daily full-system backup (to tape) is done with the db shut down, providing a daily cold backup as well as backup of the online backupsLucky you :-) but I don't see a need for this with the levels of backup that you have (especially with RMAN weekly backup and daily archive log backup). No, no need, but it does give us another layer at no real cost. This cold backup is really just a byproduct of a daily full system shutdown and backup. We have a high tolerance for system down time, but low tolerance for data loss.

  • Disaster Recovery Plan for SAP BW

    Dear All,
    We are planning for robust Disaster Recovery Site for BW . We have similar  R3 & BIW  servers at DR site at different location and data is being copied every 3 Hrs.
    R3 & BIW at DR site is exact replica of primary site. When primary site is down DR site will act as a primary. In that case we might face data loading issue from DR R3 to DR BW because of source system change. If we change the source system then we loose data consistency and might need initialisation. We are looking for the solution which will involve less efforts to up the system.
    Does anyone has done this or overcome this situation ?
    Regards,
    Manish

    Hi Raman,
    We are doing disaster recovery test for both ECC and BW systems so whole PR system switched to DR system for some time and then back to PR system. so in that case what precautions we need to take from BW side?
    Thanks
    Bhavin

Maybe you are looking for

  • HP Mini 110 bios password reset Plz

    Pls help Me  CNU9372HKN thank you so much  Best regard. This question was solved. View Solution.

  • Still images per second and "shutter times" for webcams

    Hi! I'd like to know how frequent a webcam (such as Optia AF) can take still images (at for example 2 megapixel) and send them to the PC via USB. Also, I'd like to know how long the "shutter time" is for still images, and if it can be adjusted. I wan

  • How to creat commitment for PO PR but not creat statistical cost for GR

    Hi, Quantities and Values in Valuated Project Stock: Example - Material - SAP Library Planning Material FIN-M is assigned to network activity V10 and is managed in the project stock for WBS element P/4711.1. The network type is flagged as appended an

  • Hp p7-1010 retail UPGRADING HELP

    Hi i have a p7-1010 retail and i was wondering if my upgrades would work for this computer. PSU-CORSAIR Builder Series CX600 600W ATX12V v2.3 80 PLUS BRONZE Certified Active PFC Power Supply Video card-100357-2GL Radeon HD 7750 2GB 128-bit DDR3 PCI E

  • How to Process Customer Orders

    My Question is Using the AdventureWorks2012 Database how would you create a Stored Procedure that will Allow a customer to buy multiple items and the store proc process the whole things and nsert all the necessary information in the Sales.OrderHeader