Migrating a 300GB Aperture library with limited disk space.

This morning I decided to migrate my 300GB Aperture Library to the new Photos app on my MacBook Air. I have 20GB of remaining space on my internal drive and thanks to Apple's use of hard links I was hoping this wouldn't be an issue when migrating.
After choosing to use iCloud Photo Library I was prompted that I would need to upgrade to the 500GB plan which I did. After completing the purchase I was then prompted that there wasn't enough space on my drive to download the current contents of my iCloud Library (13GB). Having 20GB available I thought this quite odd but proceeded to use optimised storage. It's worth noting that the entire contents of my iCloud Library already exist in my Aperture Library which I'm attempting to migrate. I was hoping the Photos app would be able to determine these duplicates before downloading everything!
The real kicker came when Photos app began processing the library. After reaching 3% I was informed that I would need approximately an additional 53GB of space in order to migrate this library! Freeing up that much space on my internal drive isn't a possibility without removing my Aperture Library so I'm going to have to complete the migration on an external drive.
Side note: It would be nice if Apple assed all space requirements before requiring me to pay and upgrade my iCloud space. It might be several weeks before users are in a position to actually utilise the space if such barriers occur at this point in the migration workflow.
I have now copied my Aperture Library to an external drive and I'm performing the migration on there.
I'm assuming that the additional 53GB of space the Photos app required is purely for the purposes of migration. It seems a hefty amount of disk space (roughly 18% of the library size) to be consumed otherwise. After migration is complete I'm hoping the Photos Library will only consume a small additional amount of space considering the master images and previews are hard linked. If this is the case then I should be able to copy the library back to my internal drive.
Couple of questions:
1) Is this 53GB of space required purely for migration?
2) Will I be able to copy both the Photos Library and the Aperture Library to my internal drive, preserving the hard link relationship between the two? If so, would this need to be achieved via the command line or should the Finder resolve this?
I'm worried that initiating a copy from the Finder, will in effect see the hard links for the original files, therefore requiring space for both full libraries. Ideally I would like the files to behave in the same way they would had I carried out the migration on my internal drive giving me the freedom to preserve (and therefore open) the Aperture Library in the future on my internal drive.
Thanks in advance.

68a3bf80-faea-4a37-8ac3-8f443cd21af5 wrote:
It is not clear if the MOVE operation of the LOB field toward a new tablespace performs a copy of the entire table, including segments that can be compacted (so with a total size of 400 gb), or just the real content of the field (5gb).
And it is not clear how to evaluate the size of archive logs and redo logs generated during such operation.
Some, many, most IT Professionals would run sample benchmark tests to see for themselves what occurs.
Are you incapable or unwilling to run your own simple benchmark test to learn how Oracle's behavior might impact your database?

Similar Messages

RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE

제품 : RMAN
작성날짜 : 2002-12-09
RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
==========================================================
PURPOSE
이 자료는 Oracle 9.2 이상의 RMAN에서 사용 가능한 MAXSIZE 기능에 대하여
설명할 것이다.
How to restore archive logs with limited disk space
Old Backup을 사용하여 RMAN으로 database를 recvoery할때, 모든 archived
redo logfile들을 Restore할 destination의 disk space가 모자란 경우를 종종 만난다.
이러한 경우 여러 개의 restore and recovery job으로 나누어 수행한다.
즉, 첫 번째 restore and recovery job이 끝나면 archived redo logfile들을 지우고
다음 적용될 것들을 restore한다. 그리고 다시 Recovery를 수행한다. 이러한 작업을
원하는 시점까지 recovery를 하기위해 반복적으로 수행한다.
Oracle 9iR2(9.2.0.x)부터 RMAN은 MAXSIZE option을 제공하는데 이것은 archive log
file이 restore될 disk의 space를 control할 수 있게 해 준다.
만약 disk space가 매우 제한적이라면, 즉 예를 들어 모든 archive log의 size 합보다
disk free space가 적다면 MAXSIZE option을 사용하는 것은 매우 유용하다.
이 OPTION이 기술되면 RMAN은 Media Manager에게 disk space 크기에 부합하는 만큼만
archive log들을 restore하도록 한다. 부가적인 restore operation들은 restore된
마지막 archive log가 적용될 때마다 발생한다.
MAXSIZE option은 이러한 작업들을 하나의 rman job으로 처리하게 해 주고
실수를 하지 않게 해 준다.
아래는 MAXSIZE를 설명하기 위한 예제이며 총 6 단계로 구성되어 있다.
STEP 1: Add data to the database to enforce log switches
STEP 2: Backup the database and archive logs and delete the logs
STEP 3: Add additional data to enforce new log switches
STEP 4: Remove the data file and simulate a database crash
STEP 5: Restore the data file from the backup
STEP 6: Recover the database using MAXSIZE
위 예제는 Unix와 Windows 모두에 적용될 수 있다.
STEP 6 는 다음과 같은 조건으로 두 번 수행될 것이다.
1) MAXSIZE가 archive log size보다 작은 경우:
이 경우 RMAN-6558 Error message를 만나게 된다.
그러므로 MAXSIZE를 archive log보다는 크게 설정해야한다.
2) MAXSIZE가 archive log size보다 큰 경우:
예를 들어 여러 개의 archive log를 포함할 수 있을 정도로 크게 설정하면
restore/recovery는 user에게 transparent하게 수행되어진다.
즉 archive log들은 restore된 후 applied되고 deleted되어 진다. 다시 새로운
archive log들이 restore되어지고 applied된 후 deleted 되어 진다. 이러한 작업은
recovery가 끝날 때까지 반복되어진다. 이러한 작업들이 진행되는 동안 RMAN은
아무런 Message도 발생시키지 않는다.
# Step 1: INSERT enough new data to generate log switches
create table rman_tst (col1 varchar2 (10));
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 2: BACKUP the database and the archive logs automatically
# and then delete the input
run {
backup database format='/web01/usupport/krosenme/admin/backups/db_%d%s%t'
plus archivelog format='/web01/usupport/krosenme/admin/backups/arch_%d%s%t'
delete input;
# Step 3: INSERT enough new data to generate new log switches
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 4: REMOVE users01.dbf file and crash the database
mv users01.dbf users01.org
shutdown abort
# Restore is now needed as the data file is deleted. The backup was
# taken before the new data was added to it, thus archive logs are
# needed to bring the database up to date
# Step 5: RESTORE the data file from the full backup
run {
restore datafile '/web01/usupport/krosenme/oradata/kro_920/users01.dbf';
# Step 6: RECOVER
run {
recover database delete archivelog maxsize 10 K;
# This will fail with RMAN-6558 as the archived log has a size of 16 KB,
# which is bigger than MAXSIZE limit of 10 KB. So the error is expected
# and MAXSIZE works as designed.
# Now rerunning STEP 6: but with MAXSIZE 50 K
run {
recover database delete archivelog maxsize 50 K;
RELATED DOCUMENTS
Recovery Manager Reference, Release 2 (9.2)

cold backup means offline backup, you shut database normally and copy datafiles to another location.
i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
backing up archivelogs whith rman script which is:
run {
allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
change archivelog all validate;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
release channel c1;
so here is the details.
1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
So
first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
and then restore them and then apply them.
we need rman commands to register these backups and restore them.
Regards,
Kamil

Saving aperture library to external disk

I did a search and it appears time machine is not a great way to save aperture, and for my needs in general time machine isnt a great option until I can easily afford huge disks. Anyway, my Aperture library is growing and saving each time from internal disk to external disk is taking longer and longer. Is there any way to save changes in Aperture without having to move the whole library every time?
Thanks

i use this in a shell script. change the paths to reflect your situation and save the file with a .command extension that way you can run it from the finder.
#!/bin/sh
# Sync of Aperture library with external disk muse one
echo "Sync of Aperture library with external disk muse one"
echo "----------------------------------------------------"
rsync -avE --delete /Users/joost/Pictures/Aperture\ Library.aplibrary/ /Volumes/muse\ one/Libraria\ Principal\ Aperture/Aperture\ Library.aplibrary

MacBook Pro with SSD that has a limited disk space (120GB). Rendering in Project File (User/Movies/Final Cut Projects), it takes huge space and the limited disk space would not be enough for the whole editing.

I'm using MacBook Pro with 128GB SSD that has a limited disk space. As we know, when rendering in Project File (User/Movies/Final Cut Projects), it takes huge space and the limited disk space would not be enough for the whole editing.
My question is, Is there any method to get the rendering Projects file saved into an external hard drive which is connected with USB/ Thunderbolt/ Firewire, with huge disk space (eg. 500GB HDD).
Now, new project created in my Mac is automatically saved in (User/Movies/Final Cut Projects) and my Mac has ran out of space to hold the files.
Thank you.

You have at least 3 different ways to show the project library:
1) Go to WIndow->Show Project Library
2) Click the button in bottom left of your window:
3) Hit the keyboard shortcut (Command-0)
The project library will be shown, occupying the area where the timeline usually is.
Your hard disks will be visible. Click the hard disk where you want the new project to reside and hit Cmd-N to create a new project.

Is it possible to share an aperture library with different users using osx server.

is it possible to share an aperture library with different users using osx server.

Not really. You should not be sharing an Aperture library over a network. It's not designed for that and you'll likely corrupt your library at some point.

HAVE BEEN UNABLE TO RETRIEVE MY OLD LIBRARY OF PHOTOS, ALBUMS AND PROJECTS SINCE DOWNLOADING AN APERTURE 3 SOFTWARE UPDATE TWO DAYS AGO. THE NEW LIBRARY ONLY HAS A FEW NEW PHOTOS IN ONE FOLDER PLEASE ADVISE AS HOW TO RETRIEVE OLD APERTURE LIBRARY WITH

HAVE BEEN UNABLE TO RETRIEVE MY OLD LIBRARY OF PHOTOS, ALBUMS AND PROJECTS SINCE DOWNLOADING AN APERTURE 3 SOFTWARE UPDATE TWO DAYS AGO. THE NEW LIBRARY ONLY HAS A FEW NEW PHOTOS IN ONE FOLDER
PLEASE ADVISE AS HOW TO RETRIEVE OLD APERTURE LIBRARY WITH ALL MY PHOTOS, ALBUMS AND PROJECTS

Find the old Aperture library in the Finder and double click it to launch Aperture with that library set to the default.
And check your caps look key. It appears to be stuck.

Share aperture library with another aperture user

How do I share the same aperture library with another aperture user on a different computer each using separate aperture software? We have have tried using a hard drive, but the vault is not showing up to download.

are you trying to work simultaneously from the same library? I'm not sure Aperture will handle that one very well, but as I've never tried it I can't say for certain.
You may be able to "check out" projects from the main library to work on individually within your own personal libraries. When you're done w/ your work you would check the project back in to the main library for someone else to use.
I think the danger is in trying to access the same .plist or image at the same time as Aperture wouldn't know who's instructions to follow.

Warning of limited disk space on my phone

Recently, I can no longer send text, take pictures or do anything on my phone, but make a phone call. I have backed up my phone to iTunes and my text were working for a little bit, but now again, I cannot send anything. There is warning that keeps popping up saying limited disk space, but I deleted everything off of my internal storage and still hasn't fixed the problem.

Will Aperture "see" the managed
library if it is on a RAID? Do I even need a Vault?
I backup my RAW files to DVD anyway. Any other
suggestions would be welcomed. I have not purchased
the RAID unit yet, but I am thinking of the CalDigit
eSATA. Roger
Jeremy has an article talking about how to integrate Aperture libraries into CalDigit's RAID.
http://www.caldigit.com/Testimonials/aperture-caldigit.pdf
The SATA RAID will definitely give you better speed.
http://www.caldigit.com/S2VRDuo.asp
or you can use CalDigit FireWire RAID which supports both RAID 0 and RAID 1 all together in one box.
http://www.caldigit.com/FireWireVR.asp
If you are looking for larger drive and more RAID levels, the 8-bay RAID unit can reach 8TB in RAID 0, probably 7TB in RAID5.
http://www.caldigit.com/HDPro.asp
Power G5 Quad and Intel Mac Pro Mac OS X (10.4.3)

Moving from iPhoto to Aperture with limited drive space

My biggest concern is the lack of space on my MacBook Air.
I have already purchased and download Aperture.
In the Import window I see the "move files" radiobutton and the "copy files" radiobutton under the "Store Files:" dropdown, but they are disabled.
As I understand if I just import my IPhoto Library, it will duplicate the files into the Aperture Library, and that wont work since my current library (iPhoto) is way bigger than my freespace in disk.
Buying external drive is not an option now since I im saving to buy a NAS that will solve my space problems in the near future.
What i would like to achieve is just to move all my iPhoto Library to Aperture Library. I wont use iPhoto anymore.
Can someone help me with this? Im really looking forward to use Aperture....

Hello Richieto,
I have already purchased and download Aperture.
In the Import window I see the "move files" radiobutton and the "copy files" radiobutton under the "Store Files:" dropdown, but they are disabled.What i would like to achieve is just to move all my iPhoto Library to Aperture Library. I wont use iPhoto anymore.
Set the "storeFiles" selector to "in their current location".
Have you seen this support article. Moving from iPhoto to Aperture - How to move http://www.apple.com/aperture/iphoto-to-aperture/how.html
If you follow these instructions, you will import your iPhoto Library by referencing - that means, all images remain in your iPhoto library; your iPhoto Library will remain unchanged, but Aperture references the files in in the iPhoto Library. This will save disk space; your images will be stored only once: Set the "Store Files" selector to "in their current location".
If you decide to do it this way, make sure you have a working backup of your iPhoto library. Also remember at all times that your master image files now are managed independently by two applications, that do know nothing of what the other app does and are not synchronized. So you must not move the iPhoto library, and you must not delete any images that are shared by both applications. Other than that this way to import from iPhoto will be the best deal, if you need to be frugal with disk space.
What i would like to achieve is just to move all my iPhoto Library to Aperture Library. I wont use iPhoto anymore.
Once you are happy with the way Aperture handles the images you can copy your iPhoto library to a backup location and consolidate the master image files (File -> consolidate) by moving them from your iPhoto Library into the Aperture Library. This will delete them from iPhoto and store them inside the Aperture Library package. Then delete the iPhoto Library after testing that the consolidation was successful.
I im saving to buy a NAS that will solve my space problems in the near future.
Just a caution - you should not use the NAS to store the Aperture library - an Aperture library needs to bestored on a local volume formatted MacOS X extended.
Regards
Léonie

Using Aperture library with different accounts

I needed to use my library with two different accounts that are on the same MBP. I read where you might be able to put the library on an external disk and check ignore ownership on the info of the HDD. I had recently installed a 320GB HDD to avoid having to drag around an external so I thought maybe if I partitioned the drive it would "see" the second partition as an external. I partitioned off 50GB and checked the "ignore ownership" in the bottom left corner of the info window. I option+opened Aperture and created a new library in the second HDD. After opening Aperture, I imported a few pics into the library and made dup's. I modified them in my account, closed out of Aperture and logged off. I then logged in under my wife's account and was able to open Aperture by option+opening Aperture and choosing the new library location. The pics that I had imported under my log-in were there as well as the the modified versions. I re-modified the versions to see if it work the other way. I closed out of Aperture and logged out of my wife's account and logged in under mine. I clicked on the Aperture icon in my dock and it came right up w/out any problems. I was able to view the versions that I re-modified under my wife's log-in.
I know you shouldn't share the library across users just in case two account users are trying to access the same library at the same time; but in my case it is one laptop with two accounts so we wouldn't physically be able to access it at the same time.
So if you have a big enough HDD and you don't want to drag around an external, partition it however big you think you'll need it, check the "ignore ownership" box in the HDD info window, add read & write permissions for the different accounts, move/copy your current library to the new partition and option+open Aperture to choose the new location.

Thanks! Just the answer that I was looking for! I had tried just moving the library into the shared directory, but, as we now know, this does not work.
Now only if I had a partition on my local HD (with "ignore ownership" set)...

How to upgrade Aperture with insufficient disk space

Hi,
I am trying to upgrade to the latest version of Aperture (from 3.4.3 to 3.4.4). I downloaded the update from the App Store but now whenever I try to launch Aperture it says that there is insufficient space on the library volume to perform the upgrade. The library is on a 3Tb external hard drive which only has 5Gb free. I have a lot of photos that I would be happy to delete but now I can't get in to delete them. If I select Cancel Upgrade then Aperture doesn't launch. I did briefly select Continue and Aperture started the upgrade but I Forced Quit from that as I assume it would eventually have crashed anyway.
Is there any way I can get in, using either the old or new version, to just go through and delete some images to free up the required space? Otherwise, is the only option for me to buy an even bigger external drive and manually copy the library file over to that?
Thanks for your help.
Regards,
Robert

Robert,
I am just worried about what might happen, if our internal SSD should fail. The system files, your user settings, mail boxes, everything in your user library and system library, the installed applications, plug-ins, Aperture presets, etc. From what you are describing, you are taking good care of your documents, but the system itself and the work you are putting into configuring it is not backed up. Should your system drive crash you would have a hard time to recover from that.
The easiest way to backup your system drive and the internal HD2 would be to use one of your 3TB drives with Time Machine. You need not necessarily Time Capsule to be able to do that. Time Machine can work with any external disk, that is formatted MacOS X extended.
Just plug in the backup drive you want to use, then open "System Preferences" and click the Time Machine icon.
Click the "Select Backup Disk" button.
Enable "Show Time Machine in Menu Bar".
Click the "Options" Button. If your backup drive is not large enough to include your Aperture library, deselect the other external drives in the "Options" panel. You may even deselect the second internal drive, if you are backing that up differently and only want to create a backup of the system. Then a small 500GB drive should suffice to get you started with system backups. But backing up both internal drives at once using TimeMachine would be much preferable.
Then set the switch to "on".
The first backup may take a very long time, but it will run in the background, so let it run.
Léonie

Using same Aperture library with different machines

Hi
I travel between locations some 7hrs apart and want to take my Aperture Libary and Vault with me to add to and work on in each location.
I have a Mac Pro at one location and MBP and 2011 Mac Mini (pre thunderbolt) at the other running Aperture v3.1.3 and Snow Leopard 10.6.8
I have my Aperture Libary, Vault and Referenced files etc on a seperate/external drive/s to my OS and applications.
Having to reconstruct the libary from a vault each time I change locations is time consuming as I am working with a growing Libary at the moment 720GB + 500 GB of referenced files on a second HDD
I would just like to be able to set it up so I can just plug the Aperture library and Referenced files in launch Aperture and start working
Is anyone doing this? or has any ideas ?
Many thanks in anticipation

A few points to consider:
To make a vault into a normal library you use the restore function in Aperture.
Having the vault and live library on the same spindle is not a good idea as you realize, if one goes they both go, so you need to get the vault onto a separate drive ASAP. Also as the masters are referenced you need to make provision to get those backed-up as well. And remember as they are referenced backing up the library (either by vaulting it or copying it) will not back up the masters in this case.
Given that you are physically moving the drive between locations getting everything backed-up is even more important. Also remember if the environments you are moving the drive between are extreme (moving from cold to warm in either direction) give the drive time to acclimate before spinning it up. And after you have spun it up give it some time before actually writing to it.
The question of using a vault over simply copying the library is asked a lot. There are pros and cons to each.
On the plus side. If you have a managed library the masters are backed-up with the vault and as libraries with masters in them tend be large the fact that the vault operation only write the changes after the initial vault operation makes for quicker back-ups. Copying a full library with referenced masters can't be a long process.
If the library has referenced masters in it the advantages of the vault aren't as great. You still need to back-up the masters seperatly and as the library tends to remain smaller copying it isn't as big a deal.
One other thing to keep in mind about vaults. You can't get just a single image or project out of it. It needs to be restored before you can open it with Aperture. So you will need the disk space to do the restore. With a copy you can just access it with Aperture.
Hope this helps,
regards

Any experience backing up an Aperture Library with Crashplan?

To be sure, I'm not using Crashplan for a primary backup. However, in the case of disaster, I'd like to move from my regional backup model to a backing up using a service. I realize that those of us who use a backup services with large libraries are on the fringe, but we all want to keep our libraries, don't we?
The Crashplan forum has few old articles allude to the fact that backing up an Aperture 2 library using Crashplan is not advisable.
The Aperture 3 library format has changed quite a bit.
What have your experiences been using Crashplan and Aperture 3? Have you attempted a restore after significant modification to your Aperture library, such as adjustments, moving projects, adding/deleting images, faces, places, etc.?

I just conducted a test with Aperture 3 and Crashplan. The results were unexpected. Here's how I performed the test, and what I learned:
I created a project, imported files, made some adjustments, and ran a Crashplan backup. Once the backup completed, I opened Aperture, moved projects, made additional edits, including brushes, changed metadata, altered faces, places, and tags. I emptied the trash, then rejected and deleted more files, and changed ratings.
I did the above three times, running Crashplan along the way, even with Aperture open. I restored my library, then compared the original and restored Aperture libraries.
The number of images, faces, places, metadata, adjustments, ratings, trash, and rejected items all matched. I did find two notable discrepancies. The source library when I began the restore had gone from 4.7 GB to 2.49 GB, primarily because I had deleted several movies. The restored library in CrashPlan and on my disk (once restored), was 4.63 GB. When I opened the restored library, it regenerated thumbnails and/or previews. The file resulted in 4.69 GB when complete.
What was taking up the additional 2GB? The movie files were still under the masters folder. They did NOT appear in the rejected items, trash, or any other project. They were, however, in the masters folder. I tried rebuilding the Aperture database, and importing it into a new project. I could not reduce the size of the library because the deleted files remained.
So . . . Crashplan appears to be holding on to these deleted files. The good news is, the database appears to be just fine otherwise. Any ideas on how to repair an Aperture 3 database to remove the files and shrink the library as necessary, if a restore is required?

AppleTV: sharing aperture library on external disk

I moved my Aperture library from the iMac to an external hard disk in order to free memory capacity on the iMac. Adjusted the settings in iTunes in order to instruct AppleTV to use the Aperture library on the external HD. It fails completely. Checked the permissions of the library on the HD and they are R/W, so that cannot be the issue. Anyone familiar with what I have missed?

USB2 is a poor connectivity method for hard drives on Macs, adequate for backup where speed is unimportant but bad news for a Library. Aperture performance is largely about the Library, so you want it on a relatively unfilled internal drive, definitely not on an external USB drive.
Hard drives slow as they fill above 40% or so. Take enough data off the internal drive to maintain at least 100 GB free space and keep the Aperture Library on the internal drive with Referenced Masters on external drives.
In the future buy large hard drives (currently the 1 TB size is cost effective) that have multiple connectivity methods that include Firewire800 and eSATA. One good source is OWC: <http://www.owcomputing.com/>.
Good luck!
-Allen Wicks

Can't sync Aperture library with multiple user accounts

I have created the aperture library on my main computer account and have synced photos to my iPhone with no problem. I created an account for my wife on the computer and she has admin rights. When I try to sync photos from Aperture onto her iPad I get the error message: You do not have enough rights for this operation. I checked the permissions on the Aperture library and she has Read+Write rights. Is there a solution so that we both can use Aperture for the management of our photo library but still have separate accounts?

yes, as best as I could tell.
This is a library I use for my desktop wallpaper (rotating 5 seconds apiece, random pics) so the images are kept in a folder separate from the library, which is one of the few that I permit to copy images and manage their location.
So I deleted those four images from the library, deleted their album, and reimported them from the main folder, and recreated their album, and all was well.
I presume one of them got corrupted, but the odd thing was that iTunes complained the phone couldn't be synced, and in no way indicated a fault with a file being synced.

Migrating a 300GB Aperture library with limited disk space.

Similar Messages

Maybe you are looking for