Restoring rman backup to sysdate-n while having latest full backup

is it possible to restore n-5 days database state while having latest full rman backup (n) ???

Hi,
You need the archivelog and a backup prior to the date you want to restore.
So:
You cannot return back BEFORE the date of a backup.
You can go back to the date of a backup if you have no archivelog (or archivelog backup).
You can go back to the date of a backup and anytime AFTER if you have the archivelog (or archivelog backup).
You can go prior (depending of the retention) if you use flashback (flashback log).

Similar Messages

  • Restore database in the past using only archivelog without full backup

    Hi,
    We have a 11g Oracle database up & running.
    We don't have a full backup, but we have all archived log from the last 2 months.
    Is it possible to "restore" the database using archived logs in a date in the past?
    I mean for example 3 days ago?
    Thanks in advance.

    user8973191 wrote:
    Oh, ok Vijayaraghavan K.
    Thx for u help.
    And about the users ?
    i need to create the "same" user in another machine ?
    For example:
    In this machine i using the "system" user, where i have my tables.
    Another machine, when i restore, my tables will go to the "system" user too? or i can choice? or i need to create one?A true backup is a copy of the data files at the file/block level. The restore is therefore a restore of the data files/blocks. Applying the redo (archive logs) is also done at the block level. None of that knows or cares (or needs to know or care) about logical objects (such as users, tablespaces, tables, rows, etc) within the database. so if you do a proper restore, you are restoring files to a consistent state and thus everything that was defined within those files will be there when restored.

  • Time Machine repeatedly does full backups, including FileVault while logged in

    So let me preface this - for months I'd hoped for a way that Time Machine could backup my FileVault encrypted account without logging out.  Last night Snow Leopard spontaneously started doing this.  I know many may think that I'm looking a gift horse in the mouth, but read further and hopefully someone can help me make sense of this.
    Last night I attached my external 1TB USB hard drove to my 15" MBP (spring 2010 model) running OS X 10.6.7.  It started doing a Time Machine backup automatically, as usual.  Since I was logged into my account that uses FileVault (a massive home folder - 220GB) I expected a fast backup of things only outside my home folder.  As i looked at the details, however, i quickly realized that it was backing up all 270GB of data on my hard drive - including my FileVault account while still logged in! 
    At first i thought i just got lucky - i'd been craving this feature for years and it just happened to me without even doing anything.  Curious guy that i am, i logged out of my acct with my USB drive still attached to see what would happen.  After FileVault cleared out space in my home folder, it did _another_ backup, that took about 10 minutes to complete.  This seemed strange so i logged back in and started another backup manually.  To my utter shock, it started doing the whole 270GB over again! 
    I even cleared out my TM drive, erased, reformatted, checked permissions, etc etc and did the same on my system drive, hoping that it was just a matter of broken permissions.  No change.
    So there's two things going on here and i'm pretty concerned about both:
    1) Why is TM backing up my entire encrypted home folder while i'm still logged in??? Apple has clearly designed TM and FV to NOT work this way for data integrity reasons and the fact that it's happening has me freaked out a bit over the reliability of my backups.
    2) Why is TM doing full backups after each time i login to my account?  If i stay logged in, it appears to only do incremental (normal) backups but if i logout, then re-login and allow the hour to pass and let a backup start on its own, it starts the whole 270GB again.
    I'm getting to the point of wiping the system and starting from scratch but since i presently live in a country with no Apple store and extremely poor internet access, that prospect horrifies me
    any ideas?
    many thanks,
    -Tim

    Thanks for the input Pondini -
    I tried deleting the file as mentioned in #A4 and it still had the problem.  Last weekend i finally got a brand new hard drive and reinstalled OSX 10.6.3 from scratch, then promptly applied the 10.6.7 combo update.  I purposely chose to NOT import my old user from backup and instead set up everything again manually (royal pain, but the only way i could be sure that i wouldn't bring the problem with me).  Today i whipped out my TimeMachine drive and set it up for backups.  I crossed my fingers and it AGAIN started backing up all 250+GB of my system from within my FileVault protected account. 
    My wife's MBP is still running 10.6.4 and i'm beginning to wonder if his is an issue with 10.6.7 since i'm relatively certain i didn't experience this before that upgrade. 
    I've checked my wife's exclusions under Options and her home folder is NOT in that list, yet her TM is not attempting to backup everything until she logs out of her FV acct.
    In response to Linc Davis, _yes_ it was backing up my info into a sparsebundle file, not just the raw unencrypted data, which is extremely strange.
    If i DO add my home folder to the exclude list, will it still be backed up when i log out?
    At this point, i'm thinking my next steps are:
    1) try a different TM backup drive, even though i've wiped and checked my current drive numerous times
    2) downgrade to an older version of Snow Leopard to see if 10.6.7 is the culprit
    Any other ideas?

  • How to do following restore? Full backup takes long and transaction backup in the middle.Thanks!

    One database starts to run full backup at 10am. Full backup finishes at 11:45 AM
    transaction log backups every 30 minutes: 10:00am, 10:30am,11:00 am , 11:30 am and 12:00 PM
    At 1:30 PM
    I need to restore database back to 12:00PM.
    So I should restore:
    1) Full backup at 10:00 am + transaction log backup 10:30am+ transaction log backup 11:00 am +transaction log backup at 11:30 am + transaction log backup at 12:00 PM
    or
    2) Full backup at 10:00 am + transaction log backup at 12:00PM
    Because full backup starts at 10:00 am and ends at 11:45 am, I am not sure 1) or 2) should I choose.
    Please let me know which one is correct--1) or 2) .Thanks

    alternatively you can make use of 
    RESTORE HEADERONLY FROM <BACKUP_DEVICE>
    database backup has LSN number information in te backup header, and last LSN will help you to locate next log backup in
    sequence to be restored.
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    Praveen Dsa | MCITP - Database Administrator 2008 |
    My Blog | My Page

  • Time Machine does a full backup after a full restore

    Hi,
    To test Time Machine (as you should always do with any backup system) I decided to do a full restore of one of my Macs. This went fine (after figuring out how to mount my remote backup disk).
    However I noticed that when the restored machine did its first scheduled Time Machine backup after being restored it did what pretty much amounted to a full backup (taking ages).
    I believe Time Machine should be clever enough to know that the restored files are the same as the backed up ones, and there is no need to copy new versions.
    Cheers, Ed.

    Indeed not unexpected, however it would be easy to fix this in the future by linking the restore into the existing baseline (given that it is a direct copy of it) as it writes the files.
    It is worth mentioning because if you have a smallish backup disk (I don't) then writing the second baseline may flush out a number of your older weekly backups that you would rather have retained. It will also eventually mean that you will always have those two baselines and therefore restrict the number of valid backups that you can keep.
    Cheers, Ed.

  • Diffrent name for backuppiece archivelog and full backup

    Hi,
    Is it possible to set in RMAN diffrent name for archivelog backup and full backup?
    I need to recognize file in os like.
    archivelog backup in backuppiece ... arch_%U
    full backup in backuppiece ... full_%U
    Tx & reg
    Tom
    http://oracledba.cz

    Hi Soli!
    You may use the code from the following example to solve your problem:
    <pre>
    RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE disk FORMAT '/u01/backups/datafiles_%U.bkp';
    ALLOCATE CHANNEL ch2 DEVICE TYPE disk FORMAT '/u02/backups/controlfile_%U.bkp';
    ALLOCATE CHANNEL ch3 DEVICE TYPE disk FORMAT '/u03/backups/archivlog_%U.bkp';
    BACKUP
    (DATAFILE 1,2,3,4 # channel ch1 backs up datafiles
    CHANNEL ch1)
    (CONTROLFILECOPY '/oracle/copy/cf.f'
    CHANNEL ch2) # channel ch2 backs up control file copy
    (ARCHIVELOG FROM TIME 'SYSDATE-14'
    CHANNEL ch3); # channel ch3 backs up archived redo logs
    Hope that helps!
    yours sincerely

  • TC keeps doing a full backup

    This is the third time my 1TB Time Capsule has done a full "initial" backup. I have absolutely no idea why it's doing this. Each time it apparently overwrites the previous backup.

    Zmantra,
    Welcome to the Apple discussions. Next time feel free to start a new thread as you will likely get more responses that way. But the following might give you some ideas as to what is happening.
    *_Incremental Backups Seem Too Large!_*
    Open the Time Machine Prefs on the Mac in question. How much space does it report you have "Available"? When a backup is initiated how much space does it report you need?
    Now, consider the following, it might give you some ideas:
    Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
    One poster observed regarding Photoshop: “If you find yourself working with large files, you may discover that TM is suddenly backing up your scratch disk's temp files. This is useless, find out how to exclude these (I'm not actually sure here). Alternatively, turn off TM whilst you work in Photoshop.” [http://discussions.apple.com/thread.jspa?threadID=1209412]
    If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
    If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
    If you have recently created a new disk image or burned a DVD, Time Machine will target these files for backup unless they are deleted or excluded from backup.
    *Events-Based Backups*
    Time Machine does not compare file for file to see if changes have been made. If it had to rescan every file on your drive before each backup, it would not be able to perform backups as often as it does. Rather, it looks for EVENTS (fseventsd) that take place involving your files and folders. Moving/copying/deleting/saving files and folders creates events that Time Machine looks for. [http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14]
    Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your directories. Every one of these changes is recorded by the OS as an event. Time Machine will backup every file that has an event associated with it since the installation.
    Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
    George Schreyer describes this behavior: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
    *TechTool Pro Directory Protection*
    This disk utility feature creates backup copies of your system directories. Obviously these directories are changing all the time. So, depending on how it is configured, these backup files will be changing as well which is interpreted by Time Machine as new data to backup. Excluding the folder these backups are stored in will eliminate this effect.
    *Backups WAY Too Large*
    If an initial full backup or subsequent incremental backup is tens or hundreds of Gigs larger than expected, check to see that all unwanted external hard disks are still excluded from Time Machine backups.
    This includes the Time Machine backup drive ITSELF. Normally, Time Machine is set to exclude itself by default. But on rare occasions it can forget. When your backup begins, Time Machine mounts the backup on your desktop. (For Time Capsule users it appears as a white drive icon labeled something like “Backup of (your computer)”.) If, while it is mounted, it does not show up in the Time Machine Prefs “Do not back up” list, then Time Machine will attempt to back ITSELF up. If it is not listed while the drive is mounted, then you need to add it to the list.
    *Recovering Backup Space*
    If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space.
    Launch Time Machine from the Dock icon.
    Initially, you are presented with a window that represents “Today (Now)”. DO NOT make changes to file while you see “Today (Now)” at the bottom of the screen.
    Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
    Now, navigate to where the unwanted file resides.
    Highlight the file and click the Actions menu (Gear icon) from the toolbar.
    Select “Delete all backups of <this file>”.
    *FileVault / Boot Camp / iDisk Syncing*
    Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder if you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.
    Cheers!

  • Time Machine won't create a bootable full backup

    Equipment : Mid 2010 13" Unibody MBP, Late 2010 1Tb Apple Time Capsule, 4Gb RAM, 240Gb HDD, OSX Mavericks
    Upgraded to Mavericks a few months ago, Time Machine has been backing up incrementally to my 1Tb Time Capsule no problem for years.
    I have just bought a SSD so , feeling very confident,  popped out the Seagate Momentus and replaced with PNY 240gb SSD. Booted off my Mavericks recovery CD, selected restore from a previous Time Machine Backup, selected My Time Capsule, MyMac.sparsebundle,Continue
    To my horror, the last full backup was June 2012, kind of worked out why - I had some Exclude options in Time Machine preferences that excluded /Caches , Download folder, Trash so wasnt creating any Full backups
    In order did the following
    Put the Seagate HDD back in and booted up successfully
    removed all the excludes in Time Machine ,
    renamed MyMac.sparsebundle to MyMacX.sparsebundleX ,
    kicked off Back Up Now in the confidence that this would create a brand new backup and do a full backup of the disk
    It didnt, what looked like a full backup started taking about 2h though no full backups found in the newly created MyMac.sparsebundle, so something isnt being backed up to make a full bootable backup
    Checked to see if there were any other system excludes with
    sudo defaults read /Library/Preferences/com.apple.TimeMachine SkipSystemFiles
    Answer came back as 0, so obviously not that
    Rebooted my Mac and Time Capsule, deleted MyMac.sparsebundle, did step 4 again
    Exactly the same result.
    So at this time, I cannot create a full backup to enable a HDD swap out with my SSD
    Help, Ideas anyone

    You need to partition and format the drive first.
    Drive Partition and Format
    1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    Quit Disk Utility after formatting is finished. Install Snow Leopard. Upgrade to Mavericks.

  • Difference between Full backup and lncremental level 0 backup

    Hi,
    What is the difference between Full backup and lncremental level 0 backup?
    what I understand is:
    Actually incremental backup backups all the block containing data and skips the blocks that are unused.
    Similarly full backup backups all the blocks containing data.(does it skip unused blocks ?????).
    The only difference that I feel is that the level 0 backup is recorded as an incremental backup in the RMAN repository, so it can be used as the parent for a level 1 backup where Full database backup is not recorded in the Rman respository and cannot be used as parent for level 1 backup.
    (if you still feel you have some more points to share regarding the difference between backups, I request to share with me)
    so my question here is
    Can we use Incremental level 0 backup for full database recovery. Else is there any compulsion like we must only use full database backup for full database recovery?
    can anyone throw light on this
    with regards;
    Boo

    nowhere in this thread we talked about the image copies as we are only talking about the incremental backup.
    The word "always" has a meaning. If you now wish to say, "well, RMAN will mostly use a level 0 or full backup, except when there are image copies around" then the word "always" doesn't fit your newly-revised description. That would make it an inappropriate word to use. And indeed, it's a factually wrong word to use.
    If you want to get really picky about it, incidentally, the words 'datafile copy' appear in a post from me at Aug 4, 2007 6:03 PM whereas your post (in which the "always" word was used) only appears Aug 4, 2007 8:32 PM -a full 2 and a half hours (and and two posts) AFTER the concept of image copies had been mentioned.
    But regardless of times: you can't just pretend image copies don't exist just because they haven't been mentioned so far in a thread. If you post "this is the way something ALWAYS works", you'd better be completely right about it, because "ALWAYS" is a big word. And there's no grey about this: either "always" is right, or it's wrong. And in this case, it's wrong: there are many times when RMAN will not do what you baldly asserted it would do. Image copies aren't some rare, exotic beast, either... so the occasions when your 'rule' breaks down are many and common.
    until now I was simply beliving in what Oracle docs and metalink notes says
    Try not to do that. Because you will fall into error after error if you do. Metalink is not the Holy Gospel of Oracle. Testing is, and it's because I've been testing this stuff since 1999 I will, on this occasion, decline your kind invitation to do "a small test". Been there, done that.
    All of which leaves us discussing things that are of no relevance to the original poster, and I have no desire to take the thread off into silly areas of dispute. So I will leave it there, and I have nothing further to say on the matter. RMAN does what it does, and what it does is not what you said it would do. End of story.

  • 2nd backup always full backup

    Hi:
    I'm setting up time machine to work on a USB drive attached to an airport extreme.
    Just reformatted the drive to GUID and took the apostrophes and periods out of my network name.
    Things work but there is one problem: the second backup is always a full backup. Ie it backs up 90 gigs, then the second backup is again a 90gig backup.
    After that it works fine.
    For my first backup I'm plugging the drive in directly through USB, then I go and plug it in through the airport extreme, then when it starts to do a full 90 gig backup for the second backup I cancel, unplug the drive, plug it back in through USB and let it finish the second backup.
    After that things work normally but I'm concerned because there's an extra 90 gig on my disk=my disk will get full quickly. I'm using a 500gig disk to backup two macbooks with about 90gig a piece on them currently.
    From console the only thing that looks out of place is:
    25/03/08 2:27:45 PM /System/Library/CoreServices/backupd[2925] Event store UUIDs don't match for volume: Gojira
    Should I be concerned? Am I doing something wrong here?

    Short answer, yes. Both computers backed up for the second time as if it were an initial backup.
    However that was before I reformatted the hard drive -- it wasn't GUID.
    Sorry, that's confusing. Here's what happened:
    1. Plugged in macbook. Did full backup.
    2. Second backup on macbook: did full backup again.
    3. From then on with macbook: normal backups.
    4. Plugged in macbook pro, did full backup.
    5. Second backup on macbook pro did full backup.
    6. From then on macbook pro backedup normally.
    7. Realized I needed to reformat the drive to GUID. Refmoratted.
    8. Did first backup with macbook pro. Did full backup.
    9. Did second backup with macbook pro... doing full backup. I'm mid-backup right now.
    For my initial backup on the macbook pro, console reported 465.29GB available. For the second backup 379.48GB available. Currently in the finder -- I am mid-second backup -- it reads 301GB available. So it seems like it's copying everything on my computer twice...
    - P

  • Restore RMAN from different Database Rman backup

    Hi Everybody
    I am practicing Rman so I have one query that how to restore rman backup from another database.
    For Example :
    1. I have Rman backup of DB1 with level 0 and level 1 cumulative database plus archievelog
    2. I need to import or restore Rman backup of DB1 to another database DB2.
    What is the procedure for doing the above queries. Please anyone one help me out.
    I have using oracle 10g r2 running in windows server 2003.
    Thanks in advance.

    These are the steps ; you need to write the appropiate commands for each step: Hope it helps!
    1) Take appropriate RMAN backup of the database db1. Note that you should turn on the CONTROLFILE AUTOBACKUP configuration so that we have the controlfile backed up after the database backup. When we restore the controlfile on new host from this autobackup piece, it will have the information of the latest backup.
    2) Create a PFILE for the destination database db2 using the database db1
    3) Move the backup pieces and the modified INIT.ORA file to the new host. Starting from 10g it is NO longer compulsory to copy the RMAN backup pieces to exactly the same location on the new host as the production location.
    4) Use the pfile created above to STARTUP NOMOUNT the database on the new host
    5) Now invoke RMAN and restore the controlfile specifying the location where the controlfile autobackup piece is restored on this new server. You can mount the database once the controlfile is restored successfully.
    6) You can skip this step if you have restored the RMAN backup pieces to exactly the same location they were backed up on database db1. If this is not the case then you need to catalog the RMAN backup pieces to make RMAN aware of thier new location on the new host. Note that CATALOG BACKUPPIECE command is available only starting from 10g.
    7) Having determined the point up to which media recovery should run, start the restore/recovery using for example:
    RMAN> run {
    2> set until sequence 59 thread 1;
    3> set newname for datafile 1 to '/new_location/system01.dbf';
    4> set newname for datafile 2 to '/new_location/undotbs01.dbf';
    5> set newname for datafile 3 to '/new_location/sysaux01.dbf';
    6> set newname for datafile 4 to '/new_location/users01.dbf';
    7> restore database;
    8> switch datafile all;
    9> recover database;
    10> }

  • Error  While  Restoring  Rman database

    file names not getting convert..even after putting db_file_name_convert
    db_file_name_convert='/data1/oradata/UAT/','/opt/u02/app/oracle/oradata/oamnint'
    logfile_name_convert='/data2/oradata/UAT/','/opt/u02/app/oracle/oradata/omanint','/oracle/app/oracle/oradata/','/opt/u02/app/oracle/oradata/omanint'
    we use this parameter
    ORA-19502: write error on file "/data2/oradata/NUAT/undotbs01.dbf", block number 539328 (block size=8192)
    ORA-27072: File I/O error
    Additional information: 4
    Additional information: 539328
    Additional information: 249856
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00017 to /data2/oradata/UAT/DASCORE.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/dbkp/rmanbackup01/rmanbkp_old/17ou0733_1_1_UAT_20140113
    channel ORA_AUX_DISK_1: piece handle=/opt/dbkp/rmanbackup01/rmanbkp_old/17ou0733_1_1_UAT_20140113 tag=TAG20140113T194559
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:26
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 01/15/2014 17:44:55
    RMAN-05501: aborting duplication of target database
    RMAN-05556: not all datafiles have backups that can be recovered to SCN 714518081
    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 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
    Thanks.

    Is your UNDOTBS is in FS "/data2/oradata/NUAT/undotbs01.dbf" ? Did you convert this FS to new FS name? First error seems to be issue with this.
    Second issue is seems to be you dont valid backup for the  SCN 714518081. Pls give us the restore script and also check whether you have valid backups.

  • While intending to perform a clean install of Mountain Lion while continuing with old apps and files, is it a waste to restore a backup that was made while running Mountain Lion as an UPgrade from Lion?

    While intending to perform a clean install of Mountain Lion while continuing with old apps and files, is it a waste to restore a backup that was made while running Mountain Lion as an UPgrade from Lion?
    Originally I was running Mountain Lion as an UPgrade from Lion. I created a backup in Time Machine, performed a clean install of Mountain Lion, then I proceeded to use Time Machine to restore the back up.
    When thinking about the essence of a back up restore, it occurrs to me that for all I know, I may have just wated my time IF Time Machine also restores all the old unneeded files that remain from Lion after an upgrade.
    Since the backup was made while running Mountain Lion as an upgrade from Lion, did restoring this backup defeat the purpose of a clean install by reinstalling old Lion files?
    If so, how can I re-do the last portion of the process so that I get all my home-folder files and apps back without the full bulk of old Lion files? Migration assistant I'm guessing?
    -Chris

    Hello John!
    Thank you for your response which solved my problem. For other users who may stumble upon this, I'll clear up the confusion and share how I solved the problem with your help; When looking for answers to my computer problems, finding unresolved questions where person B offers a solution and person A never comes back and says "That worked, thank you.", it demonstrates a "k-thnx-bye" user mentality that leaves others with the same problem lost. Without further ado:
    It is not clear what you did because the meaning of "clean install" is vague. You can erase a volume and install an OS which leaves none of its previous content intact,
    This is what I did: I erased the volume leaving no previous content intact, while then installing OS X Mountain Lion.
    or you can upgrade an existing OS (or reinstall the same one) which does not alter your user - installed files.
    An upgrade to Mountain Lion from Lion is what I started with initially before erasing anything. This was undesirable. Since this can cause Macs to run slower (especially whereas I'm using a mid-2011 Mac Mini), my goal was to go from operating within an upgrade to Mountain Lion, to operating within an installation of Montain Lion that was not preceded by any other oprating system.
    Hence a "clean install of Mountain Lion while continuing with old apps and files" is confusing.
    Well put and understood. What I should have said was:
    1.Erase the volume
    2.Install Mountain Lion clean
    3.Confirm that Mountain Lion is functioning properly
    4.Proceed to use either Time Machine or Migration Assistant to Import/Migrate/Copy over only two things; My old apps (That had been stored originally in the designated Applications folder) and all files and folders originally stored in the home folder under users.
    If you restore from a Time Machine backup then all modifications that occurred subsequent to that backup become erased. It renders moot any OS X upgrade performed subsequent to that backup.
    That makes sense and is just as I later suspected.
    If so, how can I re-do the last portion of the process so that I get all my home-folder files and apps back without the full bulk of old Lion files? Migration assistant I'm guessing?
    Yes.
    This is what I did and everything works perfectly. Thank you so much once again!
    -Chris

  • Restore RMAN Backup

    Dear All,
    I am practicing Oracle Restore scenarios on my Oracle 9i database. Once I complete my tests in Oracle 9i I will move up to 10g and then finally to 11g.
    Following is my recovery scenario:
    1) I did NOT configure Recovery Catalog
    2) I would like to restore my databse from a 15 days old backup
    3) control_file_record_keep_time is set to 7 days.
    4) Backups are on tape.
    Can you guys please shed some light on how to I proceed?
    - P

    In oracle 9i , check , which situation you can perform complete recovery and in which situations you have to select incomplete recovery.
    check the notes by Alejandro Vargas, BACKUP AND RECOVERY SCENARIOS
    http://www.google.co.in/#hl=en&q=oracle+backup+and+recovery+scenarios&aq=0&aqi=g10&aql=&oq=oracle+backup+and+reco&gs_rfai=&fp=aa24f2b3591f5f42
    [PDF]
    Backup and Recovery Scenarios - Backup & Recovery Check List
    - 4:11am
    File Format: PDF/Adobe Acrobat - Quick View
    Oracle Support Israel. User Managed Recovery Scenarios And Configuration .... 4. recover automatic database using backup controlfile; ...
    static7.userland.com/oracle/gems/.../BackupAndRecoveryChecklist.pdf
    refer this, this will helps you.
    Can one restore RMAN backups without a CONTROLFILE and RECOVERY CATALOG?_
    http://www.orafaq.com/wiki/Oracle_database_Backup_and_Recovery_FAQ#Can_one_restore_RMAN_backups_without_a_CONTROLFILE_and_RECOVERY_CATALOG.3F
    Edited by: rajeysh on Jun 20, 2010 6:36 PM

  • Restoring Rman backup on New Host with different directory structure

    Hi,
    I have a following scenario to clone the database.
    1. clone the database on new server
    2. source is non - ASM and target is ASM
    3. On source incremental level 0 backup taken on disk connecting to catalog, the backup is moved to target host to different directory structure
    4. source is running on 32-bit Linux two node Rac and Target is running on 64-bit Linux two node Rac
    I did the following steps and getting below error:
    1. I copied incremental Level 0 backup to target server(where we need to build new db) to different directory structure
    2. On target i created pfile and build the instance, as dbf file are in multiple locations in source i put following tow parameters in init.ora of target database
    *.db_file_name_convert =(/u02/oradata/app1p/,+QADATA2/udev/datafile),(/u03/oradata/app1p/,+QADATA1/udev/datafile),(/u12/oradata/app1p/,+QADATA1/udev/datafile,),(/u99/oradata/app1p/,+QADATA1/udev/datafile),(/u09/oradata/app1p/,+QADATA1/udev/datafile),(/u14/oradata/app1p/,+QADATA1/udev/datafile),(/u07/oradata/app1p/,+QADATA1/udev/datafile),(/u06/oradata/prod/,+QADATA1/udev/datafile'),(/u05/oradata/app1p/,+QADATA1/udev/datafile)
    *.log_file_name_convert =("/u99/oradata/app1p/","+QADATA2/udev/onlinelog/")
    3. connected to rman -->> started db in nomount -->> restored the controlfile --> cataloged the backup piece and then i am trying to restore
    All the above steps i did using the Doc id *How To Restore Rman Backups On A Different Node When The Directory Structures Are Different [ID 419137.1]*
    script i am using is :
    RMAN> run {
    2> set until time "to_date('DEC/20/2010 05:30:00','Mon/DD/YYYY HH24:MI:SS')";
    3> allocate channel c1 device type disk;
    4> allocate channel c2 device type disk;
    5> allocate channel c3 device type disk;
    6> allocate channel c4 device type disk;
    7> set newname for datafile 1 to '+QADATA1/UDEV/DATAFILE';
    8> set newname for datafile 2 to '+QADATA1/UDEV/DATAFILE';
    9> set newname for datafile 3 to '+QADATA1/UDEV/DATAFILE';
    10> set newname for datafile 4 to '+QADATA1/UDEV/DATAFILE';
    11> set newname for datafile 5 to '+QADATA1/UDEV/DATAFILE';
    12> set newname for datafile 6 to '+QADATA1/UDEV/DATAFILE';
    13> set newname for datafile 54 to '+QADATA1/UDEV/DATAFILE';
    set newname for datafile 63 to '+QADATA1/UDEV/DATAFILE';
    14> 15> set newname for datafile 67 to '+QADATA1/UDEV/DATAFILE';
    16> set newname for datafile 68 to '+QADATA1/UDEV/DATAFILE';
    17> set newname for datafile 50 to '+QADATA1/UDEV/DATAFILE';
    18> set newname for datafile 39 to '+QADATA1/UDEV/DATAFILE';
    19> set newname for datafile 38 to '+QADATA1/UDEV/DATAFILE';
    20> set newname for datafile 7 to '+QADATA1/UDEV/DATAFILE';
    21> set newname for datafile 9 to '+QADATA1/UDEV/DATAFILE';
    22> set newname for datafile 8 to '+QADATA1/UDEV/DATAFILE';
    23> set newname for datafile 11 to '+QADATA1/UDEV/DATAFILE';
    24> set newname for datafile 10 to '+QADATA1/UDEV/DATAFILE';
    25> set newname for datafile 66 to '+QADATA1/UDEV/DATAFILE';
    26> set newname for datafile 48 to '+QADATA1/UDEV/DATAFILE';
    27> set newname for datafile 47 to '+QADATA1/UDEV/DATAFILE';
    28> set newname for datafile 12 to '+QADATA1/UDEV/DATAFILE';
    29> set newname for datafile 13 to '+QADATA1/UDEV/DATAFILE';
    30> set newname for datafile 14 to '+QADATA1/UDEV/DATAFILE';
    31> set newname for datafile 15 to '+QADATA1/UDEV/DATAFILE';
    32> set newname for datafile 16 to '+QADATA1/UDEV/DATAFILE';
    33> set newname for datafile 18 to '+QADATA1/UDEV/DATAFILE';
    34> set newname for datafile 17 to '+QADATA1/UDEV/DATAFILE';
    35> set newname for datafile 19 to '+QADATA1/UDEV/DATAFILE';
    36> set newname for datafile 69 to '+QADATA1/UDEV/DATAFILE';
    37> set newname for datafile 60 to '+QADATA1/UDEV/DATAFILE';
    38> set newname for datafile 59 to '+QADATA1/UDEV/DATAFILE';
    39> set newname for datafile 55 to '+QADATA1/UDEV/DATAFILE';
    40> set newname for datafile 53 to '+QADATA1/UDEV/DATAFILE';
    41> set newname for datafile 44 to '+QADATA1/UDEV/DATAFILE';
    set newname for datafile 22 to '+QADATA2/UDEV/DATAFILE';
    42> 43> set newname for datafile 21 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 20 to '+QADATA2/UDEV/DATAFILE';
    44> 45> set newname for datafile 72 to '+QADATA2/UDEV/DATAFILE';
    46> set newname for datafile 70 to '+QADATA2/UDEV/DATAFILE';
    47> set newname for datafile 65 to '+QADATA2/UDEV/DATAFILE';
    48> set newname for datafile 64 to '+QADATA2/UDEV/DATAFILE';
    49> set newname for datafile 57 to '+QADATA2/UDEV/DATAFILE';
    50> set newname for datafile 56 to '+QADATA2/UDEV/DATAFILE';
    51> set newname for datafile 49 to '+QADATA2/UDEV/DATAFILE';
    52> set newname for datafile 45 to '+QADATA2/UDEV/DATAFILE';
    53> set newname for datafile 26 to '+QADATA2/UDEV/DATAFILE';
    54> set newname for datafile 25 to '+QADATA2/UDEV/DATAFILE';
    55> set newname for datafile 24 to '+QADATA2/UDEV/DATAFILE';
    56> set newname for datafile 23 to '+QADATA2/UDEV/DATAFILE';
    57> set newname for datafile 27 to '+QADATA2/UDEV/DATAFILE';
    58> set newname for datafile 28 to '+QADATA2/UDEV/DATAFILE';
    59> set newname for datafile 29 to '+QADATA2/UDEV/DATAFILE';
    60> set newname for datafile 30 to '+QADATA2/UDEV/DATAFILE';
    61> set newname for datafile 73 to '+QADATA2/UDEV/DATAFILE';
    62> set newname for datafile 32 to '+QADATA2/UDEV/DATAFILE';
    63> set newname for datafile 31 to '+QADATA2/UDEV/DATAFILE';
    64> set newname for datafile 34 to '+QADATA2/UDEV/DATAFILE';
    65> set newname for datafile 33 to '+QADATA2/UDEV/DATAFILE';
    66> set newname for datafile 35 to '+QADATA2/UDEV/DATAFILE';
    67> set newname for datafile 36 to '+QADATA2/UDEV/DATAFILE';
    68> set newname for datafile 37 to '+QADATA2/UDEV/DATAFILE';
    69> set newname for datafile 51 to '+QADATA2/UDEV/DATAFILE';
    70> set newname for datafile 43 to '+QADATA2/UDEV/DATAFILE';
    71> set newname for datafile 40 to '+QADATA2/UDEV/DATAFILE';
    72> set newname for datafile 41 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 71 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 58 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 52 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 46 to '+QADATA2/UDEV/DATAFILE';
    set newname for datafile 42 to '+QADATA2/UDEV/DATAFILE';
    73> 74> 75> 76> 77> 78> set newname for datafile 62 to '+QADATA2/UDEV/DATAFILE';
    79> set newname for datafile 61 to '+QADATA2/UDEV/DATAFILE';
    80> set newname for datafile 74 to '+QADATA2/UDEV/DATAFILE';
    81> restore database;
    82> switch datafile all;
    83> recover database;
    84> alter database open resetlogs;
    85>
    86> release channel c1;
    87> release channel c2;
    88> release channel c3;
    89> release channel c4;
    90> }
    Getting the following error, copied lines from the error i am getting.
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 27-DEC-10
    released channel: c1
    released channel: c2
    released channel: c3
    released channel: c4
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/27/2010 08:09:08
    RMAN-06026: some targets not found - aborting restore
    RMAN-06100: no channel to restore a backup or copy of datafile 74
    RMAN-06100: no channel to restore a backup or copy of datafile 73
    Please advice...
    Thanks,
    Tanveer Mohammed

    If you would like, please refer the link:-
    http://gavinsoorma.com/2010/04/creating-an-asm-duplicate-database-from-a-non-asm-database/

Maybe you are looking for