LINUX:while Deleting OLD backup's got error that ORACLE is not in DBA group

Error
Error - The specified host user is not a member of the operating system DBA group. The host user must be a DBA group member since the database user does not have the SYSDBA role.
But. put users: system,oracle in OS /etc/group :
oracle:x:500:oracle,system
And both users have the DBA role

To be able to OS authenticate login as sysdba, your OS user need to be in dba group which you choose when you do installation.
SYSDBA role is not same as DBA role

Similar Messages

While creating InitialContext I have got error that server was not found...

Hello.
On the server console I'v seen next message:
java.util.EmptyStackException
     at weblogic.utils.collections.Stack.pop(Stack.java:72)
     at weblogic.rjvm.InboundMsgAbbrev.getAbbrev(InboundMsgAbbrev.java:85)
     at weblogic.rjvm.MsgAbbrevInputStream.readImmutable(MsgAbbrevInputStream.java:172)
     at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
     at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:290)
     at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:906)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
     at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:107)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:115)
     at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:685)
     at weblogic.rjvm.ConnectionManagerServer.handleIdentifyRequest(ConnectionManagerServer.java:255)
     at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:619)
     at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
     at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:638)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
I use correct version of weblogic.jar,
the property for initial context:
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://127.0.0.1:7001
The server is Veblogic 6.1
The client is runing under Visual Age 3.5 EE

"Yuriy Kuzmenko" <[email protected]> wrote:
>
The nested exception on the client side was:
java.io.StreamCorruptedException: Type code out of range, is 0
     java.lang.Throwable(java.lang.String)
     java.lang.Exception(java.lang.String)
     java.io.IOException(java.lang.String)
     java.io.ObjectStreamException(java.lang.String)
     java.io.StreamCorruptedException(java.lang.String)
     byte java.io.ObjectInputStream.peekCode()
     void java.io.ObjectInputStream.SkipToEndOfBlockData()
     java.io.ObjectStreamClass java.io.ObjectInputStream.inputClassDescriptor()
     java.lang.Object java.io.ObjectInputStream.readObject(boolean)
     java.lang.Object java.io.ObjectInputStream.readObject()
     int java.io.ObjectInputStream.inputObject(boolean)
     java.lang.Object java.io.ObjectInputStream.readObject(boolean)
     java.lang.Object java.io.ObjectInputStream.readObject()
     java.lang.Object weblogic.common.internal.ChunkedObjectInputStream.readObject()
     java.lang.Object weblogic.common.internal.ChunkedObjectInputStream.readObject(java.lang.Class)
     weblogic.common.internal.PeerInfo weblogic.rjvm.ConnectionManager.readPeerInfo(weblogic.rjvm.MsgAbbrevInputStream)
     void weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(weblogic.rjvm.MsgAbbrevJVMConnection,
weblogic.rjvm.MsgAbbrevInputStream)
     void weblogic.rjvm.ConnectionManager.dispatch(weblogic.rjvm.MsgAbbrevJVMConnection,
weblogic.utils.io.ChunkedDataInputStream)
     void weblogic.rjvm.t3.T3JVMConnection.dispatch()
     boolean weblogic.socket.JavaSocketMuxer.processSockets2()
     void weblogic.socket.JavaSocketMuxer.processSockets()
     void weblogic.socket.SocketReaderRequest.execute(weblogic.kernel.ExecuteThread)
     void weblogic.kernel.ExecuteThread.execute(weblogic.kernel.ExecuteRequest)
     void weblogic.kernel.ExecuteThread.run()
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested
exception:
[java.io.StreamCorruptedException: Type code out of range, is 0]
     java.lang.Throwable(java.lang.String)
     java.lang.Error(java.lang.String)
     weblogic.utils.NestedError(java.lang.String, java.lang.Throwable)
     weblogic.utils.AssertionError(java.lang.Throwable)
     weblogic.common.internal.PeerInfo weblogic.rjvm.ConnectionManager.readPeerInfo(weblogic.rjvm.MsgAbbrevInputStream)
     void weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(weblogic.rjvm.MsgAbbrevJVMConnection,
weblogic.rjvm.MsgAbbrevInputStream)
     void weblogic.rjvm.ConnectionManager.dispatch(weblogic.rjvm.MsgAbbrevJVMConnection,
weblogic.utils.io.ChunkedDataInputStream)
     void weblogic.rjvm.t3.T3JVMConnection.dispatch()
     boolean weblogic.socket.JavaSocketMuxer.processSockets2()
     void weblogic.socket.JavaSocketMuxer.processSockets()
     void weblogic.socket.SocketReaderRequest.execute(weblogic.kernel.ExecuteThread)
     void weblogic.kernel.ExecuteThread.execute(weblogic.kernel.ExecuteRequest)
     void weblogic.kernel.ExecuteThread.run()

Time Machine - strange behavior while deleting old backups

Not sure if this is the right place, because this is actually not on Time Capsule, but on a Time Machine on an external USB drive.
In any case, I searched the web for "time machine delete old backups" and found many discussions of various aspects of this task. My objective is to clean up a partition on a the external drive that I no longer use for active TM backups, but to retain a small set of backups in case I need to go back to them. The partition now has other uses and I need the space. My main TM backup is now on a separate Time Capsule.
So again my objective is not to remove all backups, but just most of them.
It appears that the well-discussed procedure is the following:
Go into Time Machine.
Select the Macintosh HD.
Go back to one of the oldest backups.
Click on the Gear > click Delete Backup.
This procedure will remove one Backup at a time, and it seems to take 5 - 10 minutes for each backup.
Here is what I noticed that was "strange":
You could delete a selected backup using the above procedure.
For the first selected backup so deleted, there is a confirmation dialog with a warning message that it is not undoable.
After clicking OK on the warning message, the display backs up to the "Present" backup, and the administrative password is requested.
After the administrative password is entered, the backup starts but control is passed back to the user interface, and another backup can be selected to be deleted.
However, after the second backup is selected and deleted, there is no warning dialog, and no request for the administrative password. At this point the user interface is busy and nothing more can be done until the backup delete is completed. Except that the Time Machine can be exited by first pressing Escape, then Cancel on the lower left of the screen.
If the time machine is exited, there is a Delete Backups progress dialog with a progress bar for each backup so far requested. If the second backup was requested, as in the steps above, there would be two backups.
I discovered by playing around that either you had to wait within Time Machine for the deletion to complete, or alternatively exit Time Machine. While I was not sure what was going on, I kept starting one backup, then exiting Time Machine and re-entering Time Machine and requesting another delete operation. Each time after entering Time Machine, the warning/admin password sequence occurred and I was able to exit. And then immediately re-enter Time Machine and request another backup. Only by exiting and re-entering could another delete request be made.
When out of Time Machine, I thus saw the Delete Backups dialog with any number of concurrent "Delete One Backup" progress bars.
Because of the nature of the hard links used to indicate backups, I was wondering if these multiple delete operations could possibly be hung in a deadly embrace, so I decided to only do one at a time. Some further study to see if the multiple delete operations were all able to complete would be needed to know if this would be a good way to "queue up" multiple delete requests.
Bottom line: seems like kind of an odd implementation. Would be really nice if you could select many (say 30) individual backups and delete them all at once, rather than taking 5 - 10 minutes each. Again, this is because I am trying to reclaim disk space, but not delete all the backups from a Time Machine backup set that is not in active use.
Also, the method of "queuing up" backup delete requests is kind of odd, but seems to work, with the proviso that I have not yet confirmed that doing more than one at a time actually works.

Heinz-G?uenter Arnold wrote:
since the upgrade to SL it seem that Time Machine has problems to completely remove old backups completely. The "removed" backups do not show up in Time Machine anymore, but the backup folders and part of their contents can still be seen in Finder.
Hi, and welcome to the forums.
That happens occasionally, in both Leopard and Snow Leopard, sometimes after something was deleted from the Finder, but also after an abnormal shutdown or improper disconnection of the TM disk.
Run a +*Repair Disk+* on it via Disk Utility, in your Applications/Utilities folder. If it finds errors, but can't fix them all, run it again (and again) until it either fixes them all, or can't fix any more.

MacBook Pro crashed while deleting old backups off partitioned external hard drive. Now only recognizes windows formatted half of drive. Can the Apple side be saved?

MacBook Pro 15-inch, Mid 2010
Processor 2.66 GHz Intel Core i7
Memory 8 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GT 330M 512 MB
Software OS X 10.9.5 (13F34)
I have an external hard drive:
2 TB Seagate Backup+Desk Media
Partitioned:
1TB - Windows NTFS
1TB - Mac (sorry I can't remember the formatting, whatever Mavricks asked me to use...)
What happened:
I was erasing 3 old backups from the Apple partition and my laptop crashed part way through emptying the trash. (it has done this many times before, where parts of the screen are frozen in square blocks displaced all over the screen. Screenshot not possible unless I use a separate camera).
When I force restarted my computer (holding down the power button) neither side of the drive was accessible. After running the Disk Utility and Verifying and Repairing the Disk Permissions and the Disk Itself (for the Windows side) I was able to access the Windows partition. However, upon attempting to do so with the Mac partition it tells me that it cannot be repaired. I have found many forums discussing SIMILAR situations but none with the same and here is why:
Up until this happening I could access ONLY the Windows partition when the drive was connected to either my Apple laptop in Bootcamp Windows 7 or my HP laptop in Vista, while my MacBook could access both sides of the drive. HOWEVER, after this crash, BOTH my Windows 7 and Vista can access both sides of the drive (so My files are still all there and accessible) but my MacBook Pro swears that the Apple partition is doomed.
Since the Apple side of my laptop is my primary workhorse I really want to figure out how to fix my drive.
So Questions:
1. Anything else I can provide to the experts out there to help me get this fixed?
2. Can I custom fix this via accessing the drive on either of the Windows systems?
3. Why would it suddenly show up in Windows when it became unaccessible to Mac?
Thanks All!

UPDATE:
It has been maybe a month since this happened.
After I made this post and was checking emails, walking away from computer, and then came back my Mac partition of the External Drive has shown up on the Desktop...
So, in the ever immortal way of asking the tech to come check the issue and the issue resolving itself, perhaps I should posted on the forum sooner...
NOTE: The disk still shows up as unusable in the Disk Utility and it appears that the files are read only (cannot make a new folder on this side of the external drive)
I still consider this a volatile issue because I do not want to lose the files on this half of the partition and I have not gotten a replacement drive yet (too much data to move to my computer and then format the current drive)

Auto-delete old backups

My time machine/capsule does not delete old backups, so it stops backing up when the time capsule is full. I tried deleting old backups from the sparseimages but it did not clear up any space. Any advice?
Thanks,
Glenn

You could also try compacting your Sparse Bundle if it happens again: type the following command into a Terminal window: sudo hdiutil compact /Volumes/DISK/mycomputer001a6f33001.sparsebundle. You should replace the MAC address with what you find by going to the Network Pane in System Preferences: write down the MAC address listed there so that you can substitute it into the Terminal command when compacting your Sparse Bundle. Make sure to replace 001a6f33001 with your Mac's Ethernet MAC address before attempting to run the command: otherwise you'll get an error message stating that the MAC addresses don't match since every Mac has a unique MAC address for their built-in 10/100/1000 Ethernet.
Make sure to substitute in the volume name of your Sparse Bundle too: otherwise the command won't work right.

HT201250 How do it delete old backups?

I have decided that some of the files I save for the last years is not longer require and I wanted to save some space on my Time machine HDD. So, how do I remove them? Like the entire backup data on certain date.

First, open Finder and select the Time Machine disk under Devices, in the sidebar. Then, go to Backups.backupdb > computers and delete the Time Machine backups you need
WHOA!!!! That is extraordinarily bad advice! Messing with your Time Machine backups in the Finder can damage or even destroy your backups!
The proper way to delete old backups is described here:
Should I delete old backups? If so, How?
However, note that this is completely unnecessary. Time Machine will automatically remove the oldest copies of files when it needs more space. Rather than deleting them now and discovering in a month that you actually do need to restore them for some reason, just leave them there and let them be removed when necessary.

I backed up my phone. Got a new phone. Should I delete old backup since I need the storage? Will I lose anything?

I backed up my phone. Got a new phone. Should I delete old backup since I need the storage? Will I lose anything?

I would restore the new ios device with the old backup it would make the new device have the same data as the only without it causing problems

Disk Full Error... Won't Delete Old Backups

Hello- Since upgrading to ML, Time Machine is notifying me that disk is full and will erase old backups on next backup. Problem is, its not deleting old backups. Thus, its not backing up any longer. This has only happened since upgrading to ML this week.
The setup:
- 2012 MB Air with 250GB SSD and ~ 75GB unused
- Latest ML Updates
- External 1TB HD totally devoted to Time Machine- 23GB remaining space available
It has been setup this way since 2012 and this is the 1st time Time Machine is unable to erase old backups.
Thoughts?
Thx!

See C4.
Time Machine Troubleshooting

Time Machine delete old backups

My wife has a MacBook Pro and uses Time Machine on a 500 GB external drive. She is using about 160 GB on her MacBook Pro, but the Time Machine drive is now full and is not backing up current files. The Time Machine backups go back to 2010 and two or three versions of the operating system. I would like to delete old backups from Time Machine, as I understand that only files no longer needed in other backups will be deleted. Is there any reason this approach should be avoided? Are there instructions on the best way to do this? Thanks.

tomarm wrote:as I understand that only files no longer needed in other backups will be deleted. Is there any reason this approach should be avoided? Are there instructions on the best way to do this? Thanks.
yes, your wife ..
A: needs a MINIMUM of a second HD to archive data on
B: Yes, time machine "throws data out the window" when full
C: HD clones are more important.
https://discussions.apple.com/docs/DOC-6031
Methodology to protect your data. Backups vs. Archives. Long-term data protection
Time Machine / Time Capsule
Drawbacks:
1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
6. Restoring from TM is quite time intensive.
7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
13. *Level-1 security of your vital data.
Advantages:
1. TM is very easy to use either in automatic mode or in 1-click backups.
2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
HD clones (see below for full advantages / drawbacks)
Drawbacks:
1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
Advantages:
1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
3. HD clones are unconnected and isolated from recent corruption.
4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
7. *Level-2 security of your vital data.
HD cloning software options:
1. SuperDuper HD cloning software APP (free)
2. Carbon Copy Cloner APP (will copy the recovery partition as well)
3. Disk utility HD bootable clone.

Time Machine Deletes Old Backups without warning!!

I have just lost loads of pictures and emails when my Timemachine deleted old backups. I was so happy to have an easy way to keep my iPhoto cleaned up while keeping all the photos for the future. I would load my all the photos from my camera, backup with TimeMachine and delete the "bad" unwanted photos, confident in the knowledge that these pictures are still there on my external. I looked forward to some future date when someone would write an easy piece of software to consolidate old iPhoto libraries and even go through TimeMachine and consolidate those photos too. But until that fantasy event, my pictures, even though not wanted were still there.
Not any more!!
I replaced my hard drive and reloaded my laptop from Timemachine and I think that was the event that sparked the dump.
There should be a special check box to make sure that NO backups are automatically deleted, EVER. They should be a way to make them Sacred!!
There should be a way to create a separate backup just for iPhoto because right now, there are no good ways to easily break apart or merge iPhoto libraries. At least what I was doing worked, (well.... until it didn't).
Any ideas??

nerowolfe wrote:
True, TM is not a classic archival system, but until the drive is full, the difference is moot.
No, the difference isn't moot.
I still have on my TM HD every file I ever had because it's only 1/2 full.
No, you don't. Read on...
Time machine has three levels of backups:
1) hourly - deleted after 24 hours
2) daily - deleted after a week
3) weekly - deleted only when the disk is full - these are the only deletions you will be warned about
Time machine is always deleting files. Every time it backs up, it deletes files.
But the OP's real question is why he was never warned about the old backups being deleted, as TM says it will do, archival stuff notwithstanding. Apparently TM simply ignores the user's request to be warned.
No, it doesn't.
That being said, as I asked in a post not too long ago, "how many have had a warning from TM that old backups are being deleted?" as one would expect when the TM preference box, "Warn when old backups are deleted" is checked.
It appears to me to be a bug.
I ask again if anyone has gotten this warning.
Nobody answered my previous post with a yes.
Yes.
Because Time Machine continually cleans up behind itself, it tries very hard to ever delete the weekly backups. The only time I've gotten the deletion warning was when my disk was full. I think I just avoided the problem by removing my old Parallels images from Time Machine and got back an extra 70 gig or so - good for another six months.
This is not a bug. This is how Time Machine works. It is unfortunate that the original poster did not fully understand this. The fact is that Time Machine backs everything up. If you create 100 files, it backs up the folder with 100 new files. If you delete 100 files, it backs up the folder with 100 less files. Then, the next day, it deletes old backups. The only one it keeps is the last one, with 100 less files.
It is correct to say that Time Machine is not an archival system. It is a backup system. If you want to save your files forever, you need to copy them to a location that isn't under the control of any sort of automatic software.

Since Mavericks upgrade, Time Capsule stuck deleting old backups ... for days

I have a previous generation 2TB Time Capsule shared by three of us, each with separate accounts.
I know there's not much space left on the Time Capsule and that it's therefore expected that Time Machine would make room by deleting old backups. But my account seems stuck forever on these deletions (for over 72 hours now), while the other two accounts on the Time Capsule are working just fine.
I've been through Pondini's recommendations for (a) patience and (b) finally resetting Time Machine, but on it goes.
Here is the last couple of hours of the log (filtered for this problem). The entire log for the last 72 hours is too long to post -- but the pattern is the same, with the constant deletions barely making a dent, and sometimes in fact the space available decreases.
I'd cheerfully give up on the oldest backups, but meanwhile it's been 8 days since TC has been able to complete a backup. (I have been cloning the drive daily with SuperDuper just to make sure I have a fallback until this is figured out.)
Hoping one of you can recommend a course of action.
Thanks in advance for any help...
10/28/13 8:06:51.276 PM com.apple.backupd[758]: Found 1022200 files (58.34 GB) needing backup
10/28/13 8:07:01.173 PM com.apple.backupd[758]: 75.13 GB required (including padding), 16.43 GB available
10/28/13 8:07:05.162 PM com.apple.backupd[758]: Ejected Time Machine disk image: /Volumes/edbern/EB’s MacBook Air.sparsebundle
10/28/13 8:07:05.162 PM com.apple.backupd[758]: Compacting backup disk image to recover free space
10/28/13 8:25:44.384 PM com.apple.backupd[758]: Completed backup disk image compaction
10/28/13 8:25:44.388 PM com.apple.backupd[758]: Starting manual backup
10/28/13 8:25:44.915 PM com.apple.backupd[758]: Network destination already mounted at: /Volumes/edbern
10/28/13 8:26:04.847 PM com.apple.backupd[758]: Disk image /Volumes/edbern/EB’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups 1
10/28/13 8:26:05.230 PM com.apple.backupd[758]: Backing up to /dev/disk3s2: /Volumes/Time Machine Backups 1/Backups.backupdb
10/28/13 8:26:31.228 PM com.apple.backupd[758]: Event store UUIDs don't match for volume: Macintosh HD
10/28/13 8:26:31.546 PM com.apple.backupd[758]: Waiting for index to be ready (100)
10/28/13 8:27:25.289 PM com.apple.backupd-helper[112]: Not starting scheduled Time Machine backup: Backup already running
10/28/13 8:27:31.784 PM com.apple.backupd[758]: Waiting for index to be ready (100)
10/28/13 8:27:56.892 PM com.apple.backupd[758]: Deep event scan at path:/ reason:must scan subdirs|new event db|
10/28/13 8:35:43.224 PM com.apple.backupd[758]: Finished scan
10/28/13 8:35:43.241 PM com.apple.backupd[758]: Not using file event preflight for Macintosh HD
10/28/13 9:05:03.078 PM com.apple.backupd[758]: Found 1022200 files (58.34 GB) needing backup
10/28/13 9:05:16.881 PM com.apple.backupd[758]: 75.13 GB required (including padding), 31.85 GB available
10/28/13 9:05:17.689 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/03624AE5-22CE-463C-9265-CE6A8826C535 containing 4 KB; 31.85 GB now available, 75.13 GB required
10/28/13 9:05:17.700 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/7503F996-8E27-4558-9308-15FC60270865 containing 4 KB; 31.85 GB now available, 75.13 GB required
10/28/13 9:23:23.471 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/C424E6F6-EFBE-4154-A543-375E805E68C8 containing 8.3 MB; 31.86 GB now available, 75.13 GB required
10/28/13 9:28:36.239 PM com.apple.backupd-helper[112]: Not starting scheduled Time Machine backup: Backup already running
10/28/13 9:55:03.037 PM com.apple.backupd[758]: Error: Error Domain=NSOSStatusErrorDomain Code=-36 "The operation couldn’t be completed. (OSStatus error -36.)" (ioErr: I/O error (bummers)) deleting backup: /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/C434BAEA-946E-4531-BA61-74DD5A34EFF2
10/28/13 9:55:03.037 PM com.apple.backupd[758]: Deleted 3 backups containing 8.3 MB total; 31.86 GB now available, 75.13 GB required
10/28/13 9:55:03.321 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.579 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.580 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.582 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.702 PM com.apple.backupd[758]: Backup canceled.
10/28/13 9:55:11.830 PM com.apple.backupd[758]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
10/28/13 9:55:11.831 PM com.apple.backupd[758]: Failed to eject volume (null) (FSVolumeRefNum: -110; status: -35; dissenting pid: 0)
10/28/13 9:55:11.832 PM com.apple.backupd[758]: Failed to eject Time Machine disk image: /Volumes/edbern/EB’s MacBook Air.sparsebundle

Alas, it spent the night fruitlessly.   I think I need to find a way to kill the existing backup or dismount the disk first. Sorry I'm a bit thick about all this.
10/29/13 12:39:06.822 AM com.apple.backupd[1628]: Starting automatic backup
10/29/13 12:39:07.028 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:39:07.995 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:39:11.397 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 12:39:12.969 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc243f1c0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 12:39:13.059 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
10/29/13 12:39:13.060 AM com.apple.backupd[1628]: Waiting 60 seconds and trying again.
10/29/13 12:40:24.403 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:40:24.792 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:40:27.642 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 12:40:29.209 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc27275c0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 12:40:29.324 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
10/29/13 12:40:29.325 AM com.apple.backupd[1628]: Waiting 60 seconds and trying again.
10/29/13 12:41:40.533 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:41:41.252 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:41:44.549 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 12:41:46.208 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc26090d0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 12:41:46.309 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
10/29/13 12:41:46.310 AM com.apple.backupd[1628]: Giving up after 3 retries.
10/29/13 12:41:46.350 AM com.apple.backupd[1628]: Backup failed with error 31: 31
10/29/13 1:44:01.616 AM com.apple.backupd[1768]: Starting automatic backup
10/29/13 1:44:01.649 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:44:02.604 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:44:07.254 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 1:44:08.881 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af9531a70 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 1:44:08.962 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
10/29/13 1:44:08.962 AM com.apple.backupd[1768]: Waiting 60 seconds and trying again.
10/29/13 1:45:20.105 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:45:20.536 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:45:23.526 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 1:45:25.145 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af97030e0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 1:45:25.280 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
10/29/13 1:45:25.280 AM com.apple.backupd[1768]: Waiting 60 seconds and trying again.
10/29/13 1:46:36.511 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:46:37.340 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:46:40.510 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 1:46:42.150 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af9608030 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 1:46:42.195 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
10/29/13 1:46:42.195 AM com.apple.backupd[1768]: Giving up after 3 retries.
10/29/13 1:46:42.198 AM com.apple.backupd[1768]: Backup failed with error 31: 31
10/29/13 2:49:46.227 AM com.apple.backupd[1880]: Starting automatic backup
10/29/13 2:49:46.301 AM com.apple.backupd[1880]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 2:49:47.381 AM com.apple.backupd[1880]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 2:49:50.418 AM com.apple.backupd[1880]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35

I backup to an external hdd with Time Machine, when it ran out of space it did not delete old backups, now my internal hdd says its full when before it had heaps of space. I have searched for extra files but cant find any. Can anyone help, please.

I backup to an external hdd with Time Machine, when it ran out of space it did not delete old backups, now my internal hdd says its full when before it had heaps of space. I have searched for extra files but cant find any. Can anyone help, please.

First, empty the Trash if you haven't already done so. Then reboot. That will temporarily free up some space.
To locate large files, you can use Spotlight as described here. That method may not find large folders that contain a lot of small files.
You can also use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Proceed further only if the problem hasn't been solved.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install ODS in the Applications folder as usual.
Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Launch the Terminal 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 Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means.
When you're done with ODS, quit it and also quit Terminal.

Doesn't Time Machine delete old backups when it needs more space?

I've had time machine running for a long time now. It worked flawlessly for quite some time.
Today it gave me the error that there was not enough free space on the disk to complete the backup (the error message says something like there is 360 GB of data on the Time Machine drive already, 140 GB of free space and it would require more than that to complete my backup). I have a 500 GB Time Machine disk and my Mac has a 500 GB hard drive, so I should technically never run out of space.
The Time Machine almost acts like this is the first time I've ever backed up, which is not true. Shouldn't Time Machine delete old backups to make space for the new? What's even weirder is that if I open the "Star Wars" window of Time Machine I only see one backup from March 31, 2011, but I have been running Time Machine for well over a year now. I'm totally confused as to what happened. Any advice on how to get my Time Machine back up and running (without buying a new drive) would help!

You see only one backup in the Time Machine window because Time Machine has deleted the older backups to make space to do the current backup.
Time machine needs some working space to do its backups, and so backing up a 500GB drive onto a 500GB time machine volume is not ideal.
However, I do essentially the same thing, and what I do, when I have this problem, is exclude things from the backup.
First off, figure out what you changed. If you moved things from one partition to another, then that will cause a backup of the size of the thing that was moved. This may be why you have a large backup.
When I have this problem, I exclude large things that have changed recently from the backup. This makes the backup smaller, and means that there is less working space needed. I do this until I get a successful backup. Then I remove things, one by one, from the exclusion list, and back up after each one.
So, for instance if you just put 4 new folders on your drive, each of which s 20GB of data and they are named A, B, C and D, add all four to the exclusion list, do a backup, then remove A from the exclusion list (leaving B, C & D on it) and do a backup, and continue like this, adding 20GB of backup data each time until none of the new data is on the exclusion list and you get a completed backup.
Another possible issue, if you use multiple partitions, is that Time Machine may be keeping an obsolete backup of a partition that you previously reformatted. To see if this is the case, go into time machine (The universe interface) and go back to the most recent backup it shows. Click on your computer and see what partitions show up-- are any of them old ones that have been reformatted and renamed? You may be storing a duplicate backup because Time Machine does not realize that the disk that went away isn't coming back (because it has been reformatted as a different partition)
You can right-click on these items and remove them from your backup by sleecting "Delete all backups of...." This will free up space as well.

Tried to install OS X Yosemite on my MacBook. Got message that it could not be installed on my computer due to error while extracting files from package "Essentials.pkg". When i quit the installer as recommended it goes in a loop and gets stuck.

Tried to install OS X Yosemite on my MacBook. Got message that it could not be installed on my computer due to error while extracting files from package "Essentials.pkg". When i quit the installer as recommended it goes in a loop and gets stuck.

Hey corrafromlondon,
Thanks for the question. After reviewing your post, it sounds like the installer file isn't working. Have you tried deleting the installer and redownloading the installer? I would recommend that you read this article, it may be able to help you isolate or resolve the issue.
How to install OS X Yosemite on your Mac - Apple Support
you can find the Yosemite installer app in your Applications folder or Launchpad.
Thanks for using Apple Support Communities.
Have a nice day,
Mario

Time Machine running out of space but doesn't delete old backups

First some context:
I am running Parallels Desktop on a 2011 iMac. The VM is on a partition that is excluded from Time Machine.
I have a second partition where I copy the VM every night using CCC. (This avoids TM backing up a large VM every hour).
TM says initial backup is 220 GB. I have a 1TB USB drive attached. So normally, this works fine.
This morning 100GB were copied to my Parallels Desktop partition. So TM should copy something in excess of 100GB during backup.
Currently, only 15GB are free on my backup volume. But TM doesn't try to delete old backups. It doesn't seem to recognize the size of the backup. Instead when it starts, it predicts about 1GB to backup. Then during backup the amount grows (note that no new data is changed during backup!) and it finally hits the wall at 15GB because the disk is full.
Any idea why TM doesn't figure out the real backup size?
Here's the log from TM Buddy:
10.12.12 13:25:13,472 com.apple.backupd[27667]: Backing up to: /Volumes/Time Machine-Backups/Backups.backupdb
10.12.12 13:38:34,588 KernelEventAgent[48]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine-Backups', from '/dev/disk1s2', low disk
10.12.12 13:38:34,000 kernel[0]: HFS: Low Disk: Vol: Time Machine-Backups freeblks: 38389, warninglimit: 38400
10.12.12 13:38:45,000 kernel[0]: HFS: Vol: Time Machine-Backups Very Low Disk: freeblks: 25589, dangerlimit: 25600
10.12.12 13:38:45,066 KernelEventAgent[48]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine-Backups', from '/dev/disk1s2', low disk, very low disk
10.12.12 13:38:45,088 mds[42]: (Warning) Volume: Indexing reset and suspended on backup volume "/Volumes/Time Machine-Backups" because it is low on disk space.
10.12.12 13:39:47,794 KernelEventAgent[48]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine-Backups', from '/dev/disk1s2', low disk
10.12.12 13:39:53,885 com.apple.backupd[27667]: Error: (-34) SrcErr:NO Copying /Volumes/WBackup/Parallels/Smart iMac Windows 7.pvm/Smart iMac Windows 7-0.hdd/Smart iMac Windows 7-0.hdd.0.{a09d01ec-5596-4f65-b4cd-86aeff90082f}.hds to /Volumes/Time Machine-Backups/Backups.backupdb/Smart iMac/2012-12-10-072536.inProgress/3380F092-9336-408F-90EB-387FDE60A79D/WBackup/ Parallels/Smart iMac Windows 7.pvm/Smart iMac Windows 7-0.hdd

I would highly recommend the following resource to help you with this problem:
http://pondini.org/TM/Troubleshooting.html
Hope this helps

LINUX:while Deleting OLD backup's got error that ORACLE is not in DBA group

Similar Messages

Maybe you are looking for