Archived log application to a cold backup fails with ora-00328

I am testing backup and recovery scenario as mentioned in Metalink Doc id:69468.1 where a cold backup of one production server is restored on a separate machine. Some activity, say a table creation in some schema and insertion of rows in it is followed by a few log switches. Next I moved just the archived logs ( newly generated) to the test machine and proceed as follow to recover but log application is failing as below,any help would be appreciated!
SQL> startup mount;
ORACLE instance started.
Total System Global Area 205520896 bytes
Fixed Size 1248116 bytes
Variable Size 71304332 bytes
Database Buffers 130023424 bytes
Redo Buffers 2945024 bytes
Database mounted.
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581541, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
Please Help

The error displayed stated you are required to have an specific sequence:
ORA-00280: change 581754 for thread 1 is in sequence #1
Check the contents of the v$recover_file dynamic view and verify if you really have all required archivelog files.
~ Madrid

Similar Messages

Clone from hot backup failing with ORA-19870, 19505 unable to find backup

Ok, the steps I am taking worked previously, the only thing that I know changed was the underlying file system and I am perplexed but then again I am not the most experienced dba so please forgive if I miss something obvious.
My steps are: create backup using:
backup database tag= tagname format '/archive/stage/DBNAME/%U';
backup archivelog all format '/archive/stage/DBNAME/%U';
backup current controlfile '/archive/stage/DBNAME/%U';
Then on the new server, I copy the files over to the new server and:
connect target username@prod
connect auxillary
set until time
duplicate target database to "PRODSBX"
etc...
The problem is the duplicate is not looking at my '/archive/stage/DBNAME' directory for the backup. It's looking in the normal backup directory on that prod box that it can't connect to... can anyone give me clues as to what I should be looking at to figure out why? I looked at file permissions in case it couldn't access this directory, I looked at id, group etc... and I am not seeing anything. These exact same scripts worked before... the only thing I have edited is the set until time so I just can't figure out why it's not going to the /archive/stage.
Any light shed in my general direction would be greatly appreciated.
Thanks!
Va.

I have no way to copy the output of the files as this is on a closed network. If there is any particular information you are looking for I'd be happy to post it.
The restore is looking for the default backup location as specified in my rman configuration but in my backup script, I specify a different location that I do the hot backup to. The first time it took this location and successfully cloned to the new server and now it seems to be ignoring it. I am not sure why, any suggestions in what I should look at, if this is a possible configuration issue on my clone server or on my primary?
Thanks,
Va.

RMAN backup failes with ORA-19624 occurred during call to DBMS_BACKUP_RESTO

RMAN backup up failes with following errors. It works some times and then failes. When it failes then if i un install and reinstall Oralec agent and Backup cliet then it start working OK for few days and then again start getting error. See the messages below...
Recovery Manager: Release 8.1.7.0.0 - Production
RMAN-06005: connected to target database: MIMSDEVH (DBID=3525230908)
RMAN-06008: connected to recovery catalog database
RMAN> RUN { 2> execute script tapelevel0; 3> }
RMAN-03021: executing script: tapelevel0
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script tapelevel0
RMAN-03007: retryable error occurred during execution of command: allocate
RMAN-07004: unhandled exception during command execution on channel ch00
RMAN-10035: exception raised in RPC: ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-19557: device error, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-19511: SBT error = 4110, errno = 0, BACKUP_DIR environment variable is not set
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.DEVICEALLOCATE
Send me some solution...

hi,
what is your backup script
can you post back the result of the command
show all;
from the rman command prompt
regards
Alan

Export backup failing with ORA-1555snapshot too old: rollback segment ERROR

DB version =8.1.7.4
OS=Solaris =5.10.
I know this is outdated. But still we are supporting this version of database.
We are facing ORA-1555 error daily when we are running the export backup of database. Consistent parameter is set to N .
I needed to know why export uses rollback segments during export operation. even though CONSISTENT parameter is N.
Thanks,
Edited by: ahshivap on Dec 12, 2012 5:19 AM

Hi,
Consistent=y just mean the tables are consistent with each other. Oracle still has to guarantee that each individual table is at least consistent with itself. That's your issue.
Regards,
Harry

Any way to undo archive log application?

While cloning the target from the source, we were supposed to restore till log sequence x and we restored it till x+1. Is there any way to undo an archive log application till sequence x. Our database version is 10.2.0.2

1) However, Is it possible to flashback the database to a point before the resetlogs in 10g?
If you meant that after doing flashback databse and resetlogs, can you do it for the point past the resetlogs than yes you can.See this.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9011.htm#SQLRF01801
2) Do we have any other options apart from flash back since it is disabled.
Not that which I can think of.If you don't have flashback database,the other option will be to manualy undo the changes.
Aman....

Windows 2008 R2 backup fails with event 521 error code 2155348001

Windows Server 2008 R2 SP1. Hyper-V role installed.
OS on drive C. All VMs stored on Drive D.
I am attempting to run a Bare Metal backup of the host system to a network share.
Drive D is not included in the backup job. I am getting the following error:
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          1/10/2014 11:28:52 PM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      SHAQTUS.scdl.local
Description:
The backup operation that started at '‎2014‎-‎01‎-‎11T04:08:50.683000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event
details for a solution, and then rerun the backup operation once the issue is resolved.
Reviewing event details, as suggested, does not offer any solution.
I have tried the suggested solutions in other similar threads of increasing the timeout value with the registry entry.
This does not work.
I have not tried reregistering the VSS writers manually, as the only links I have found are for server 2003/2008 (not R2) and explicitly state that they won’t work on higher versions of the OS, since they now utilize manifests and the manual procedure could
cause problems for those servers. Haven't found similar procedures for 2008 R2.
I have been able to narrow this down a bit.
A Windows 2008 R2 SP1 server with Hyper-V installed – backup to a network share is successful;
Install the DPM 2012 agent – same backup fails with the 2155348001 error.
We use DPM 2012 to backup VMs, but DPM cannot perform a bare metal backup/restore of server and the 2012 version no longer has the DPMSRT feature.
I prefer to run Bare Metal Backup to a file server share.
Stuck on this one.
Rick

Hi,
The issue is related to DPM, I would suggest you ask for help from DPM forums:
http://social.technet.microsoft.com/Forums/en-US/home?forum=dataprotectionmanager
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Backup Fails with Invalid RECID Error

Hi All,
Please help me to understand Caution -section
below text is from
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
Backup Fails with Invalid RECID Error: Solution 2
This solution is more difficult than solution 1:
To create the control file with SQL*Plus:
   1. Connect to the target database with SQL*Plus. For example, enter:
      % sqlplus 'SYS/oracle@trgt AS SYSDBA'
   2. Mount the database if it is not already mounted:
      SQL> ALTER DATABASE MOUNT;
   3. Back up the control file to a trace file:
      SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
      # The following commands will create a new control file and use it
      # to open the database.
      # Data used by the recovery manager will be lost. Additional logs may
      # be required for media recovery of offline data files. Use this
      # only if the current version of all online logs are available.
      STARTUP NOMOUNT
      CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG
      -- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
          MAXLOGFILES 32
          MAXLOGMEMBERS 2
          MAXDATAFILES 32
          MAXINSTANCES 1
          MAXLOGHISTORY 226
      LOGFILE
        GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M,
        GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M,
        GROUP 3 '/oracle/oradata/trgt/redo03.log' SIZE 500K
      -- STANDBY LOGFILE
      DATAFILE
        '/oracle/oradata/trgt/system01.dbf',
        '/oracle/oradata/trgt/undotbs01.dbf',
        '/oracle/oradata/trgt/cwmlite01.dbf',
        '/oracle/oradata/trgt/drsys01.dbf',
        '/oracle/oradata/trgt/example01.dbf',
        '/oracle/oradata/trgt/indx01.dbf',
        '/oracle/oradata/trgt/tools01.dbf',
        '/oracle/oradata/trgt/users01.dbf'
      CHARACTER SET WE8DEC
      # Take files offline to match current control file.
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
      # Configure RMAN configuration record 1
      VARIABLE RECNO NUMBER;
      EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
      DEBUG 255');
      # Recovery is required if any of the datafiles are restored backups,
      # or if the last shutdown was not normal or immediate.
      RECOVER DATABASE
      # All logs need archiving and a log switch is needed.
      ALTER SYSTEM ARCHIVE LOG ALL;
      # Database can now be opened normally.
      ALTER DATABASE OPEN;
      # Commands to add tempfiles to temporary tablespaces.
      # Online tempfiles have complete space information.
      # Other tempfiles may require adjustment.
      ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
      # End of tempfile additions.
   5. Shut down the database:
      SHUTDOWN IMMEDIATE
   6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
      STARTUP NOMOUNT
      CREATE CONTROLFILE ...;
      EXECUTE ...;
      RECOVER DATABASE
      ALTER SYSTEM ARCHIVE LOG CURRENT;
      ALTER DATABASE OPEN ...;
Caution:
      If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.

Please help me to understand Caution -section
Caution:
If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
Rgds.

Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

Hello all,
Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
Time Capsule won't backup if Modem (Motorola SB6121) attached
This was on Feb 10th resolved. Few days later I upgraded to Yosemite. Backups were working fine since.
Yesterday I happen to notice my last backup was 5 days ago. I looked in the console logs and saw:
2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
I called Apple. Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
But the next hour it failed
Called Apple again, this time to Sr Advisor. He suggested factory reset of the TC and set up again. Also first backup worked then rest failed
Third call to Apple useless also. He was asking questions I didn't feel relevant. He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
I begged him to collect data to submit to engineering, which will take days to get a reply.
So I thought I would throw this out to the community....
TC Is NEW (replaced from last issue). Mac is 8 months old (iMac 27"), Os is Yosemite, TC also new (latest model)
Thanks...

Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

Backup fails with System writer error

Hi,
We have a networker backup solution in place. Backup fails on one of the windows 2012 server. Event log below. I am not sure how to resolve this issue. Can someone please help?
Log Name:      Application
Source:        VSS
Date:          6/17/2014 5:01:41 PM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ---
Description:
Volume Shadow Copy Service error: Unexpected error calling routine GetVolumeNameForVolumeMountPoint is now failing on the volume, winerror 0x00000005. . hr = 0x80070005, Access is denied.
Operation:
   PrepareForSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {13f27935-f32a-4e30-bdb6-d87894cecf12}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8193</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-06-17T15:01:41.000000000Z" />
    <EventRecordID>4864</EventRecordID>
    <Channel>Application</Channel>
    <Computer>
    <Security />
</System>
<EventData>
    <Data>GetVolumeNameForVolumeMountPoint is now failing on the volume, winerror 0x00000005. </Data>
    <Data>0x80070005, Access is denied.
</Data>
    <Data>
Operation:
   PrepareForSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {13f27935-f32a-4e30-bdb6-d87894cecf12}</Data>
    <Binary>2D20436F64653A20565353415049435030303030313131332D2043616C6C3A20565353415049435030303030313035372D205049443A202030303030303434302D205449443A202030303030313539362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>

Hi,
in my case, I didn't have "System Writer" shown in the Writers list. I tried everything to put it up and running, but without any luck. I even tried re-registering writers, which was a bit risky, but that didn't help either.
Then I have found this hotfix, installed it, and it worked after it.
Anyway, you can find here on technet few topics about this particular issue. For the others, something else worked. Please, take a look:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f4c7fb5b-162a-4c75-994c-b75fbd1dece7/vss-system-writer-is-missing
http://social.technet.microsoft.com/Forums/windowsserver/en-US/4458947a-623e-45c1-b8e4-868aad1e93b0/missing-vss-system-writer-and-capi2-error-in-event-log?forum=winserverfiles
https://kb.acronis.com/content/45776#Win2008 - pay attention what is for 2003 and what for 2008, you can end up with broken system
http://social.technet.microsoft.com/Forums/windowsserver/en-US/764791ff-ecb5-4716-9f1c-9e22852e0f6b/resolved-backup-failing-on-server-2008-r2-system-writer-missing?forum=windowsbackup
http://social.technet.microsoft.com/wiki/contents/articles/7309.backup-fails-with-error-message-writer-missing-or-failed-or-timed-out-or-waiting-for-completion-in-vssadmin.aspx
You can try all of this (I did), but this hotfix saved my day in the end.
Hope this helps.
If this helped you resolve your issue, please mark it Answered, thanks! Kind regards

What to do about Backup failed with error: The target volume is read-only

This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

Pondini wrote:
odysseus wrote:
This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
I've tried this before, but it can't be repaired, because it can't be mounted.
Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
I'm backing up to my own sparseimage bundle just fine.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
That checks out fine.
if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

Time Machine backup fails with error 2

trying to run a backup for the first time on a new external hard-drive but backup fails to complete. Any suggestions?
Starting standard backup
Backing up to: /Volumes/FreeAgent GoFlex Drive/Backups.backupdb
Failed to create progress log file at path:/Volumes/FreeAgent GoFlex Drive/Backups.backupdb/Jones’s iMac (3)/2011-11-24-170759.inProgress/.Backup.343882684.814583.log.
Event store UUIDs don't match for volume: Macintosh HD
Error: (-50) Creating directory 6A3DF5C4-679A-4FBE-A116-218CE389908A
Failed to make snapshot.
Backup failed with error: 2

I too am having multiple problems with time machine for a couple of weeks now, however this is not my first backup. I have been using TM for over 2 years, and these are new problems. This is the last error message:
Starting standard backup
Backing up to: /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb
Failed to create progress log file at path:/Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/.Backup.344169198.317667.log.
Event store UUIDs don't match for volume: Mac 2
Event store UUIDs don't match for volume: Mac 1
Error: (-50) Creating directory 0A89DB49-A127-4ECE-8E98-65C5393BC268
Failed to make snapshot.
Backup failed with error: 2
The above came after permissions repair & disk repair. Before the messages were mostly:
Error: (-50) SrcErr:NO Copying /Applications/Font Book.app to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/E0326568-C860-4A3F-888D-9840DFF72832/Mac 1/Applications
Error: (-50) SrcErr:NO Copying /Applications/Front Row.app to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/E0326568-C860-4A3F-888D-9840DFF72832/Mac 1/Applications
Error: (-50) SrcErr:NO Copying /Applications/Full Key Codes to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-
With a whole string of different applications with the same error, then ending with:
Error: (-43) SrcErr:NO Copying /User Guides And Information to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-1407) SrcErr:NO Copying /Users to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-43) SrcErr:NO Copying /usr to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-1407) SrcErr:NO Copying /Volumes to (null)
Formulating crash report for process backupd[960]
Any help/suggestions out there ??

TM Backup failed with error: 11 - when copying Movie, image, music files

TM giving backup errors (for a long time unsolved until I read forum entry about monitoring events with Console prog.) Recently upgraded from 10.5.4 to 10.5.6 with Combo package (attempts at upgrade to 10.5.5 failed with "unknown error")
I narrowed down to the file types listed by excluding relevant erring folders. TM backup works OK now but without Movies, Photos, Music and small number of applications that appear to fail mainly on copying an image within appl.
Using Console with "backupd" filter on LOG FILES/system.log (while executing TM backup) gives the following 4 samples of errors:
1. Dec 21 02:20:03 Macintosh /System/Library/CoreServices/backupd[1627]: Starting standard backup
Dec 21 02:20:05 Macintosh /System/Library/CoreServices/backupd[1627]: Backing up to: /Volumes/MacBook Backup/Backups.backupdb
Dec 21 02:20:06 Macintosh /System/Library/CoreServices/backupd[1627]: Event store UUIDs don't match for volume: Macintosh HD
Dec 21 02:20:06 Macintosh /System/Library/CoreServices/backupd[1627]: No pre-backup thinning needed: 64.44 GB requested (including padding), 129.33 GB available
Dec 21 02:22:31 Macintosh /System/Library/CoreServices/backupd[1627]: Error: (-36) SrcErr:YES Copying /Users/xxxxx/Movies/iMovie Events.localized/New Event 07-04-2008 2/clip-2008-04-07 11;30;45.mov to (null)
Dec 21 02:22:32 Macintosh /System/Library/CoreServices/backupd[1627]: Error: (-36) SrcErr:NO Copying /Users/xxxxx/Movies/iMovie Events.localized/New Event 07-04-2008 2/clip-2008-04-07 11;30;45.mov to /Volumes/MacBook Backup/Backups.backupdb/............
2. Dec 21 02:25:23 Macintosh /System/Library/CoreServices/backupd[1627]: Starting standard backup
Dec 21 02:25:23 Macintosh /System/Library/CoreServices/backupd[1627]: Backing up to: /Volumes/MacBook Backup/Backups.backupdb
Dec 21 02:25:24 Macintosh /System/Library/CoreServices/backupd[1627]: Event store UUIDs don't match for volume: Macintosh HD
Dec 21 02:25:24 Macintosh /System/Library/CoreServices/backupd[1627]: No pre-backup thinning needed: 64.44 GB requested (including padding), 126.79 GB available
Dec 21 02:27:46 Macintosh /System/Library/CoreServices/backupd[1627]: Error: (-36) SrcErr:YES Copying /Users/xxxxx/Music/iTunes/iTunes Music/Duck Baker, Maggie Boyle and Ben Paley/The Expatriate Game--Traditional Irish & American Music/07 Rye Whiskey.m4a to (null)
3.Dec 21 13:17:28 Macintosh /System/Library/CoreServices/backupd[1768]: No pre-backup thinning needed: 6.26 GB requested (including padding), 120.05 GB available
Dec 21 13:21:11 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/StockXloader.app/Contents/Resources/StockXloaderName.tif to (null)
Dec 21 13:22:03 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/MacOS/Stox to (null)
Dec 21 13:22:31 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image002.png to (null)
Dec 21 13:23:07 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image033.png to (null)
Dec 21 13:23:31 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image060.png to (null)
Dec 21 13:24:09 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image120.png to (null)
Dec 21 13:27:29 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/MacOS/EyeTV to (null)
Dec 21 13:27:53 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/authopen to (null)
Dec 21 13:28:17 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/Device Pictures/CinergyDTXS.png to (null)
Dec 21 13:28:42 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/Device Pictures/CinergyTExpress.fscaled.png to (null)
Dec 21 13:29:07 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/Device Pictures/ElgatoDiversity.fscaled.png to (null)
4. Dec 21 14:44:46 Macintosh /System/Library/CoreServices/backupd[1858]: Starting standard backup
Dec 21 14:44:48 Macintosh /System/Library/CoreServices/backupd[1858]: Backing up to: /Volumes/MacBook Backup/Backups.backupdb
Dec 21 14:45:50 Macintosh /System/Library/CoreServices/backupd[1858]: No pre-backup thinning needed: 2.11 GB requested (including padding), 116.67 GB available
Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Error: (-36) SrcErr:YES Copying /Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A/BGComp atibility to (null)
Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Error: (-36) SrcErr:NO Copying /Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A/BGComp atibility to /Volumes/MacBook Backup/Backups.backupdb/xxxxxxx’s MacBook/2008-12-21-131514.inProgress/58F99FC2-7474-42C9-8DCA-5C99F724CE6E/Macin tosh HD/Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A
Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Stopping backup.
Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Error: (-8062) SrcErr:NO Copying /Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A/BGComp atibility to /Volumes/MacBook Backup/Backups.backupdb/xxxxxx’s MacBook/2008-12-21-131514.inProgress/58F99FC2-7474-42C9-8DCA-5C99F724CE6E/Macin tosh HD/Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A
Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Copied 52 files (26.7 MB) from volume Macintosh HD.
Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Copy stage failed with error:11
Dec 21 14:46:24 Macintosh /System/Library/CoreServices/backupd[1858]: Backup failed with error: 11

solongpc wrote:
Regardless if this is a general problem or not, does anyone know of any documentation/release notes for common/generic TM error codes? That would be helpful.
Yeah, many of us would love it! But no such thing exists, at least not that us mere mortals can find.
There might be another variable that I don't understand right now but at least it is consistent.
Could it be something funky in the name of one of the folders? Or could the folder object itself be corrupt? Or have some odd extended attribute?
All I can suggest is calling AppleCare, and/or reporting it as a bug:
*_Submitting a +Bug Report+ to Apple._*
|
This requires a membership in the +Apple Developer Connection,+ but you can get one for free.
Register here: http://developer.apple.com/programs/start/register/create.php
Once you receive the confirmation, go to: https://bugreport.apple.com and login.
Click +New Problem+ at the top.
Click Help at the top, and/or any of the items underlined in blue for more information.
Provide as much specific detail as possible, and attach a log, screenshot, etc., as appropriate in the lower section.
When done, click Submit at the bottom.

Windows Server 2008 R2 Backup failing with error - 0x8004231F

Hi,
I have Windows Server 2008 R2 Web Edition. Everything was working fine until recently. I tried checking for the log files, but I see that there are no log files that are created now in the location C:\Windows\Logs\WindowsServerBackup. The only files that
are being created recently are of the type mentioned below.
Wbadmin.1.etl
WbadminUI.0.etl
etc.
I tried removing the old backup and starting a new backup. But, even now it is failing with the same error.
When running the backup from the PowerShell, the output is as below.
PS C:\Users\administrator> Wbadmin start backup -backupTarget:\\localhost\E$\WindowsImageBackup\Server01 -systemState -vss
Copy
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Note: The backed up data cannot be securely protected at this destination.
Backups stored on a remote shared folder might be accessible by other
people on the network. You should only save your backups to a location
where you trust the other users who have access to the location or on a
network that has additional security precautions in place.
Retrieving volume information...
This will back up volume System Reserved (100.00 MB) (Selected Files),SAN(I:) (Selected Files),Local Disk(C:) (Selected
Files) to \\localhost\E$\WindowsImageBackup\Server01.
Do you want to start the backup operation?
[Y] Yes [N] No y
The backup operation to \\localhost\E$\WindowsImageBackup\Server01 is starting.
Starting to back up the system state [12/8/2013 9:29 AM]...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Summary of the backup operation:
The backup of the system state failed [12/8/2013 9:30 AM].
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-08-12-2013_09-29-49.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-08-12-2013_09-29-49.log
There is not enough disk space to create the volume shadow copy on the storage location. Make sure that, for all volumes
to be backup up, the minimum required disk space for shadow copy creation is available. This applies to both the backup
storage destination and volumes included in the backup.
Minimum requirement: For volumes less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more th
an 500 megabytes, the minimum is 320 megabytes of free space.
Recommended: At least 1 gigabyte of free disk space on each volume if volume size is more than 1 gigabyte.
ERROR - A Volume Shadow Copy Service operation error has
occurred: (0x8004231f)
Insufficient storage available to create either the shadow copy storage file or other shadow copy data.
If you see the free space available in each of the drives, they are in plenty.
C:\ 7.5 GB free of 70 GB
E:\ 250 GB free of 499 GB
I:\ 86.7 GB free of 350 GB
I am out of any hints on how I can proceed now. Has any one had similar issues? Can any one give any hint on this? Thanks.
Thanks.

Some Additional info.
Shadow Copy Storage association
   For volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\)\\?\Volume{a9f
b0474-f1bd-11e0-b235-806e6f6e6963}\
   Shadow Copy Storage volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}
\)\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 32 MB (32%)
Shadow Copy Storage association
   For volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01d1}\
   Shadow Copy Storage volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01
d1}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 35 GB (10%)
Shadow Copy Storage association
   For volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01bd}\
   Shadow Copy Storage volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01
bd}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 149.999 GB (30%)
Shadow Copy Storage association
   For volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e69
63}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 4.99 GB (7%)
Hope this might also help you experts to get a little more information.

Backup failed with Error: (-50) Creating Directory

Repeats ad nauseum.
This is backing up to a second internal drive that is an exact duplicate (in terms of HD model and size).
Does anyone know what Error -50 means? Lack of permissions? Invalid name (doesn't seem like it)?
8/30/08 9:06:37 AM /System/Library/CoreServices/backupd Starting standard backup
8/30/08 9:06:37 AM /System/Library/CoreServices/backupd Backing up to: /Volumes/Sliffy Time/Backups.backupdb
8/30/08 9:06:58 AM /System/Library/CoreServices/backupd Error: (-50) Creating directory 2008-08-30-090658.inProgress
8/30/08 9:06:58 AM /System/Library/CoreServices/backupd Failed to make snapshot container.
8/30/08 9:07:03 AM /System/Library/CoreServices/backupd Backup failed with error: 2

Hi Glenn,
Thanks for the suggestion. Nope, it's not listed. The only thing listed is my Time Machine volume.
After a reboot, Time Machine seems to be working. It's making backups on schedule and the logs look good, not reporting any strangeness.
A bit bummed about these phantom errors that go away on reboot. I'll keep on eye on the error/reboot frequency.
Rob

Backup failed with error: 11 -Error: (-41) SrcErr:NO Copying

Like many of you, I was unlucky to get the famous TimeMachine error message: "The backup was not performed because an error occurred while copying files to the backup disk". I started to get as much help as I could from Google and all your forum posts.
Until recently I could not get an easy answer and it seemed that various people had success by:
- renaming their machine to remove say extraneous characters (such as apostrophe)
- delete the last "in progress" backup
- reset the TM
- etc.
I did all of that plus reformatting my new WD HDD but nothing changed. After 2 days of frustration with this piece of software (Time Machine), the good news for me is that I can consistently reproduce the error as well succeed in performing a backup. The solution for me seems to make sure that I +*do not have a source directory structure deeper than 15 levels*+. As soon as I have a file that is 16 levels deep from the root of the HDD that I try to backup, I get this error:
+*Error: (-41) SrcErr:NO Copying /Volumes/<HDD to Backup>/<Deep Directory Structure>... to*+
+*/Volumes/<Your TM Drive>/Backups.backupdb/<Your Machine>/<Timestamp>.inProgress/<AutoGenerated-GUID>/<HDD to Backup>/<Deep Directory Structure>...*+
+*Copy stage failed with error:11*+
+*Backup failed with error: 11*+
The Console app shows the system log with the path to the file that failed during backup. I tried to make the pathname shorter than 255 characters to make sure this is not an 8bit limitation of some string length in the code. Even if I have a path shorter than 255 characters, TM fails with the above error when the source files are at least 16 levels deep in the directory structure.
What is most frustrating about this is not the careless and uninformative error message or this apparently non-sense limitation of 15 levels - it might be something historical in Apple's code - but the lack of documentation. In the absence of proper logging and error handling in this piece of code, wouldn't be nice to have some explanation from Apple with regards to what this error #11 means or perhaps what caused this "Error (-41) SrcErr:NO Copying"? I guess most of us would be just fine to know that as per release notes, Apple has this limitation of 15 levels for the source directory structure.

solongpc wrote:
Regardless if this is a general problem or not, does anyone know of any documentation/release notes for common/generic TM error codes? That would be helpful.
Yeah, many of us would love it! But no such thing exists, at least not that us mere mortals can find.
There might be another variable that I don't understand right now but at least it is consistent.
Could it be something funky in the name of one of the folders? Or could the folder object itself be corrupt? Or have some odd extended attribute?
All I can suggest is calling AppleCare, and/or reporting it as a bug:
*_Submitting a +Bug Report+ to Apple._*
|
This requires a membership in the +Apple Developer Connection,+ but you can get one for free.
Register here: http://developer.apple.com/programs/start/register/create.php
Once you receive the confirmation, go to: https://bugreport.apple.com and login.
Click +New Problem+ at the top.
Click Help at the top, and/or any of the items underlined in blue for more information.
Provide as much specific detail as possible, and attach a log, screenshot, etc., as appropriate in the lower section.
When done, click Submit at the bottom.

Archived log application to a cold backup fails with ora-00328

Similar Messages

Maybe you are looking for