Does RMAN trigger checkpoint before a full backup?

Hello,
My test as follows:
1 insert some data to a table
2 backup full database using rman
3 shutdown abort
4 delete all datafiles(including redo logs)
5 restore and recover database
6 the inserted data can still be found.
I think RMAN triggers checkpoint before a full backup,but I can't verify it,can someone help me?
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Thanks.

Dear user!
As Mr. Baker already stated in his very friendly way RMAN fires a checkpoint before a backup. You may verify it like that:
1.) Use v$datafile_header to get the checkpoint_time of an arbitrary datafile. In my example I've used datafile number 8.
SELECT file#, name, TO_CHAR(checkpoint_time, 'dd.mm.yyyy HH24:MI:SS') as checkpoint_time
from   v$datafile
where  file# = 8;
     FILE#
NAME
TO_CHAR(CHECKPOINT_
         8
/u01/app/oracle/oradata/ORCL/myts1000_01.dbf
17.06.2009 06:58:312.) Export your NLS_DATE_FORMAT environment variable like that:
set NLS_DATE_FORMAT='DD.MM.YYYY HH24:MI:SS'3.) Start RMAN and backup datafile number 8
BACKUP DATAFILE 8;
Starten backup um 17.06.2009 06:58:29
Kontrolldatei der Zieldatenbank wird anstelle des Recovery-Katalogs verwendet
Zugewiesener Kanal: ORA_DISK_1RMAN will show the time when it started the backup.
4.) Query again v$datafile_header like you did in step 1.
SELECT file#, name, TO_CHAR(checkpoint_time, 'dd.mm.yyyy HH24:MI:SS') as checkpoint_time
from   v$datafile
where  file# = 8;
     FILE#
NAME
TO_CHAR(CHECKPOINT_
         8
/u01/app/oracle/oradata/ORCL/myts1000_01.dbf
17.06.2009 06:58:31As you can see the last checkpoint_time of datafile 8 is near to the startingtime of the backup.
I hope that's what you wanna know.
Yours sincerely
Florian W.

Similar Messages

  • Restore Time Machine Full Backup After Catastrophic Failure

    I am new to the Mac and using Time Machine as my primary backup utility. My concern is the way it creates one full backup at the beginning and only incremental ones after that. If the full backup gets overwritten due to the program needing hard drive space, does it know to create another full backup, even if it needs to delete some older incremental backups?
    I am concerned I will need to complete a full restore at some point, and will not be able to do so because there will not be a full backup present on the Time Machine disk.
    Also, who has had to restore from a catastrophic disk failure using an external time machine disk? Is this easy? Does it work properly?

    you concerns are unfounded. due to the way TM keeps data organized every backup is full and independent of any other backups.
    when TM makes a backup it only backs up afresh new and changed files. everything else is _*hard linked*_ to existing backup copies.
    deleting an earlier backup to save space as TM does sometimes has zero effect on the remaining backups. they remain full and complete. doing a full system restore from TM is very easy. you boot from the SL install DVD and select "restore system from backup" from Utilities menu.
    However, it should be noted that TM is still very buggy and doing a full restore can not be tested until you actually do it. therefore, it's advisable to have a double backup using a different backup tool. bootable clones are the best for doing a full restore. CCCloner and Superduper are excellent cloning backup programs.

  • Time machine makes a full backup every time

    I had a 1tb external drive that I was using for Time Machine backups. Fine. No problem. But it got filled up.
    I bought a new external drive - 1Tb. Iwas surprised that within a couple of wweeks, it was filled up.
    I bought a new 2Tb drive.
    Now as I observe what it's doing, it appears ot meaking a FULL BACKUP of my entire hard drive over and over again. I though it was only supposed to do incremental backups? This is nuts! At this rate my 2Tb drive will be filled up in no time. And becasue it's continually backing up many Gb of data it makes the machine run slowly. It is driviing me crazy!!! How do I stop this behaviour? Why is it making a full backup every time? I can't see any preferences to change this. Help!

    Thanks but I think maybe I didn't explain the problem clearly
    My understanding is that Time Machine backs up only the fiels that have changed each time it does a backup. Thi sis how it USED to work. So each hourly backup would take a few minutes, usually, and a 1TB drive lasted well over a year.
    Now it seems to be making a FULL backup of the COMPLETE internal drive EVERY HOUR! So it is currently backing up 135Gb of data and my Time Machine drive is almost half full,, even though I only installed it two days ago!
    When it gets to the point where it needs to start deleting old backups, I would get a new drive and start afresh, saving the old one for reference. I can't buuy a new backup drive every week!
    How do I get it to behave like it used to?

  • RMAN Backup Issue when Full backup file was missing

    Hi,
    On : 11.2.0.2 version, Recovery Manager
    RMAN Backup issue
    Last week we had the NFS Issue where we backup the files onto NFS.
    The problem occurred in the below sequence
    Saturday the backup was successful
    Saturday before deleting the backup files they are copied to tape
    Deleting the backup files via OS command
    Sunday Full backup started but due the NFS issue backup failed(Killed the instance and restarted)
    Did the RMAN Incremental backup which worked on Monday
    On Tuesday RMAN started complaining and started doing the Full backup.
    no parent backup or copy of datafile 1 found
    no parent backup or copy of datafile 3 found
    no parent backup or copy of datafile 24 foundSony any idea why the Incremental backup worked on Monday but not on Tuesday
    Regards
    NM

    Ok here is why I would like exact filenames..
    1) to speed the time of recovery. I am much more familiar with traditional recovery methods than RMAN, and while I myself installed and suggested RMAN for backups, our other (11i) database does not use RMAN and so I am more familiar with traditional recovery. So to be able to recover quickly I want to have these files as close as possible to the original names so that I can use my standard script (from a trace file) to recreate the control fiile. If I can get RMAN to spit out the filies with original names but keep RMAN for making the backup, I may ditch the rman bacjup script in chron and write a traditional hot backup script which copies the files the old fashioned way.
    2) to reduce cloning time. The RMAN duplicate command is not as good as I thought. I was actually easier for me to restore RMAN backups first to a box that has all the same paths, and THEN shutdown (cold) these files and copy them cold to another server, and restore from there. Agaiin if I can get the original file names, I could choose to do recovery either way (RMAN or traditional) in a real emergency instead of being forced to use rman.
    3) to be able to switch to a backup file in the FRA without having to rename it. Seems logical if it is already named correctly.
    thanks ! Marvi

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

  • 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 Does Excessive Full Backups

    Time Machine used to just backup changed material on a hourly basis. It seems that recently every time I look at the progress indicator it is trying to do a full backup of my entire hard drive. Any ideas why?

    Have you recently done a restore?
    I have the same problem. I did a full restore, and TM did a full backup afterwards. This is a "documented feature". Then it did skims every hour. However, if I reboot, it does a full backup the first time after the reboot. It's done 5 full backups (50 GB each) in the past 5 days. I can't afford to shut down my Mac until I figure this out. I only have 170GB of free space on my Time Machine drive.
    Is there any way to see how big each backup is, and delete un-needed ones?
    I'd really like to figure out what causes this problem, before Time Machine starts deleting old stuff I want backed up to make room for all these wasteful new backups.

  • NW65 SP7 doing Full backups not Inc.

    I have recently upgraded to NW65 SP7 and the backup
    software (Veritas Netbackup) does a Full backup instead
    of Incremental backups on these upgraded clients.
    Before the upgrade it worked fine.
    Any ideas ?

    6568593,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Rman full backup issue

    Hi,
    The Media Management Layer GUI shows that my RMAN incremental level 0 (full) finished successfuly in the last 3 weeks.
    Yet , V$RMAN_BACKUP_JOB_DETAILS shows only incremental level 1 and archive log backups :
    SQL> select distinct input_type
      2   from V$RMAN_BACKUP_JOB_DETAILS ;
    INPUT_TYPE
    ARCHIVELOG
    DB INCRIt does not shows DB FULL .
    What elese i can check to be sure that my Full backups are finished successfully ?
    Thanks

    Hi,
    From the results of this statments i dont see DB FULL
    SQL> select distinct object_type from v$rman_status where operation='BACKUP';
    OBJECT_TYPE
    DB INCR
    CONTROLFILE
    ARCHIVELOGIn the second suggested query , the output results suggest for FULL backup :
    select ctime "Date",
           decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type,
            bsize "Size MB"
    from (select trunc(bp.completion_time) ctime
                  , backup_type
                  , round(sum(bp.bytes/1024/1024),2) bsize
           from v$backup_set bs, v$backup_piece bp
           where bs.set_stamp = bp.set_stamp
           and bs.set_count  = bp.set_count
           and bp.status = 'A'
           group by trunc(bp.completion_time), backup_type)
    order by 1, 2;
    Date      BACKUP_TYPE    Size MB
    11-NOV-11 Archive Log       6304
    11-NOV-11 Full           1455291   <<<<===
    11-NOV-11 Incremental     1192.5
    12-NOV-11 Archive Log    4718.25
    12-NOV-11 Incremental     8939.5
    13-NOV-11 Archive Log    7391.25
    13-NOV-11 Full              23.5   <<<<===
    13-NOV-11 Incremental   13892.25
    14-NOV-11 Archive Log    4995.75
    14-NOV-11 Full              23.5   <<<===
    14-NOV-11 Incremental    4045.25
    15-NOV-11 Archive Log       2249
    15-NOV-11 Full              23.5   <<<<====
    15-NOV-11 Incremental    1617.75This of the first Full output : 1455291 M seems OK , but the rest are too small just 23 Mega .
    How come ?
    Also how can i be sure that this FULL backup finished successfully ?
    Thanks Again for you help

  • Repaired permissions, now TM doing a full backup?

    Hi, intelligent user who doesn't have much advanced knowledge concerning what Repairing Permissions even means here.
    So I'm planning on replacing my Macbook Pro's HD, and I just finished making a full bootable backup onto a 200GB FW drive using Super Duper, and checked the "Repair Permissions first" option. I figured that having a latest Time Machine backup (1TB Time Capsule) would make sense as well, so before powering down to unscrew the case I did a Back Up Now. It scanned the entire computer and decided that it would backup all 70 GB fresh. I'm assuming this has something to do with having repaired permissions, but I don't quite know what that means. It may be something similar to what recently happened to me, when I erased my whole computer and refreshed from Time Machine, and then on the next backup it did everything over again instead of updating (for that backup I can still browse dates before that happened as long as I start at the root drive).
    Anyone know what I could do to fix this?

    Brian wrote:
    We have to be careful here: there are three different scenarios:
    New computer or logic board. Time Machine identifies your computer by it's +Media Access Control address+ (MAC address), embedded in the hardware of the logic board. There is a way that some folks have gotten around this on Leopard after a new logic board, but it's tedious and very easy to mess up (I did that, twice!) per the link in #C8 of Troubleshooting. (It's very dangerous on a different Mac).
    That was automated for Snow Leopard, resulting in the Re-Use prompt mentioned in #B5 of Troubleshooting. But, as #B5 specifies, Time Machine usually still does a full backup; the advantage is, Time Machine will delete the old backups normally.
    New drive on the same Mac (per the link you provided). I don't believe that works on Snow Leopard, and I've not seen a hack specifically for Snow Leopard posted here.
    Full restore (from Time Machine, a "clone", or otherwise) to the same drive on the same Mac. This almost always results in a new, full backup. An Apple engineer said that would stop with Snow Leopard, but obviously didn't. Some real techie UNIX guru decided there ought to be a way to do it; he posted a two-page log here a few months ago, of altering all sorts of things via Terminal, converting UUIDs to hex, etc., and claimed to have made it work. But he did it only as an exercise, and even he wouldn't recommend it, even to expert UNIX types.
    . . . I suppose the best way to save space on my Time Capsule (it now has at least 3 copies of my entire system with only very minor differences in the existence of some files) would be to make sure I have all the files I will ever want to have backed up, then delete the old records, which is something I presume wouldn't be too hard, make a fresh backup, then delete whatever I don't think I need right now, knowing it will all be found by scrolling back to July of 2010?
    I'd have to agree. It just isn't worth the hassle, or the risk of damaging something that you might not notice for a long time. I have no problem hacking around with most things, but not my backups.
    Depending on whether Time Machine made new sparse bundles, it may not be too tedious to delete the old backups. See #12 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).

  • Why is TM doing a full backup?!

    After two attempts, I finally thought I had TM working properly. The initial backup took HOURS to complete but, once done, every hour thereafter, it did just a small (measured in kilobytes) incremental backup. Excellent, right?
    Well, I put my machine to sleep for about three hours and, when I fired it back up, TM now has started to do another FULL backup of 70 GB's. It is, of course, taking forever to complete once again.
    What gives? After the initial full backup, every backup thereafter should be incremental, no? This is going to be completely unusable if it doe a full backup daily, or every time the machine has been off for 3+ hours.
    The only thing I did before shutting the machine off was to install two small applications that are used to update the content of my portable GPS. Does the installation of an application force a full backup? Grr...

    I'm running a Macbook Pro C2D. I had 70 GB worth of data that kept getting backed up every time I plugged in my external hard disk even if I hadn't changed any files.
    Maxthewildthing's advice in a different thread worked for me -- your mileage may vary. His advice reportedly came from Apple Support and applies to Intel machines. I've reformatted and elaborated on his steps a bit.
    1. Start Applications > Utilities > Disk Utility.
    2. Highlight the disk you intend to use for Time Machine.
    3. Click "Info" on the file bar. The Partition Map Scheme should read: "GUID Partition Table".
    4. If it does not, you need to re partition your Time Machine disk. Under "Volume Scheme" click the down arrow and select "1 partition".
    5. Name your time machine drive, making sure that the selected format is "Mac OS Extended (Journalled)".
    6. Click "Options" at the bottom and select "GUID Partition Table". Select "Apply." WARNING: This will erase all of the data on the selected disk! Performing this step triggers the repartitioning process and wipes your disk clear.
    7. When it's done, Time Machine will likely open on its own. Turn it off and then on.
    8. Set it up as you would normally, e.g. excluding directories if you wish.
    9. When you finish selecting your options, let it do the initial backup. This will be a lengthy process since it's backing up all of your files for the first time. Subsequent backups will backup only changed files.
    Good luck.
    Steven

  • RMAN restore from older full backup.

    version. 10gR2
    We take full backup every Wednesday (7/2, 7/9, 7/16 and 7/23). I need to restore the database from 7/2 backup. No recovery is needed. How do I do that. Thanks for the help.

    You can specify the BACKUPSET or TAG you want to restore from on the restore command.
    RESTORE ... FROM BACKUPSET
    RESTORE ... FROM TAG = '..'
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta051.htm#sthref796
    Why do you need that specific backup? If you were restoring to a point in time before the 7/9 backup then RMAN will work out to use the 7/9 backup. If no recovery is needed I assume you're testing a restore using VALIDATE and/or PREVIEW?

  • Rman full backup and restoration

    Hi,
    I am planning to upgrade a oracle 10.2.0.2 RAC database to 10.2.0.4.
    If i get any issues during oracle upgradation we need to revert back to 10.2.0.2 again.
    I am not pretty perfect in RMAN, so please let me know
    1) DO I need to take the full backup of RMAN?
    2) Should I take cold backup or hot backup?
    3) If my upgradation fails, how to come back to 10.2.0.2 again by using rman backup?
    Thanks,
    Mahi

    Mahi wrote:
    Hi,
    My new Oracle Home location is different from the old Oracle Home location.Huh? You would apply the patchset to an existing ORACLE_HOME. Where does this different location come in?
    and what operating system are we talking about here?
    >
    Is any one please explain me how to revert back to old 10.2.0.2 database with the RMAN backup if get strucked up during the upgradation.
    If you please explain with the rman commands then that could be great help for me.
    Have you taken a look at the Backup and Recovery Reference?
    >
    Thanks,
    Mahi

  • Time Machine doing full backup of external drive again

    I have a Time Capsule, as well as an external data drive connected to my Mac. The external drive (named Yoda) is NOT excluded from backups. Yoda has about 703 GB of data on it.
    I recently replaced the hard drive inside my time capsule. Consequently, a full backup was made, which was to be expected.
    When the new full first backup was done, I disconnected the Yoda drive. A day later, I reconnected it, and now Time Machine is saying it's doing a 703 GB backup. Since the size TM indicates its backing up is ever so slightly larger than the total amount of data on Yoda, I'm assuming it's doing a full backup of the Yoda drive for some reason (the only other drive, the system drive, only has about 200 GB on it).
    The files on Yoda weren't changed, certainly not all 703 GB of them. No hardware changes were made, no updates, tinkering, modifications, or anything. The Mac itself has not even been shut down or logged out. The ONLY thing that's happened was the Yoda drive was unmounted and disconnected, then several hours later it was reconnected.
    Why is Time Machine repeating a full backup of this external drive? Is this going to happen every time I disconnect and reconnect the drive? Is there any way to make this not happen, short of excluding the drive (which I don't want to do)?

    After posting this thread, I did find a similar thread (in the "More Like This" section) and saw your responses in it. You had suggested the same thing, as well as doing #A5 if that didn't work.
    I tried #A4 and although that seemed to work in the other thread, unfortunately it didn't work for me. So I moved on to #A5, but I could not get my Time Capsule drive to show up in the Disk Utility. I didn't see a "data folder", but I did try directly dragging the sparsebundle to the left pane of the Disk Utility, but that seemed to hang Disk Utility.
    At this point I'm probably going to try deleting the plist file as per #A4, erasing (reformatting) the drive, rebooting, and starting a whole new backup from scratch. It's not going to take much longer than backing up the entire external drive by itself would have, and I still have older backups (up to a few days ago) on the original Time Capsule drive in case of massive disaster.
    So we'll see how that goes...

  • Best software for doing full backups to ext. hard disk to to be used to restore system

    As a new PC owner I wanted to find out what the best software for doing full backups to external hard disk,  to to be used to restore the system if primary primary disk crashes. Im aware that Windows, Acronis and Paragon all have software that doing varying degress of back and resore functions.

    lasvideo,
    My favorites are ShadowProtect to do an "image backup" of boot drive and Beyond Compare for backing up files for all other "data" arrays. ShadowProtect does not seem to have much market share compared with Ghost and Acronis, but I really love it.
    What I like about ShadowProtect:
    - Extremely fast (complete image backup for 61GB of files on my boot SSD RAID 0 array to a RAID data array takes less than 3 minutes)
    - Can do image backups across a LAN; restores from boot CDROM and USB device
    - Allows for backups from one controller and restore of OS on a different controller and/or RAID configuration (has HAL tools; Hardware ? Layer I think)
    - Can "mount" an image backup as a drive letter and see (and copy) all directories, files, etc. that are contained in the archive
    What I like about Beyond Compare:
    - Can choose what to backup and what to ignore very easily (for example you can set it to ignore certain files or directory names to ignore and then save how you set things up as a "session")
    - Only needs to copy over files that are new or have changed since your last backup
    - Makes it very easy to selectively delete files from your backup
    Regards,
    Jim

Maybe you are looking for