Monthly Backup Failed!

Dear All,
We're running SAP on oracle 10.2.3 and have outsourced the backups.
this month the backup against the policy failed. while checking the logs I found the following:
BR0051I BRBACKUP 7.00 (36)
BR0055I Start of database backup: begftubc.anf 2011-07-02 10.45.32
BR0484I BRBACKUP log file: F:\oracle\P01\sapbackup\begftubc.anf
BR0280I BRBACKUP time stamp: 2011-07-02 10.45.35
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance P01 failed
BR0280I BRBACKUP time stamp: 2011-07-02 10.45.36
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance P01 failed
BR0056I End of database backup: begftubc.anf 2011-07-02 10.45.36
BR0280I BRBACKUP time stamp: 2011-07-02 10.45.36
BR0054I BRBACKUP terminated with errors
There has been no issues before this and I've not changed any user-id/passwords. Please help.
Regards.
Tejasav Kalra

Hello,
We're running SAP on oracle 10.2.3 and have outsourced the backups.
well, check the release, this one was never supported at all for SAP.
There has been no issues before this and I've not changed any user-id/passwords. Please help.
The OPS$ User does not authenticate with a password at all.
If you did not change anything, there are only a few things left that could have been changed.
First: check that the user still exists and is not locked: >> SELECT * FROM DBA_USERS
Second: check what OS-User is executing your backup command. It needs to fit the OPS$ User
Third: check the Windows group membership of this OS User. This defines, if it has DBA permissions.
Volker
BTW: And there are A LOT of older threads dealing with exactly this problem.
May be we should have a "Solve ORA-1017" thread made sticky in this forum?

Similar Messages

Time Capsule/TM backups work for a month, then fail and corrupt the SB

I have two Powerbook G4s backing up to a time capsule. Both exhibit exactly the same problem. The initial backup (over Ethernet) works fine, as do regular TM backups. After several weeks, however, it starts to take longer and longer for the backups to start. Sometimes 30 minutes or more is required to complete the "Preparing Backup" phase.
Eventually, the backups fail altogether and the SB cannot be mounted ("This volume is corrupted. Please backup your data and reformat").
This behavior renders this software/hardware nearly useless, since every month or so you need to wipe the old backup file and start over again.
If I could make the following suggestions to apple (or perhaps there are ways to accomplish this already?):
1. Allow the user to control the backup frequency. I would much rather have daily backups that actually worked rather than hourly backups that don't.
2. Provide a mechanism for compressing or compacting an exiting SB.
Can anyone suggest any ideas (other than going back to Super Duper, which actually seemed to work) to fix this?

Read C13 in Pondini's troubleshooting. http://www.pondini.org/TM/Troubleshooting.html
Have a nice day.

Recent backups fail: "An error occurred while copying files to the volume."

I recently moved to a new place and set up Time Capsule as a bridge. Backups were working fine for the first couple days but then, out of the blue, I got a message that said the password I entered for Time Capsule was incorrect. I entered the correct password and hit OK. Time Machine was able to connect but now backups fail with this error: "Unable to complete backup. An error occurred while copying files to the backup volume."
Time Machine indicates it is "preparing backup" for a few minutes, then sits at "zero of __MB completed" for a long while, finally starts backing up and gets to the end but then fails. Console indicates "unexpected reply from backup server; ignored."
None of these attempts have fixes my problem:
--I have deleted my TC passwords in Keychain Access.
--I have tried downloading the latest Airport Utility and re-entering the TC disk's password in both Airport Utility and in Time Machine preferences.
--I have restarted my computer and unplugged & plugged back in TC.
My Internet connection works fine; TC's light is solid green. I can enter Time Machine to restore backups without a problem. The backups just fail every time now. Any ideas?

The problem really isn't the speed of the backup; it's done in 5-10 minutes, but each time it finishes, TM reports it has failed. I don't believe plugging it in overnight or letting TM try over and over will fix the problem. I've tried to manually start backups a number of times, and have let TM try to start and complete them on its own but they consistently fail.
It would be an awful shame if I had to delete my old backup--I bought the Time Capsule for the specific purpose of having backups that go back months and I don't want to lose what I've already backed up.

MBP wakes from sleep, TM backup fails

Since updating to 10.5.6, whenever I open my MBP, it immediately begins to try to do a Time Machine update to my Time Capsule. This quickly fails. If I look in System Preferences>Time Capsule, in addition to showing that the backup failed, it shows the next scheduled backup, which comes and goes with no backup. The NEXT backup will usually work. Any suggestions? Thanks in advance.

Thanks, guys. Here is a report log. I removed the gateway address numbers from the log since I am both paranoid and not especially computer savvy. Maybe this was unnecessary.
I have one possible theory of the crime. Months ago, I set up an action in Automator and put it into iCal as a plug-in scheduled to go off at 3 am everyday. It is an action to backup a bunch of files from my local iDisk to another file on my iMac. Now, when I sync by iCal, this plug-in gets synced to my other two computers, and every morning, when I wake them up, I get a little alarm telling me the action could not be completed on those computers. Well, of course, since it is set up to copy files from one place to another on ANOTHER computer. Couldn't figure a way around this, so just kept it, and would click OK on the alarm. Caused no problems for months, and may not be the culprit now. Just thought I'd mention it.
Again, this is not a major issue for me, this TM backup problem, as it does eventually backup. I appreciate whoever goes over this log below. You should really have some of your genes frozen or something for future generations.
Dec 24 07:17:15 Macintosh kernel[0]: hibernatepage_listsetall start
Dec 24 07:17:16 Macintosh kernel[0]: hibernatepage_listsetall time: 155 ms
Dec 24 07:17:16 Macintosh aosnotifyd[164]: Stream:streamCallback - an error occurred on CFReadStream: Operation could not be completed. Socket is not connected
Dec 24 07:17:16 Macintosh kernel[0]: pages 394371, wire 179286, act 99308, inact 15, zf 0, throt 8592, could discard act 68961 inact 30146 purgeable 8063
Dec 24 07:17:16 Macintosh [0x0-0x9009].com.apple.dock[150]: 2008-12-24 07:17:16.214 DashboardClient[361:10b] com.fmr.widget.FidelityMarketMonitor: Fidelity is unable to provide the information that you requested at this time Please retry your request at a later time.
Dec 24 07:17:16 Macintosh kernel[0]: hibernatepage_listsetall found pageCount 287201
Dec 24 07:17:16 Macintosh configd[34]: rtmsg: error writing to routing socket
Dec 24 07:17:16 Macintosh kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
Dec 24 07:17:16 Macintosh /System/Library/CoreServices/backupd[1728]: Starting standard backup
Dec 24 07:17:16 Macintosh DashboardClient[361]: com.fmr.widget.FidelityMarketMonitor: Fidelity is unable to provide the information that you requested at this time Please retry your request at a later time.
Dec 24 07:17:16 Macintosh kernel[0]: IOHibernatePollerOpen(0)
Dec 24 07:17:16 Macintosh kernel[0]: writing 285717 pages
Dec 24 07:17:16 Macintosh kernel[0]: image1Size 479949824
Dec 24 07:17:16 Macintosh kernel[0]: all time: 19070 ms, comp time: 2042 ms, deco time: 0 ms,
Dec 24 07:17:16 Macintosh kernel[0]: image 709969920, uncompressed 1170296832 (285717), compressed 702119024 (59%), sum1 d4a91d71, sum2 f482cab8
Dec 24 07:17:16 Macintosh kernel[0]: hibernatewriteimage done(0)
Dec 24 07:17:16 Macintosh kernel[0]: sleep
Dec 24 07:17:16 Macintosh kernel[0]: Wake reason = EC LID0
Dec 24 07:17:16 Macintosh kernel[0]: System Wake
Dec 24 07:17:16 Macintosh kernel[0]: vmmon: powerStateDidChange flags=0x82 (state 4)
Dec 24 07:17:16 Macintosh kernel[0]: Previous Sleep Cause: 0
Dec 24 07:17:16 Macintosh kernel[0]: EIR is not supported.
Dec 24 07:17:16 Macintosh kernel[0]: AFPSleepWakeHandler: waking up
Dec 24 07:17:16 Macintosh kernel[0]: vmnet: VMNetDisconnect called for port 0xa032200
Dec 24 07:17:16 Macintosh kernel[0]: vmnet: bridge-en1: filter detached
Dec 24 07:17:16 Macintosh kernel[0]: vmnet: bridge-en1: down
Dec 24 07:17:16 Macintosh kernel[0]: vmnet: bridge-en1: detached
Dec 24 07:17:16 Macintosh kernel[0]: vmnet: Freeing hub at 0xa894000.
Dec 24 07:17:17 Macintosh kernel[0]: AirPort: Link Up on en1
Dec 24 07:17:17 Macintosh configd[34]: AppleTalk startup
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x10245700.
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: VMNetConnect: returning port 0x10245700
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: Allocated hub 0xa894000 for hubNum 0.
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:fb:7d:82
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: Hub 0
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: Port 0
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: bridge-en1: got dev 0x5d9d804
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: bridge-en1: wireless interface detected.
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: bridge-en1: up
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: bridge-en1: attached
Dec 24 07:17:20 Macintosh kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x10245700.
Dec 24 07:17:22 Macintosh mDNSResponder[22]: Double NAT (external NAT gateway address (I removed the numbers here) is also a private RFC 1918 address)
Dec 24 07:17:23 Macintosh configd[34]: AppleTalk startup complete
Dec 24 07:17:23 Macintosh /System/Library/CoreServices/backupd[1728]: Backup failed with error: 19

Domain Controller SystemState backup failing on 3 servers

Hi,
I've been puzzling over this for a few weeks - getting a bit desperate now... Seen a few similar issues on the forums, but no definitive answer that works...
I have 3 2012R2 domain controllers - 2 are new, clean build, no AV installed, built in the last month and have latest updates installed.
Windows Server backup installed on all 3 and is failing with same error on all 3 when attempting to do a system state backup.
This is what I'm running from an elevated command prompt...
C:\Windows\system32>wbadmin start systemstatebackup -backuptarget:e:
Also fails exactly the same from the GUI.
Windows Server Backup Log has this error:
Error in backup of C:\Windows\WinSxS\amd64_microsoft-windows-alttab_31bf3856ad364e35_6.3.9600.16384_none_599bb25393087eb6\AltTab.ptxml during read: Error [0x80070005] Access is denied.
I haven't changed any permissions, they are default...
>cacls AltTab.ptxml
...\AltTab.ptxml NT SERVICE\TrustedInstaller:F
              BUILTIN\Administrators:R
              NT AUTHORITY\SYSTEM:R
              BUILTIN\Users:R
              APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:R
In the Event Log I have:
Event 517
The backup operation that started at '‎2015‎-‎01‎-‎05T07:30:13.107907800Z' has failed with following error code '0x80780049' (None of the items included in backup were backed up.). Please review the event details for a solution, and then rerun the backup
operation once the issue is resolved.
Same error is present on all DC's, all 3 are failing on files in the winsxs folder - different files on each.
As per a previous article I read, on one of the servers I have re-applied permissions to the WinSxS folder, which didn't make any difference.
I cannot see any locks on the winsxs files using sys internals process explorer.
Interestingly though, system state backup did work before windows update applied huge amount of updates straight after the build.
At this point, I have no good backups of AD - I have run out of options - all assistance appreciated.
Thanks,
Charles.

OK, this is getting ridiculous.
Built another clean server from latest 2012 R2 iso... en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso
joined domain, backups work, windows update works and installs 24 updates
Promoted to DC, then Windows update and backups fail with
WU...
2015-01-09
14:30:38:735
836
d6c
AU
>>## RESUMED ## AU: Search for updates [CallId = {6DD3D371-4F02-4D34-95FE-B04899E14E92} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
2015-01-09 14:30:38:735
836 d6c
AU # 4 updates detected
2015-01-09 14:30:38:735
836 d6c
AU #########
2015-01-09 14:30:38:735
836 d6c
AU ## END ## AU: Search for updates [CallId = {6DD3D371-4F02-4D34-95FE-B04899E14E92} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
2015-01-09 14:30:38:735
836 d6c
AU #############
2015-01-09 14:30:38:735
836 d6c
AU All AU searches complete.
2015-01-09 14:30:38:735
836 d6c
AU # WARNING: Failed to find updates with error code 80070005
2015-01-09 14:30:38:735
836 d6c
AU AU setting next detection timeout to 2015-01-09 19:30:38
2015-01-09 14:30:38:735
836 d6c
AU Adding timer:
2015-01-09 14:30:38:735
836 d6c
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-01-09 19:30:38, not idle-only, not network-only
2015-01-09 14:30:38:735
836 d6c
AU WARNING: ISusInternal::CanInstallNow failed, error = 0x80070005
Backups failing with:
Error in backup of C:\Windows\WinSxS\amd64_microsoft-windows-alttab_31bf3856ad364e35_6.3.9600.16384_none_599bb25393087eb6\AltTab.ptxml during read: Error [0x80070005] Access is denied.
Any suggestions?
Thanks.

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/

Time Capsule backup failed, volume read-only, can't delete

I've only been using Time Machine and Time Capsule for 2 months. This week it stopped working. First error message:
"Unable to complete backup. An error occurred while copying files to the backup volume."
Checking the Time Machine preferences, "Last backup" would read "backup failed"
When I got this error, all the wireless functions went offline, even thought the TC light was still green.
I would shut down, shut down the Time Capsule, shut off my modem reboot everything in order.
I would come back online, but after about 20 minutes to 1.5 hours into the next backup, same thing would happen again.
Next error message:
"Disk repair. The disk 'Backup of [my computer]' was not repairable by this computer. It is being made available to you with limited functionality. You must backup your data and reformat the drive."
Then: "Time Machine Error: The backup volume is read only. To select a different volume ... Time Machine preferences ... "
I spoke to someone at Apple, who sent me the Time Machine Troubleshooting page:
http://support.apple.com/kb/HT3275?viewlocale=en_US
Steps I went through:
1. updated my system software
2. updated the TC firmware to 7.4.1
3. dragged the sparsebundle to DiskUtility. It took a while (more than an hour?) but said the disk could not be repaired. When I tried again, the repair function wouldn't run.
4. tried to delete the sparsebundle, but it would choke at almost the end, sometimes it would just crash the finder, sometimes say "Sorry, an unexpected error occurred," sometimes "Operation cannot be completed because the item 'bands' is in use." I even tried to Stuff the bundle with 'delete original' checked, but the stuffing, after about 15 hours, jammed near the end (stuffed 20 gigs of 35 gigs).
5. tried to reselect the TC, and run backup anyways ... now it can't find the volume, back to the error messages and crashing Finder
6. checked password in Keychain, all ok.
Now what??
Do I use Airport Utility to erase it? At least TC is still showing up there. Or press the rest button on the back of the Time Capsule to reset to factory defaults?
I've resigned myself to losing my backups. Now I would just like to get it up and running again.
In hopes,
Linda

Now what??
Do I use Airport Utility to erase it? At least TC is still showing up there. Or press the rest button on the back of the Time Capsule to reset to factory defaults?
Yes, open Airport Utility and erase the drive. Once the sparsebundle is corrupted beyond repair there's little more you can do. However, do not reset the TC. Doing so will not erase the drive, but it will remove any custom configurations you may have setup for the router. Only if that part of the TC is also misbehaving should you use the reset button.

Time Capsule backup failed error -43?

Hi and Thanks to Anyone in Advance!
Below is the Time Capsule Error Log I get when doing a Time Machine Backup, wirelessly, on my 2T Time Capsule HD/Router.
Initial Setup and Backup done via ethernet, flawlessly, two months ago. Subsequent backups worked until about three days ago (Why, I have not a clue!)
Often, using Airport Utility, the Time Capsule does not appear. Turning off Computer Airport and on again, the disk becomes magically available for backup. Similar problem with wireless LAN printer...truly a pain. the printer needs to be deleted, and then added again in Print/Fax Preferences. (HP PhotoSmart C7250)
I used Disk Utility" on my Computer HD with a repair permissions, then performed a TC reset, physically, and reconfigured the TC on the LAN, trying a new name "gotyourback" for the backup. Backup begins every time, but keeps failing after about five minutes.
Hope this helps others with similar problem...
Again,
Thanks!
Starting standard backup
Attempting to mount network destination using URL: afp://Suz%20Tim%20Abri%20and%[email protected]/Data
Mounted network destination using URL: afp://Suz%20Tim%20Abri%20and%[email protected]/Data
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Data/Rogers Rocks Home.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102f20b60 "The file “CM” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001c76a0 "The file “std” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001dfc50 "The file “js” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001e06c0 "The file “en” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001e11e0 "The file “disofactor.swf” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001e1320 "The file “diso.sol” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100527ec0 "The file “Download” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
No pre-backup thinning needed: 1.19 GB requested (including padding), 1.38 TB available
Stopping backup.
Error: (-43) SrcErr:NO Copying /Applications/The Learning Company to /Volumes/Time Machine Backups/Backups.backupdb/Rogers Rocks Home/2011-09-08-114311.inProgress/A0EF34AF-A412-4268-B48E-1FD4BF77C8BA/ROGERS LOVE/Applications
Copied 177 files (33.0 MB) from volume ROGERS LOVE.
Copy stage failed with error:11
Backup failed with error: 11
Ejected Time Machine disk image.

Ok, if it is only 2months old it shouldn't be a problem..internally at least.
? (10.0.1.1) at b8:c7:5d:c6:3c:db on en1 ifscope [ethernet]
It doesn't have a name.. although it has registered the MAC address and IP .. that is the TC unless you changed it the ? indicates there is an issue with device name. All the entries should have a name.
ray-hs-mac-pro:~ Ray$ arp -a
tc2.bigpond (192.168.2.104) at 60:33:4b:2e:91:77 on en1 ifscope [ethernet]
andrew-gigabyte.bigpond (192.168.2.130) at 0:25:22:16:43:c7 on en1 ifscope [ethernet]
bigpond.bigpond (192.168.2.254) at 0:24:17:71:ad:6d on en1 ifscope [ethernet]
bigpond.bigpond (192.168.2.254) at 0:24:17:71:ad:6d on en0 ifscope [ethernet]
? (192.168.2.255) at ff:ff:ff:ff:ff:ff on en1 ifscope [ethernet]
I have the TC in bridge and it is picking up the domain from my router.. if your using the TC as the main router then you should have entries for gotbackup.local
You are running SL still?? Or lion?
I thought of simply restoring the computer's settings to what they were 4-5 days ago, via Time Machine.
The issue is network.. so restoring will not fix it.
But so is my overdue dentist appointment...really not looking forward to either!
My condolances to your dentist.
I think you need to dig a bit harder to get the cause.
Most importantly are you getting IP via dhcp from the TC?
Do you have ethernet and wireless connected at the same time?

TM backup failed again...help please!!

Its been working fine for months & failed 3 times in the last couple of days, following are log from TM Buddy -
Starting standard backup
Backing up to: /Volumes/Kui-2/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
2011-01-25 22:56:12.577 FindSystemFiles[274:907] Looking for system packages
2011-01-25 22:56:12.988 FindSystemFiles[274:907] Using system path cache.
Backup content size: 165.5 GB excluded items size: 16.1 GB for volume Macintosh HD
No pre-backup thinning needed: 179.23 GB requested (including padding), 595.28 GB available
Waiting for index to be ready (101)
Copied 89.5 GB of 149.4 GB, 51437 of 771314 items
Indexing a file failed. Returned 200 for: /Users/ckui/Library/Mail/[email protected]@imap.gmail.com/[Gmail]/All Mail.imapmbox/Messages/384041.4.emlxpart, /Volumes/Kui-2/Backups.backupdb/CKui’s MacBook Pro/2011-01-25-225613.inProgress/BCE58664-D000-43A6-90E9-7677E042857B/Macintosh HD/Users/ckui/Library/Mail/[email protected]@imap.gmail.com/[Gmail]/All Mail.imapmbox/Messages/384041.4.emlxpart
Aborting backup because indexing of file failed.
Stopping backup.
Stopping backupd to allow ejection of backup destination disk!
Copied 213216 files (110.4 GB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11

Hello again,
Got a brand new external drive; reformatted to Mac standard, started well then almost to the end of the backup (163.13GB to total of 165GB) it started back to "Calculating Changes" & "Indexing Backup"!
Thanks in advance for your help.
Here are the log from Buddy.......
Starting standard backup
Backing up to: /Volumes/Time Machine Backup Jan-2011/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Backup content size: 162.0 GB excluded items size: 7.6 GB for volume Macintosh HD
No pre-backup thinning needed: 185.29 GB requested (including padding), 1.82 TB available
Waiting for index to be ready (101)
Copied 43.7 GB of 154.4 GB, 199486 of 943126 items
Copied 102.3 GB of 154.4 GB, 222627 of 943126 items
Copied 134.3 GB of 154.4 GB, 491140 of 943126 items
Copied 492128 files (152.0 GB) from volume Macintosh HD.
No pre-backup thinning needed: 6.24 GB requested (including padding), 1.66 TB available
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)

Backup aborted - Configuration Backup Failes

Over the past couple of days, I've started getting the Error "Backup aborted - Configuration backup failed" on 3560/2960 switches and 2900/2800 routers. Pretty much everything at my primary site and a few devices, but not all, at some of my clients. What's odd to me is that the devices with the backup failures now have a greyed out "Backup Now" button. Again that doesn't apply to all, but most devices.
Shawn Eftink
CCNA/CCDA
Please rate all helpful posts and mark correct answers to assist others searching for solutions in the community.

Hi Shawn,
We saw this same behavior this morning with a test ON100 in the lab. The ON100 may need to run through it's normal scheduled nightly maintenance window before the driver tries the backup and then subseqeuntly enables the Backup Now button within the portal. Please take a look at this customer again on Monday and let us know if the backup succeeded, and if the Backup Now button becomes available again. We are looking into what it will take to issue a fix, as a contingency plan, or until a fix can be deployed, we are looking into controlled periodic monthly reboots of all ON100 which might mitigate issue by clearing the /tmp ramdisk on the devices.
-mike

Time machine wont backup says backup failed

Hi all . I have had time maching running successfully for 5 years. It is running on mavericks IMAC and using an external MYbook drive - same setup 5 years. My macbok also backing up remotely over wifi to this drive using time machine. Recently my macbook stopped backing up and would not recognise the sparse file even though time machine could find the backups it would not backup. I connected th Mybook directly to my Macbook and it recrreated the backup and now works fine over wifi. However since connecting my Mybook back to IMAC time machine again recognises the Backups and history and the drive - but it wil not backup. It goes through the motion of preparing backup but fails after 45 mins just stating "backup failed" ! I run disk utility on the Mybook adn it is fine. I have deleted the in progress file but still does not work. How can I force Time machine to work - mad that it will recognise the drive, see all my previous backups but not use it as a backup drive and fail the backup with no proper error message. Any deas ?

Mister_E wrote:
Hi:
I have a mac that is about 3 months old. I am using Mac OS X 10.6.3. I am not using Time Capsule. I am using an external hard drive. My Mac's hard drive is 500 G the external drive is also 500 G.
That's almost certainly much too small. See #1 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
But of course, it depends on how much is on your internal HD, which you haven't told us.
The message I get says I have 74.74 GB of 499.75 GB available.
Under options I do have "Notify after old backups are deleted" checked.
That means you're running Snow Leopard. PLEASE update your settings (click +My Settings+ at the right of this very page, and select the version of OSX you're running, and be more specific than "iMac" about your hardware) so we know what we're dealing with, as asked before! PLEASE
That's one of the things that changed in Snow Leopard. Having that box checked in Snow Leopard does not prevent deletions.
As I said, it backed up fine for a couple weeks but now what do I do? No matter how small I make the backup, if it just keeps adding backups it will eventually fill the drive.
From your first post: +*"I started getting messages that TM failed to backup because is was full (something like that)."+*
Now that we know you're on Snow Leopard, most likely the message says *+"The backup disk is full,"+* which is simply the notification you asked for by having the "Notify after old backups are deleted" box checked. See #C4 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
Next time you get the message, take the time to note exactly what it says, and see #C4 in the Troubleshooting Tip.
And PLEASE update your settings.

EFI Folder on desktop during TimeMachine backup, backup fails.

Hello,
I am haing a very strange and infuriating problem. The problem is whenever my Time Machine begins to backup a folder shows up on my desktop labeled "EFI". The file size says 313.8MB, 312.6MB free. Then my Time Machine backup fails time and time again (pun intended).
The Time Machine is located on a MacMini Server, but even when I plug a TM drive directly into the USB it says the same thing and fails to backup. I've tired different brand drives but still the same outcome.
I then tired to clone the drive using SuperDuper but it can't even find the Macintosh HD. So I did a PRAM reset, repaired permissions, wiped and partitioned the drive and did a clean install of the current OS. I then used Migration Assistant to restore my data.
It ran fine for a day and now the same thing is happening all over again, but now it shows the EFI folder anytime I connect a USB or network drive onto it, plus it now takes a good 5 minutes to even boot.
I'ts absolutely maddening! Since I owned this laptop it's had the screen replaced twice as well as the logic board for random shutdown issues. I've begged and demanded for Apple to please replace this laptop since it was a month old. Sadly, Apple has refused any resolution other than to keep replacing parts and adding scratches. I purchased two twin units and the other unit has been whistling Dixie since day one. My son got one and I got stuck with the evil twin.
Any help would be greatly appreciated, but my guess is it is going to be shipped back to Apple for the 5th time.
Thanks for reading!

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressingcommand-V.
☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Time Machine Backup Failed with error: 2

I have been doing unattended continuous backups to a 1 TB drive for about 4 months via Time Machine. In the last 2 months I have been getting a dialog box with this message: "Unable to complete backup. An error occurred while creating the backup directory." In each case I have gone to Disk Utility to repair the disk, and each time have had to reboot to get the Repair Disk function to work, since without a reboot, the backup disk won't unmount. After repair, the backups resume, but the frequency of the failures is beginning to worry me. I never had problems with scheduled SuperDuper backups and am thinking of returning to that approach, albeit different.
Below is what is listed in in the system log after the backup failure. It lists "error: 2", whatever that is.
The backup disk has over 400GB space remaining.
Can anyone help me with this?
May 2 19:34:17 Macintosh /System/Library/CoreServices/backupd[12497]: Backup requested by user
May 2 19:34:17 Macintosh /System/Library/CoreServices/backupd[12497]: Starting standard backup
May 2 19:34:26 Macintosh /System/Library/CoreServices/backupd[12497]: Backing up to: /Volumes/WD1TB Backup Disk/Backups.backupdb
May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Error: (-50) Creating directory 2008-05-02-193428.inProgress
May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Failed to make snapshot container.
May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Backup failed with error: 2
Thanks,
Art

Betty - actually, no. Rebooting alone didn't resolve the problem. Time Machine still wouldn't resume backups.
Once the directory was rebuilt via Disk Utility, it is up and running again, at least for a while.

Time Machine Backup Fails - backup disk is unmounted during backup

I've been having trouble on and off with Time Mahcine backups. I have an iMac running Lion, an external USB HD which is my Time Machine disk. It will run fine for a day or so and then fail with the "Unable to complete backup. An error occurred while creating the backup folder". If I run the Time Machine Buddy utility it shows the follwing error log:
Starting standard backup
Backing up to: /Volumes/Media/Backups.backupdb
Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Media/Backups.backupdb/Kitchen size:37
Backup failed with error: 2
Stopping backup to allow backup destination disk to be unmounted or ejected.
Backup failed because the destination disk was ejected or disconnected unexpectedly!
Any idea why the backup disk would be unmounted during the backup?

I have had a related problem.
Over the last three-four years of using TimeMachine I have had FOUR (4) disk drives fail on me. In the first instance, the power supply failed twice. Switching from connection via Firewire to USB seemed to solve that problem.
Then in May 2011 I bought TWO x Freecom HD 1 TB portable drives, I indicated to the Apple retailer, YooBee, expressly for use as TimeMachine backups.
They have both FAILED for me, as per the description below, which I have filed on the Freecom support site.
So FOUR disk drives failing over 3 to 4 years is beyond bad luck, beyond coincidence, but 'conspiracy' as Churhill might have put it. The common factor is that all four disks failed 'on watch' as being my TimeMachine drives. I am VERY ALARMED at his rate of failure, and wonder if there is a fault with TimeMachine in burning out the disks through some feature of excess use?
I note the detailed advice here is pertinent ... but I've only just found it!
Backup, restoring, formatting info: Apple Support Communities. (n.d.). Retrieved January 16, 2012, from https://discussions.apple.com/message/16276201#16276201
Message to Freecom Support Forum 2012-1-14, and YooBee.
I was absolutely assured by my Apple Mac (YooBee, 123 Broadway, Newmarket) store that these drives would be perfect for TimeMachine backup. But to have TWO fail within 8 months of purchase is very, very, very alarming. One failing is bad luck. Two failing is more than coincidence....
There was an alarming clicking noise from the disks.
Disks were disconncted from USB.
Message from Mac saying USB drive disconnected incorrctly. I DID NOTHING: Timemachine was just in the middle of doing a backup, perhaps. I was just working away when I noticed the tiny noise, above.
I turned of Timemachine in preferences. Physically powered down and disconnected Freecom drive. Waited. Reconnected. Unable to remount. Used Disk Utility to mount, and initiated Repair.
Message Apple disk utility
Verify and Repair volume "MELLALIEU-01-FREECOM-HDD-1TB"
Checking file system
Volume repair complete
Updating boot support partitions for the volume as required
Error: disk Utility cant repair this disk. Back up as many files as possible, reformat the disk, and restore your backed up files"
Another message
Mac OS X can't repair the disk
MELLALIEU-01-FREECOM-HDD-1TB
You can still open or copy files on the disk, but you can't save changes to files on the disk. Back up the disk and reformat it as soon as you can.
Well: the Freecom is not able to be remounted, even after plugging, and replugging the USB.
This happened with TWO drives.
And despite the suggestion to backup the files NONE are accessible.
This is NOT what I expect to have happen with drives expressly purchased for use as TimeMachine backups.
I managed to reformat the one that first failed, about two months after purchase. I have not attempted to reformat the latest failure-- and loose my complete Timemachine backup. Naturally, I don't use the reformatted disk for Timemachine, but a Vault for Aperture.
Equipment specification and serial numbers:
Freecom HD Mobile Drive xxs 1 Tb x 2
model SSYAAA P/N 35154
Purchased May 2011, YOOBEE, Newmarket.
S/N 351540442100051.
S/N 351540442100021.

Since I installed Yosemite, Time Machine is not doing any backup. It just keep coming with the following message in a window: "Backup Failed. Time Machine could´t back up to "....... Time Capsule". What can I do start backing up again?

Time Machine not working since Yosemite was installed.

I had this issue too and went through all the great suggestion found on this site, but finally was able to resolve it after looking at the system.log to see the reason it was failing. By using terminal and entering:
sudo grep backupd /var/log/system.log
I saw "Backup failed with error:11". Then looking above, I saw many "Error: (-36) SrcErr:YES /Applications/" messages. After "Applications" I saw the culprit files that were causing Time Machine to fail. I deleted some Apps that I didn't need and found Time Machine would get farther than before. I then looked at the system.log again and saw it failing on the remaining Apps. I was able to use Time Machine to restore these App directories from a couple months ago before the Time Machine was failing. Now the problem is resolved. Whew! It seemed to be choking on corrupt files and these can be corrected by restoring earlier ones that were not corrupted.
Well, I thought I should share this with others that may have run into the same issue so they can save time. Hope it helps!

Monthly Backup Failed!

Similar Messages

Maybe you are looking for