Space Error on Vault Backup

I'm still relatively new to Aperture, and finally got all my digital images into the library and added keywords.
I just tried to back up my library (395GB) and I received an error message stating lack of space on my vault. My back up drive is an internal 750GB drive, with nothing else on it. Before the backup, I had rearranged the images into different folders, renamed some folders, and added some keywords, but didn't add any images to the library since the last back up.
What is going on, and what can I do to back up the library?
Thanks for the help!!!

I had this exact same problem. It happened after I did a huge import of images into Aperture as I was first moving into using the program. I imported images into about a dozen projects, all named "Untitled xx." After the import, I was able to create a vault just fine. Then, a couple of weeks later when I decided to organize the projects by renaming them and shuffling around the images and deleting a bunch, Aperture said that I had no room on my vault drive to back up. This was absolutely preposterous! I had nearly 4 times the amount of space on the drive as the size of the vault. I had to delete the vault and start again, which, IMO, totally defeats the purpose of the vault.
My solution was two fold.
First, I've not moved all of my images to referenced files and back them up using third party solutions rather than using Aperture's Vault. Apple need to do some serious work on this feature as it feels like an afterthought stuck into Aperture. it is poorly implemented and it's usefulness questionable since it seems that sometimes there is no guarantee that you can fully restore your library with the vault in case the worst has happened.
Second, I use Chronosync to synchronize the Aperture Libraries. If you read this article you can see how to do so:
http://www.oreillynet.com/digitalmedia/blog/2006/11/syncingaperture_librarieson.html
What's cool is that you can automate the process just by scheduling Chronosync to trigger wither at a certain time or when you plug in a backup drive. Best thing about this method is that it also syncs deletions as well, which is what the big hang up is with the Vault. BAcking up to the vault, you need to have all this extra space for deleted images and scratch disk space for re-copying files that have been moved around.
I don't know if anyone from Apple is listening to this, but this has been a BIG problem with Aperture since version 1.1 and I wish they'd fix it already.

Similar Messages

Problems after space error reported

My Time Capsule device has worked perfectly for months and deletes old backups as necessary when there is insufficient space for a new backup. I'm using a 500Gb device to backup a Mac Pro and a G4 Powerbook - no problems until yesterday.
During a backup I received an error message - this gist of it was "Time Capsule encountered an unexpected space problem during a backup and will create space next time". Expecting this problem to be resolved automatically I clicked OK and carried on working. The problem I now have is that Time Capsule has been preparing for backup for several hours (across two consecutive days) now and shows no sign of starting a new backup.
I left the MacPro running overnight yesterday but the new backup had not started when I started work this morning. I restarted the MacPro this morning (8 hours ago) and prompted Time Capsule to "Backup Now" - it has been eight hours and the backup has not started - it is still "preparing".
I have looked in the system log and can see messages containing write error 28 and something to do with "needs recovery" (see below) but this way above my level of expertise.
(May 27 00:00:29 Cliffs-G5-Tower mds[31]: (Error) DiskStore: permission cache (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775/perm Store) write error: 28
May 27 00:00:29 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/B452885D-CF11-4D79-8349-35C3D3EF5545)(Err or) IndexCI in CIMetaInfoSync:write err: 28
May 27 00:00:29 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775)(Err or) IndexCI in openIndex:index shadow err:-1 at 0.
May 27 00:00:29 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775)(Err or) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775/0.; needs recovery)
There are lots of messages in the system log as follows: -
(May 27 16:48:48 Cliffs-G5-Tower KernelEventAgent[33]: tid 00000000 type 'hfs', mounted on '/Volumes/Backup of Cliff's G5 Tower', from '/dev/disk5s2', low disk
May 27 16:49:04 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/F856DAC8-CE5F-46E8-B826-19B10BC52F31)(Err or) IndexCI in CIMetaInfoSync:write err: 28
May 27 16:49:34 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/F856DAC8-CE5F-46E8-B826-19B10BC52F31)(Err or) IndexCI in CIMetaInfoSync:write err: 28
May 27 16:50:04 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/F856DAC8-CE5F-46E8-B826-19B10BC52F31)(Err or) IndexCI in CIMetaInfoSync:write err: 28)
I can also see messages from 26 May that report no space left on device and then others that say "waiting for index to be ready (909 >0) - see below.
26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Exception writing exclusions cache. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Unable to create exclusions cache data.
26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Failed to write exclusions cache. Continuing anyway.
26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
26/05/2009 14:57:24 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
26/05/2009 14:57:34 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
26/05/2009 14:57:49 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
This message is repeated every 30 seconds and is the only entry in the log since the "no space left on device" message.
Is this just Time Capsule carrying out a deep traversal (there's no mention in the log) or do I have a problem with the TC device? I'd be very grateful for any help or suggestions.
Kind regards,
Cliff
Brighton, UK

I think I got it.
Open Terminal, type "hdiutil compact " and drag the sparsebundle onto the terminal window, so that it copies the right path. Hit return and let it free some space. The sparsebundles do not automatically compact themselves when they delete some old backups, so doing it manually did the trick for me.
After completing, I had some 40 GB space again and the backup worked again.

Time Machine estimated space is wrong resulting in unexpected out of space error.

Hello,
I'm running Mountain Lion 10.8.2 on a Mac Pro with a 300 GB boot partition and a 485 GB data partition in a RAID-5 configuration. I have two 2 TB G-Drives attached via firewire for Time Machine backups.
As I understand it, Time Machine (TM) estimates the amount of space it requires to perform an incremental backup. If there is not sufficent room on the backup drive, TM selects a number of previous backups to remove to make space. The problem I've encountered is the amount of space TM estimates is much less then is required.
While TM is performing the backup, in TM preferences the progress message shows the estimated size slowly increasing until it exceeds the amount of space available on the backup drive and eventually leads to the error "The backup disk ran out of space unexpectedly."
I have reviewed the often cited link http://pondini.org/TM/C18.html. I have performed repairs on the two TM backup drives/partitions and on the internal data drive/partition and have done a verify on the internal boot drive/partition. There was one error on one of the backup drives which was repaired and all others passed without errors.
Are there any other steps that can be taken to determine the reason TM cannot accurately estimate the required space for a backup?
Thanks.
Nathan

After further testing the case ended up being not to do with any of the video codecs at all - somehow the audio was the problem. I tried a few different audio codecs which started working, but then suddenly the original started working as well. I'm not sure what exactly caused the change, but I figured I'd post as much as I knew in case someone else runs into similar problems. Look at the audio is my best guess, I suppose.

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/

Insufficient disk space to perform full backup

Hi to all
i'm trying to backup my acs 5.2 "backup acs repository repository application acs" but acs gives me a critical error.
% Creating backup with timestamped filename: acs-121022-1431.tar.gpg
% Error: Insufficient disk space to perform full backup.
% Try lowering the data window on ACSView Data retention under Data Management Configuration.
% Application backup error
how do i lower the data witdow in ACS view?
thanks in adv
Antero

Hi
the problem is solved now, i've openned a TAC and the cisco Guy told me how to solve it.
in summary you need to have root access to ACS and then erase de acsview database and put a clean one.
my acsview db has grown to 175GB., this was caused by the misconfiguration of acsview database doesn't being backuped and the purgin was, in this case, not being also done.
so Brian if you hav e the same problem then you need to open a TAC case.
Thanks
Antero Vasconcelos

Hard drive says I have more than 300 GB available with a 500 gb capacity. Yet I get "Low Disk Space" error messages when I do anything.

Hard drive says I have more than 300 GB available with a 500 gb capacity. Yet I get "Low Disk Space" error messages when I do anything.
Attempted solutions:
-I created a new User Account and I can download large files with no issues.
-I ran "Repair Disk Permissions" but still get warnings.
Google Drive Warning:
Spotify Warning:
But on my other user account I can use spotify and download large files, etc.

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Your Time Capsule disk is low on storage space - error

I am getting the error "Your Time Capsule disk is low on storage space." and it now flashes amber. I use the time capsule to set up a wireless network and I can no longer access the internet from my MapBook Pro in another room, only if I am next to the Time Capsule. Help!!! Why is my time capsule low on storage space? I thought it is suppose to delete the old backups to make room for the new backups.

MacDoz wrote:
I too am getting the same low disk space issue on my Time Capsule, and have not been able to find an answer anywhere given that I thought the Time Capsule was meant to automatically delete old back-ups.
Those are two different, independent, things.
Since you can use a Time Capsule for things besides backups, there's a built-in warning (the flashing light) when it gets near full (exactly how full is not clear).
Time Machine is separate; when it doesn't have space for a new backup, it will delete the oldest backup(s) as necessary, if it can, to make room for new ones.
The handling is a bit different, though, for Leopard vs. Snow Leopard.
In Leopard, if you have the +Warn when old backups are deleted+ box checked in Time Machine Preferences > Options, it will fail with a message. All you have to do is remove the check.
In Snow Leopard, it will delete old backups as necessary, do the backup, then send a message if you have the box, now worded +Warn after old backups are deleted,+ checked.
See #C4 in Time Machine - Troubleshooting for details.

HT1414 how much disk space is needed for backup and restore.

i want to unlock iphone,for this how much disk space is needed for backup and restore activiti

OK... now subtract the music. That's not part of the iPhone backup. Neither are apps, but in app data is.
Why are you asking? Did you get an error? If so, then clear out some disk space.

Can't Hide Aperture During Vault Backup

Running the latest Mac OS and Aperture on a Mac Pro with a ton of RAM. Whenever I run Aperture's vault backup (I backup onto another hard drive), Aperture is essentially locked up during the backup. I can't even hide the app in the background as I continue to use my Mac. I can use other apps in front of Aperture, but the desktop is always hidden by the Aperture window, and this makes it a lot more difficult to access apps and windows in the Finder, especially if Aperture is backing up for a long time.
This has been true for all versions of Aperture that I've owned, if I remember, back to 1.0.
Does anyone else have this problem? Is there some workaround?

So it's not just me, eh?
I didn't know spaces would help. Thanks, I'll give that a try.

I cannot back up my phone to I cloud. Error message 'last backup could not be completed'.

I cannot back up my phone to I cloud. Error message 'last backup could not be completed'.

go to settings/icloud/storage and backup and verify avialable storage space.
Reboot ipad,
Try backing up again

I just had to reformat the external hard drive that houses my iPhoto library, then restore it from a backup. Now Time Machine is telling me my backup hard drive suddenly does not have the space to complete a backup. I also noticed when I go in to Time Mac

I just had to reformat the external hard drive that houses my iPhoto library, then restore it from a backup. Now Time Machine is telling me my backup hard drive suddenly does not have the space to complete a backup. I also noticed when I go in to Time Machine, there are only about 5 backups recorded on the ext. hard drive. There were many more before. Any idea what happened and if I have to buy a new back up hard drive?

Hallo Kieth ,
I am not quite ready to restore the full iphoto library , as I have days of work re - imputting titles,descriptions and enhancement . I hope that your suggestion works , as I use my Macbook basically to work with digital photography. Through time , I will need to delete my library to recover more disc space and I would hate to have to spend more time re - imputting titles and descriptions all over again .
Thanks for your interest and advice.
regards - Alan

I am having issues with Time Machine. Error message "The backup disk image could not be created.

Error message "The backup disk image could not be created." I have tried everything I have found online in the community from TM full reset to changing my computers name. Anything else I can try? I am using a Seagate external HD with a connection through my router. I spent an hour on the phone with seagate and everything is ok on the HD end.
TM sees it and it is mounted but cannot go any further. HELP?!!!!
Thanks
-A

How should it be connected? It has a usb port and ethernet. The USB on the ExHD looks like the port on the back of my computer, so I would need one wth the same ends? Do they make those?
I can usually fix most my comp problems myself, but this new ExHD has stumped me.
Thanks for your help.
-A

How to fix this error message The backup disk image "/Volumes/AirPort Disk/FARES DEL VALLE's iMac.sparsebundle" could not be accessed (error -1).

how to fix this error message The backup disk image “/Volumes/AirPort Disk/FARES DEL VALLE’s iMac.sparsebundle” could not be accessed (error -1).

The troubleshooting C17 is the specific article.
http://pondini.org/TM/Troubleshooting.html
This is generally a Lion error.. and you will need 5.6 utility to get access to the disk area.
So download the real utility. Run it instead of v6 toy version.
http://support.apple.com/kb/DL1482
Go to the manual setup, disk page and click on disconnect all users.. that will unmount all users connected to the disk and allow it to start working. But there are a number of other issues that are possible cause. Pondini lists some of them.

HT4946 Can I back up my iPhone 4S to my ipad 3 (64 gb)? I do not have a computer. I deleted pictures from my iPhone and added then to the ipad, but now I don't have enough space in iCloud to backup either device. Why not?

Can I back up my iPhone 4S to my ipad 3 (64 gb)? I do not have a computer running Mountain Lion. Our desktop still runs Tiger, so I purchased the 3rd generation iPad with 64 gb thinking it had had plenty of room to backup my iPhone photos. I used a camera connection kit and transferred about 1100 old photos from my camera roll on my iPhone to my ipad. I then deleted pictures from my iPhone and now my camera roll has only 357 photos. However, in the Settings, under "About" it says I have 2147 photos. Why? I only have a total of 216 photos in all my albums. However, now I don't have enough space in iCloud to backup either device. Why not? Any help, any advice, appreciated please! I spent a long time on the phone with Apple today and they couldn't solve the problem.

rabidrabbit wrote:
Can I back up my iPhone 4S to my ipad 3 (64 gb)?
no
rabidrabbit wrote:
However, now I don't have enough space in iCloud to backup either device. Why not?
iCloud only give so much space for free storage, then if you exceed the limit of 5gb you have to pay for additional storage.

Heap space error while creating XML document from Resultset

I am getting Heap space error while creating XML document from Resultset.
It was working fine from small result set object but when the size of resultset was more than 25,000, heap space error
I am already using -Xms32m -Xmx1024m
Is there a way to directly write to xml file from resultset instead of creating the whole document first and then writing it to file? Code examples please?
here is my code:
stmt = conn.prepareStatement(sql);
result = stmt.executeQuery();
result.setFetchSize(999);
Document doc = JDBCUtil.toDocument(result, Application.BANK_ID, interfaceType, Application.VERSION);
JDBCUtil.write(doc, fileName);
public static Document toDocument(ResultSet rs, String bankId, String interfaceFileType, String version)
    throws ParserConfigurationException, SQLException {
        DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
        DocumentBuilder builder = factory.newDocumentBuilder();
        Document doc = builder.newDocument();
        Element results = doc.createElement("sims");
        results.setAttribute("bank", bankId);
        results.setAttribute("record_type", "HEADER");
        results.setAttribute("file_type", interfaceFileType);
        results.setAttribute("version", version);
        doc.appendChild(results);
        ResultSetMetaData rsmd = rs.getMetaData();
        int colCount = rsmd.getColumnCount();
        String columnName="";
        Object value;
        while (rs.next()) {
            Element row = doc.createElement("rec");
            results.appendChild(row);
            for (int i = 1; i <= colCount; i++) {
                columnName = rsmd.getColumnLabel(i);
                value = rs.getObject(i);
                Element node = doc.createElement(columnName);
                if(value != null)
                    node.appendChild(doc.createTextNode(value.toString()));
                else
                    node.appendChild(doc.createTextNode(""));
                row.appendChild(node);
        return doc;
public static void write(Document document, String filename) {
        //long start = System.currentTimeMillis();
        // lets write to a file
        OutputFormat format = new OutputFormat(document); // Serialize DOM
        format.setIndent(2);
        format.setLineSeparator(System.getProperty("line.separator"));
        format.setLineWidth(80);
        try {
            FileWriter writer = new FileWriter(filename);
            BufferedWriter buf = new BufferedWriter(writer);
            XMLSerializer FileSerial = new XMLSerializer(writer, format);
            FileSerial.asDOMSerializer(); // As a DOM Serializer
            FileSerial.serialize(document);
            writer.close();
        } catch (IOException ioe) {
            ioe.printStackTrace();
        //long end = System.currentTimeMillis();
        //System.err.println("W3C File write time :" + (end - start) + " " + filename);
    }

you can increase your heap size..... try setting this as your environment variable.....
variable: JAVA_OPTS
value: -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m

Space Error on Vault Backup

Similar Messages

Maybe you are looking for