Tag: Backup

  • Reviewing Backup for my Photos

    Reviewing Backup for my Photos

    [UPDATE: After reading this, go to the bottom of the post to discover that this was really one of the worst decisions I’ve ever made. I’ve reviewed what I’m doing and have reverted to using more hard disk storage and storing it off-site. I’ve cancelled my additional storage with Google Drive. I may re-visit this in the future to use Adobe Cloud Storage if I move to using Lightroom CC more.]

    It’s always good to stop, think, review and possibly change the way you do things. I’ve always been reasonably confident about my backup strategy for my photographs, but a trip away last weekend without my external hard disk which is my working storage for my images, as well as carrying the Lightroom catalogs got me to thinking.

    As long as the hard disk is not sitting under the desktop computer and is away from that computer and the Time Machine backup disc that sits behind the computer – happy days. In the worst case scenario I would not only have my working disc to get started on as soon as I needed it, but I’d also have the Time Machine to restore from. Seemed OK – especially since I’d set Lightroom to copy imported photos to a Google Drive folder, and likewise I’d set Lightroom to backup the catalog to another Google Drive folder on exit. With the Google Drive folders being sync’d to the Cloud – I felt reasonably “safe”.

    I’d also created a bullet-proof annual off-site backup of the external hard disk with a neighbour, so that once a year I would swap the disks around and be reasonably confident of an easy restore from the Time Machine backup of the external hard disk – happy days (hopefully) … or so I thought.

    The weekend away however – without that working external SSD hard disk got me to thinking, and caused me to quickly review cloud storage options. I read this excellent article and that gave me some useful leads, and insights and made me consider using an external cloud service, but I already had – Adobe Photography Plan, Dropbox, iCloud, oneDrive and Google Drive, and I could consider shipping everything off to my web-hosting site as well – so did I really need/want another option?

    I decided to go with what I knew and to reconfigure how I used Google Drive with Backup and Sync. Put simply, (1 -> to the cloud) I’m now using My Computer with just one Folder (actually the entire external hard disk) to create a backup of that disk on an increased subscription (£79.99pa for 1Tb) Google Drive; and (2 <- from the cloud) I’ve cleaned-up my existing Google Drive content in the Cloud to that which I actually want access to, or to give others access to – shipping content elsewhere on my hard-disk. I’ve left the “Photo and video upload size” as High Quality (not original quality) as that higher resolution and chargeable storage will be covered anyway by the fact that the images are being treated as files, not images in the Backup and Sync of the external hard disk; and I’ve unchecked “Upload newly added photos and videos to Google Photos” as I will only be doing that from my Phone, not from the computer.

    The initial Backup and Sync, will take a long time I know, but then subsequently on a daily-use basis I won’t need to do a second copy of the Imported Images to Lightroom as that will be handled by the Backup and Sync of the external hard disk where the images will then be. So … I can rest assured that I have Backup copies of all my images, and the Lightroom catalogs that record the changes/edits I make to them – really happy days! Let me re-iterate – this is not so that I can edit them anywhere, it’s to be on the safe side in case of catastrophic loss – it’s a backup strategy, not part of an editing workflow for Lightroom, or anything else.

    Why did I choose Google over the other options? Cost, integration of existing practices, speed of upload, familiarity.

    This approach to backup also highlights the value of Lightroom as a non-destructive photo editor. Once imported, the images never change; it’s the catalog that changes and that will still be backed up to Google Drive separately when I exit the program so nothing should ever be lost! Sync’s after the initial one will generally be quite fast.

    What I will have to remember however is NOT to shutdown the computer whilst Backup and Sync is running – so I better just stop writing and go and have a cup of tea!

    =====================

    So, five days later and Backup and Sync hasn’t finished yet! The idea of backing-up to the Cloud wasn’t necessarily a bad idea but the execution and scope was really not great thinking. If I’d confined the Backup to just the current year’s images that would probably have been OK, but I’d already decided against having different annual Lightroom catalogs, so the die was cast … I had to copy all the images. Now, all I can do is wait until it finishes.

    I also know that there was a huge gap in my thinking in backing-up from the external USB-attached SSD. The disk access was potentially fast, but the USB slowed things down. Given my strategy (which I’m happy with) for storing Catalog and Images on an external SSD, backing-up to the Cloud from it was just plain daft as I’d inserted another step in the process. Backing-up from the computer’s internal SSD would have been much faster, but I couldn’t then have used Backup and Sync for continued Backup of the external SSD.

    Then there’s the question of whether using Backup and Sync was the best way of doing the initial Backup. Perhaps, just perhaps (I’m not going to test it) it might have been better (faster) to do a Folder Upload from My Drive on Google Drive. I’ll never know!

    Anyway, documenting one’s failings is as good as any way I know of learning, and my goodness have I learnt a few things about Cloud Backup and Google Drive!

  • Google Photos – some observations

    Google Photos – some observations

    I’m following up my previous post with some notes based on using Google Photos for a couple of days of testing and observation. This will lead into some thoughts on how I will use it, and what I need to do to make sure the Workflow is “right” for me. This might also be relevant to others, especially those using both DSLR and Smartphones, so I’d welcome comments.

    The first thing to mention is that My Drive > Google Photos and the separate Google Photos menu item on your Google Drive are not the same! This is reflected in this note which advises you not to use Google Photos Backup (from your Desktop) and the sychronised My Drive > Google Photos  local folder at the same time.

    What this means in practice is that if you have a Workflow that involves placing an image in your local Google Photos folder to sync to your My Drive folder on Google Drive for sharing, or for embedding in a blogpost (like the tasteful one above taken during the testing 😆 ), then you probably shouldn’t use the Google Photos Backup application.

    What does this mean then? Well a couple of observations.

    1. Google Photos is a good repository for images taken with Smartphones; it’s painless, quick and ensures that if you have auto-sync switched on in either your Google Photos app, or in the Google+ app (for iOS 7, or earlier) that you have a safe and secure home for your images which will have lots of other advantages. read this excellent review by Mike Elgan for further information.
    2. If you’re a DSLR camera user then you have to think carefully whether you want to use the Google Photos Backup application on your desktop.
      1. If you don’t use any other Image Editing software then it might well be a good idea – setting the Image Quality probably to High (so that you don’t use any of your 15Mb of Free Storage) and following the guidance in the note referenced above about excluding your My Drive > Google Photos from your Google Drive synchronisation, if relevant.
      2. If you’re using something like Lightroom to post-process your images then it might be better to use the export options in the software to copy an image (or collection of images) from the software to your My Drive > Google Photos folder to sync up to Google Photos  and then on for sharing from either your desktop, or your mobile device a little later, and not using the Google Photos Backup application.
    3. Luckily none of the decisions you make now are irreversible, but a bit of careful consideration now may mean that you have the “right” workflow for your needs. For me as an iPhoneographer and DSLR camera user I’m happy to let Google Photos now be my Backup and Storage Solution of choice for the iPhone (see 1 above), but because I’m also a Lightroom user I’ll not use the Google Photos Backup application. Moreover, having made this decision it means that I can, if I chose, Import any images taken on the iPhone into Lightroom for post-processing, meaning I don’t clutter Lightroom up with images I don’t really want to keep.

    Any thoughts?