Attempt at Full Backup keeps crashing

When I attempt a full backup through PE8, at the window where its "calculating total media size", the program always stops working,crashes and the adobe crash report window pops up. I don't have any hope adobe will read or help, so here I am. I have no missing files to reconnect. The system info shows my catalog is on my 3rd drive which is where I want it. All the actual photos are stored on my 2nd drive if that makes a diff.

That doesn't make a difference.Please verify that the place where you are taking the backup has enough space.

Similar Messages

Backup keeps crashing with Snow Leopard

Anyone still using Backup, the Apple program, to still back up certain smaller files to iDisk? I was until I upgraded to Snow Leopard, and now all of a sudden Backup just crashes every time I try to use it.
I use TIme Machine and that's great for local backups, but insist on backing up important files (like Quicken) to a remote sight in case of a major catastrophe. Any ideas how to back up to iDisk automatically if Backup no longer works?

Hey - I have the same issue with Backup and iPhoto.
I understand what you wrote about Backup's limits - though I can't see any logic in such a limit. Backup needs to look at file sizes or dates and transport them to a destination. Regardless of size (?!)
In the case of IPhoto I've made the same mistake and upgradet iDisk, only to find out that Backup 3.1.2 reports a "no space left on the device". As I understand the iPhoto Library folder it's just a fancy look for a 100% regular folder with sub-folders and jpg files.
None of my (single) pictures are >90mb .. so while they take up a lot of space when counted all-in-all, I can't see that as a reason for Backup to reject the upload/transport ?
I realize it would take quite some time to upload my 13Gb picture collection in the first batch, but was counting on Backup to only upload pictures with newer dates in the future. So uploading a couple of hundred mb's once in a while would be very much achievable on a household upstream connection.
My questions:
1. Why upgrade a iDisk to 40+ Gb if Apple have no method of backing up peoples images ? Everybody have digital cameras and if the iPhoto Library folder is percieved as one big file .. then 90mb is a very very unusable limit !
2. Can any of you name a transporter software/ftp thingie that will do as described above ?
3. Can iDisk handle the iPhoto Lib if you manually drag it up ? (just to know if we're only searching for an alternative to Backup 3.1.2. or to iDisk itself)
Thanks in advance
/Bo of Copenhagen
3.

Backup keeps crashing

Hi there!
I have a strange problem with Apple's "Backup"-app which is driving me crazy. Maybe someone can help...
I am using the latest version Backup with the latest version of OS X, plenty of RAM on my MacBook Pro.
I have three different sets of Backup-plans:
no 1 + 2: daily automatic backup of specific files/folders to my MobileMe Disk
no 3: manual backup of my entire user folder to an external HD
no 1 + 2 are working just fine; no 3 keeps chrashing!
Here is what I do:
Once every 4 weeks I connect an external HD to my Mac via firewire 800. I than start the manual backup (no 3) of my user folder. Until february, everything went just fine. Now, however, the backup fails and Backup *unexpectedly quits*.
I thinks that there is still enough free space on the external HD (approx 60 GB); the previous incremental backup files only had a couple of GB each; I found out that Backup crashes at the very end of the backup process, after having nearly completed the writing of the backup file.
I also checked my internal and external HD with the Disk Utility and also repaired the permission; didn't help...
Is there anything else I could try to get the backup process working again?
thanks & best regards
W

Process: Backup [840]
Path: /Applications/Backup.app/Contents/MacOS/Backup
Identifier: com.apple.Backup
Version: 3.1.2 (374)
Build Info: BackupProject-3740000~3
Code Type: X86 (Native)
Parent Process: launchd [117]
Date/Time: 2009-04-20 23:32:52.320 +0200
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x0000000016f2c133
Crashed Thread: 8
Thread 8 Crashed:
0 libSystem.B.dylib 0xffff07ff __memcpy + 95 (cpu_capabilities.h:246)
1 com.apple.Foundation 0x96394777 -[NSArchiver encodeArrayOfObjCType:count:at:] + 455
2 com.apple.Foundation 0x96394545 -[NSArchiver encodeDataObject:] + 149
3 com.apple.Foundation 0x96383fcd encodeObjectold + 189
4 com.apple.Backup 0x00026f5d 0x1000 + 155485
5 com.apple.Foundation 0x96383fcd encodeObjectold + 189
6 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
7 com.apple.Foundation 0x96383fcd encodeObjectold + 189
8 com.apple.Backup 0x00027221 0x1000 + 156193
9 com.apple.Foundation 0x96383fcd encodeObjectold + 189
10 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
11 com.apple.Foundation 0x96383fcd encodeObjectold + 189
12 com.apple.Backup 0x00027221 0x1000 + 156193
13 com.apple.Foundation 0x96383fcd encodeObjectold + 189
14 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
15 com.apple.Foundation 0x96383fcd encodeObjectold + 189
16 com.apple.Backup 0x00027221 0x1000 + 156193
17 com.apple.Foundation 0x96383fcd encodeObjectold + 189
18 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
19 com.apple.Foundation 0x96383fcd encodeObjectold + 189
20 com.apple.Backup 0x00027221 0x1000 + 156193
21 com.apple.Foundation 0x96383fcd encodeObjectold + 189
22 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
23 com.apple.Foundation 0x96383fcd encodeObjectold + 189
24 com.apple.Backup 0x00027221 0x1000 + 156193
25 com.apple.Foundation 0x96383fcd encodeObjectold + 189
26 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
27 com.apple.Foundation 0x96383fcd encodeObjectold + 189
28 com.apple.Backup 0x00027221 0x1000 + 156193
29 com.apple.Foundation 0x96383fcd encodeObjectold + 189
30 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
31 com.apple.Foundation 0x96383fcd encodeObjectold + 189
32 com.apple.Backup 0x00027221 0x1000 + 156193
33 com.apple.Foundation 0x96383fcd encodeObjectold + 189
34 com.apple.Foundation 0x9637cf12 -[NSArray(NSArray) encodeWithCoder:] + 562
35 com.apple.Foundation 0x96383fcd encodeObjectold + 189
36 com.apple.Backup 0x00027221 0x1000 + 156193
37 com.apple.Foundation 0x96383fcd encodeObjectold + 189
38 com.apple.Backup 0x0001076d 0x1000 + 63341
39 com.apple.Foundation 0x96383fcd encodeObjectold + 189
40 com.apple.Backup 0x0000f985 0x1000 + 59781
41 com.apple.Backup 0x0000f193 0x1000 + 57747
42 com.apple.Backup 0x0000ef50 0x1000 + 57168
43 com.apple.Backup 0x00061f89 0x1000 + 397193
44 com.apple.Backup 0x0004c9b9 0x1000 + 309689
45 com.apple.Backup 0x00095a0e 0x1000 + 608782
46 com.apple.Backup 0x0009f7df 0x1000 + 649183
47 com.apple.Backup 0x0004d963 0x1000 + 313699
48 com.apple.Backup 0x000bd6bb 0x1000 + 771771
49 com.apple.Backup 0x000bd79a 0x1000 + 771994
50 com.apple.Backup 0x0004d94b 0x1000 + 313675
51 com.apple.Backup 0x00045a96 0x1000 + 281238
52 com.apple.Backup 0x00044c6c 0x1000 + 277612
53 com.apple.Backup 0x0005b4b2 0x1000 + 369842
54 com.apple.Backup 0x0005b0cb 0x1000 + 368843
55 com.apple.Foundation 0x9633a7ed -[NSThread main] + 45
56 com.apple.Foundation 0x9633a394 _NSThread__main_ + 308
57 libSystem.B.dylib 0x93cfa095 pthreadstart + 321
58 libSystem.B.dylib 0x93cf9f52 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x93cc9226 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x93cfb1ef pthread_condwait + 1244
2 libSystem.B.dylib 0x93cfca73 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x9638075c -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x96380570 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.Foundation 0x963804d5 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.Backup 0x0005a4e1 0x1000 + 365793
7 com.apple.Backup 0x0005b472 0x1000 + 369778
8 com.apple.Backup 0x0005b0cb 0x1000 + 368843
9 com.apple.Foundation 0x9633a7ed -[NSThread main] + 45
10 com.apple.Foundation 0x9633a394 _NSThread__main_ + 308
11 libSystem.B.dylib 0x93cfa095 pthreadstart + 321
12 libSystem.B.dylib 0x93cf9f52 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x93cc9226 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x93cfb1ef pthread_condwait + 1244
2 libSystem.B.dylib 0x93cfca73 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x9638075c -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x96380570 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.Foundation 0x963804d5 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.Backup 0x0005a4e1 0x1000 + 365793
7 com.apple.Backup 0x0005b472 0x1000 + 369778
8 com.apple.Backup 0x0005b0cb 0x1000 + 368843
9 com.apple.Foundation 0x9633a7ed -[NSThread main] + 45
10 com.apple.Foundation 0x9633a394 _NSThread__main_ + 308
11 libSystem.B.dylib 0x93cfa095 pthreadstart + 321
12 libSystem.B.dylib 0x93cf9f52 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x93cc9226 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x93cfb1ef pthread_condwait + 1244
2 libSystem.B.dylib 0x93cfca73 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x9638075c -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x96380570 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.Foundation 0x963804d5 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.Backup 0x0005a4e1 0x1000 + 365793
7 com.apple.Backup 0x0005b472 0x1000 + 369778
8 com.apple.Backup 0x0005b0cb 0x1000 + 368843
9 com.apple.Foundation 0x9633a7ed -[NSThread main] + 45
10 com.apple.Foundation 0x9633a394 _NSThread__main_ + 308
11 libSystem.B.dylib 0x93cfa095 pthreadstart + 321
12 libSystem.B.dylib 0x93cf9f52 thread_start + 34
Thread 8 crashed with X86 Thread State (32-bit):
eax: 0xffff0704 ebx: 0x963945bb ecx: 0x00010154 edx: 0x0000000d
edi: 0x16f2c133 esi: 0x7f6d8001 ebp: 0xb04e4728 esp: 0xb04e4720
ss: 0x0000001f efl: 0x00010202 eip: 0xffff07ff cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x16f2c133

Photoshop keeps crashing...saying an attempt was made to load a program with incorrect format. Can anyone help?

photoshop keeps crashing...saying an attempt was made to load a program with incorrect format. Can anyone help?

You can
Supply pertinent information for quicker answers
The more information you supply about your situation, the better equipped other community members will be to answer. Consider including the following in your question:
Adobe product and version number
Operating system and version number
The full text of any error message(s)
What you were doing when the problem occurred
Screenshots of the problem
Computer hardware, such as CPU; GPU; amount of RAM; etc.

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!

Amount being backed up by Time Machine keeps growing during full backup

After some problems with Time Machine backup, I removed a bunch of stuff from my internal hard drive, reformatted my external HD used for backups, and started a new full backup. Time Machine has been running for about 24 hours and gives me a status of Backing up: xx GB of yy GB. Both xx and yy keep growing (apace) so that I don't believe xx will ever equal yy.
To cryptic? Here are real numbers. My internal disk being backed up contains 469.39 GB. Backup status now says Backing up: 685.78GB of 754.42 GB. Both numbers just keep growing. What's going on here? I'm happy to let Time Machine overnight (again) but, really, this can't be normal.

Start up in Recovery mode, launch Disk Utility, select the startup volume ("Macintosh HD," unless you gave it a different name), and run Repair Disk (not Repair Permissions.) If any problems are found, repeat. Then restart as usual.
If you don't already have a current backup, you must back up your data before you take the above step. You may be able to back up, even if the system isn't fully functional. Ask if you need guidance.
Directory corruption in a MacOS journaled volume is always the result of a drive malfunction. It's not caused by power failures, system crashes, or anything else. You might choose to tolerate such a malfunction once in the life of a drive. If it's repeated, the drive must be replaced, or there is some other hardware fault that needs to be corrected. Ignoring repeated directory errors will result in data loss.

Need to backup and remove photo library form my iphone. This library was previously backup on a hard drive that crashed. So these photos are only in the photo library and not in the camera roll. If I do a full backup, it only takes the camera roll.

Need to backup and remove photo library from my iphone. This library was previously backup on a hard drive that crashed. So these photos are only in the photo library and not in the camera roll. If I do a full backup, it only takes the camera roll.
So this is a 2 part question:
1) how to I backup the Photo Library to my new hard drive (as the last one was unrecoverable but previously backed up)
2) how do I remove the Photo Library form my phone (preferably after backup in item 1)
Thanks, Janis

Since it has always been very basic to backup your computer and all it's data, Apple provides no way for you to transfer music from your iPhone back to your computer. As you know, you can re-download all iTunes purchases, but music that you ripped yourself you'll have to just re-rip again.
You can try and find 3rd party applications that might help you. I'm sure you'll pay, however.
Let this be a very important lesson learned.
Best.

My Laptop crashed. I had a full backup on Carbonite so the iTunes folder is there and downloadable. Is there any way just to import that and have iTunes on my new computer (Windows 7) recognize it?

My Laptop crashed. I had a full backup on Carbonite so the iTunes folder is there and downloadable. Is there any way just to import that and have iTunes on my new computer (Windows 7) recognize it?

Nothing gets imported. Simply restore the ENTIRE iTunes folder to the new/restored computer.
Download and install iTunes from Apple's website.
The first time iTunes is launched, assuming the ENTIRE iTunes folder is restored to the correct location, it will launch and be exactly as it was prior to the comptuer issues. If for some reason this does not work, close iTunes, hold the SHIFT key while launching iTunes and a prompt will appear to choose or create a new iTunes library. At this point simply point iTunes to the correct location for the existing iTunes library.

Elements 10 full backup crashes computer @ ~70%

I am running Elements 10 on Windows 7. I am trying to do a full backup of a catelog and it crashes my computer somewhere between 60 and 80% complete. I left the computer overnight so it isn't just "taking a long time".
I have successfully done backups in the past using Elements 10 backup on this computer.
Tried it to the local drive as well as a USB Drive. Nothing else running at the time. Done a catalog repair (no errors found) as well as an optimization.
Elements 10 was the first version I had so shouldn't be a catalog conversion issue.
Any ideas?
Thanks.

Did you tried on the different locations of the hard drive, sometimes in the specific location there is a limited perssimison issue.
Also, check if you have any videos on your catalog, if so please try to move them into a different catalog and try only with images.
Harshit

HT1766 I backed up to my PC and attempted restore but I keep getting an error message that "iTunes could not restore the iPhone because not enough free space is available." I have a 32GB iPhone; only 13GB used!!! HELP! iCloud backup/restore did not work

I backed up to my PC and attempted restore but I keep getting an error message that "iTunes could not restore the iPhone because not enough free space is available." I have a 32GB iPhone; only 13GB used!!! HELP! iCloud backup/restore did not work either! How can I resolve this problem to restore from back up.

If you're not a developer then you really should not have upgraded.
I'm unsure how you can fix this as you have already done a back-up on iOS 7 and apple don't support firmware downgrades.

Word keeps crashing when I attempt to open an .docx email attachment, how do I fix this?

Word keeps crashing when I attempt to open an .docx email attachment, how to I stop word from crashing and be able to open the file?

Since Word is a Microsoft product, you might have better luck of getting an answer over on the Microsoft forum.

Time machine keeps performing full backup to my new time capsule

After years of perfect time machine function to a local usb drive, I bought a time capsule and reconfigured time machine to backup there for my wife's macbook air and my macbook pro.
The macbook air time machine is running perfectly. However after a week or so the time machine on my macbook pro has repeatedly performed a full backup and lost all the backup history. I clearly cannot keep on like this and find it very worrying that this piece of technology, even if it loses connection for some reason, is not robust enough to recover the incremental backup?
Is this a weakness of time machine design? or is there something obvious I need to check?

try if this user tip helps.

Keeping ARCH and Deleting FULL backups on RMAN

Dear all,
RMAN deletes all my full backup and archivelogs in 2 days with;
DELETE NOPROMPT OBSOLETE RECOVERY WINDOW OF 2 DAYS;
But I want to keep archivelogs at least 9 DAYS and delete just the FULL backups after 2 DAYS. How can i set this?
Any recommendations?
Regards

You reported the Sybrand's post as an "abuse to consider" to the mod. Not to take a part or the other, but Sybrand made several points you should yourself to consider up front :
1. you claimed your problem as an emergency case, it is considered as rude in a public forum based on volunteers.
2. also you did not provided any information which can make difference, as the minimum of Oracle version (and OS...), for one who want to be considered as an emergency, that's rather strange, no one here is sitting next to you
3. Sybrand gave you a command to run that you should see the suggestion resulted
4. He also made a point about the documentation, whether it can appears rude to you, it's always, ALWAYS, good to show exactly to your peers what you have done so far to solve your problem, based on what docs...
5. We could also point you a link such as How to ask question
Please, keep it in mind, and come down.
Nicolas (moderator).
PS: without saying that 2 mods spent their time to proceed with your faulty reported abuse case
Message was edited by: Nicolas.Gasparotto

Rman full backup, crash and full restore?

Hi,
I try to implement a simple backup and restore process with rman. Ok, with rman it's not simple. ;-)
My aim is to backup a database with a full backup and restore it from this backup, for example when it crashes.
Ok, for creating the backup I use this rman script:
run
allocate channel t1 type disk;
backup incremental level 0 format 'PATHTOBAKFILE' database;
release channel t1;
The result is a 1GB large backupfile.
Now I delete the whole database and create a new one to simulate a crash.
After this is done, I want to restore the state of the database which is frozen in the backupfile.
Therefor I use the following rman script:
run
allocate channel t1 type disk format 'PATHTOBACKUPFILE';
shutdown immediate;
startup mount;
restore database;
recover database;
alter database open resetlogs;
release channel t1;
Now rman tells me an error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei restore Befehl auf 04/09/2008 10:24:59
RMAN-06026: Einige Ziele nicht gefunden - Recovery wird abgebrochen
RMAN-06023: Kein Backup bzw. keine Kopie der Datendatei 4 zum Wiederherstellen gefunden
RMAN-06023: Kein Backup bzw. keine Kopie der Datendatei 3 zum Wiederherstellen gefunden
RMAN-06023: Kein Backup bzw. keine Kopie der Datendatei 2 zum Wiederherstellen gefunden
RMAN-06023: Kein Backup bzw. keine Kopie der Datendatei 1 zum Wiederherstellen gefunden
In english: No backup or copy of datafile X where found for restore.
I think the backup/restore possibilities with rman are very complex and I don't exactly understand which is the right backup strategie. I'm not an oracle specialist. Maybe someone can give me a hint.
My program should backup the database full, differential and incremental and also restore only by using the given backupfiles. So I want somethink like Point-In-Time recovery, but rman should use the time-point of the given backupfile. And this backupfiles are stored outside oracle, e.g. on a server or somethink like this.
Thanks a lot for help.
Best regards,
Ronny

RMAN> run
2> {
3> allocate channel t1 type disk;
4> backup incremental level 0 format 'PATHTOBAKFILE.%d.%u.P%p.C%c' current contr
olfile database;
5> release channel t1;
6> }
released channel: ORA_DISK_1
allocated channel: t1
channel t1: sid=160 devtype=DISK
Starting backup at 09-APR-08
channel t1: starting incremental level 0 datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF
channel t1: starting piece 1 at 09-APR-08
channel t1: finished piece 1 at 09-APR-08
piece handle=C:\WINDOWS\SYSTEM32\PATHTOBAKFILE.ORCL.0TJDDSC1.P1.C1 comment=NONE
channel t1: backup set complete, elapsed time: 00:01:05
channel t1: starting incremental level 0 datafile backupset
channel t1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel t1: starting piece 1 at 09-APR-08
channel t1: finished piece 1 at 09-APR-08
piece handle=C:\WINDOWS\SYSTEM32\PATHTOBAKFILE.ORCL.0UJDDSE2.P1.C1 comment=NONE
channel t1: backup set complete, elapsed time: 00:00:05
channel t1: starting incremental level 0 datafile backupset
channel t1: specifying datafile(s) in backupset
including current controlfile in backupset
channel t1: starting piece 1 at 09-APR-08
channel t1: finished piece 1 at 09-APR-08
piece handle=C:\WINDOWS\SYSTEM32\PATHTOBAKFILE.ORCL.0VJDDSE7.P1.C1 comment=NONE
channel t1: backup set complete, elapsed time: 00:00:02
Finished backup at 09-APR-08
released channel: t1
RMAN> list backup of controlfile
2> ;
ORACLE error from target database:
ORA-19922: there is no parent row with id 0 and level 0
ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 5035
ORA-06512: at line 1
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT row
s
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
18      Incr 0 2M         DISK        00:00:02     09-APR-08
        BP Key: 18   Status: AVAILABLE Compressed: NO Tag: TAG20080409T214537
        Piece Name: C:\WINDOWS\SYSTEM32\PATHTOBAKFILE.ORCL.0UJDDSE2.P1.C1
Controlfile Included: Ckp SCN: 337949       Ckp time: 09-APR-08
BS Key Type LV Size       Device Type Elapsed Time Completion Time
19      Incr 0 2M         DISK        00:00:01     09-APR-08
        BP Key: 19   Status: AVAILABLE Compressed: NO Tag: TAG20080409T214537
        Piece Name: C:\WINDOWS\SYSTEM32\PATHTOBAKFILE.ORCL.0VJDDSE7.P1.C1
Controlfile Included: Ckp SCN: 337950       Ckp time: 09-APR-08
RMAN> run
2> {
3> allocate channel t1 type disk format 'PATHTOBAKFILE.ORCL.0VJDDSE7.P1.C1';
4> shutdown immediate;
5> startup nomount;
6> restore controlfile from 'PATHTOBAKFILE.ORCL.0VJDDSE7.P1.C1';
7> startup mount;
8> restore database;
9> recover database;
10> shutdown normal;
11> startup;
12> release channel t1;
13> }
released channel: ORA_DISK_1
allocated channel: t1
channel t1: sid=160 devtype=DISK
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
Total System Global Area     171966464 bytes
Fixed Size                      787988 bytes
Variable Size                145488364 bytes
Database Buffers              25165824 bytes
Redo Buffers                    524288 bytes
Starting restore at 09-APR-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=160 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL01.CTL
output filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL02.CTL
output filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL03.CTL
Finished restore at 09-APR-08
database is already started
database mounted
ORACLE error from target database:
ORA-19922: there is no parent row with id 0 and level 0
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 5038
ORA-06512: at line 1
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT row
s
Starting restore at 09-APR-08
Starting implicit crosscheck backup at 09-APR-08
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=160 devtype=DISK
Crosschecked 2 objects
Finished implicit crosscheck backup at 09-APR-08
Starting implicit crosscheck copy at 09-APR-08
using channel ORA_DISK_1
Finished implicit crosscheck copy at 09-APR-08
searching for all files in the recovery area
cataloging files...
cataloging done
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSTEM01.DBF
restoring datafile 00002 to C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF
restoring datafile 00003 to C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSAUX01.DBF
restoring datafile 00004 to C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\WINDOWS\SYSTEM32\PATHTOBAKFILE.ORCL.0TJDDSC1.P1.C1 tag=TAG200804
09T214537
channel ORA_DISK_1: restore complete
Finished restore at 09-APR-08
Starting recover at 09-APR-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 1 is already on disk as file C:\ORACLE\PRODUCT\10.
1.0\ORADATA\ORCL\REDO02.LOG
archive log filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO02.LOG thread=1 s
equence=1
media recovery complete
Finished recover at 09-APR-08
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 04/09/2008 21:53:03
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
open database with resetlogs instead startup
RMAN>Khurram

Constantly attempting Full Backup

Time capsule is constantly attempting full backup.
Full backup completed on startup.
I allowed it to complete a second full backup but as soon as that finished started again.
2TB machine 500 Gb to backup 1 iMac using Lion..
Any ideas appreciated

See #D7 in Time Machine - Troubleshooting.

Attempt at Full Backup keeps crashing

Similar Messages

Maybe you are looking for