- #Synology cloud station backup too slow update
- #Synology cloud station backup too slow windows 10
- #Synology cloud station backup too slow windows
I store my Lightroom catalog (the catalog only, not the photo RAWs) on my computer's SSD, sync'd by Dropbox.
#Synology cloud station backup too slow windows
While on Windows it may be something like X:\Photos\…, on MacOS the path is in the format of /Volumes/Photos/… so you can't exactly share a catalog across machines easily without changing the path each time you swap machines (if you need to access stuff on the NAS on both machines).
The reason I prefer keeping all my computers on the same OS is that I want the remote NAS volume path to remain the same across devices.
#Synology cloud station backup too slow windows 10
I just happen to use Windows 10 computers for Lightroom: my desktop PC and my Thinkpad X1 Carbon laptop. My Lightroom usage is also pretty much the same. Google can do this entirely on its own on a daily cadence and it's quite handy. I had thought about using Hyper Backup for this but that app is intended for backing up data local to the NAS to cloud providers, instead of having the master copy live on a cloud provider like I have with my Lightroom catalog.Īmazon S3 Google Cloud sync: While not directly related to the NAS, I have manually set sync tasks on Google Cloud Storage to backup some of my Amazon S3 buckets (used for hosting the photos on my site via Cloudfront). I could probably automate this with a script on my desktop one day. So I occasionally move versions of the catalog file to a folder on my NAS manually. Unfortunately, it is just sync, not versioned backup, so if I accidentally delete it in Dropbox, it will be deleted from the NAS too (Dropbox has file restoration of course but ideally I would have this solved on my end as well to be safe). I don't have any photos on there but I have my Lightroom catalog stored there so I'm using Cloud Sync to store a copy on my NAS in case I ever get locked out of Dropbox. Hopefully Synology will eventually add proper Google Cloud support to Hyper Backup.ĭropbox sync'd to my NAS via the Cloud Sync app. I had to create a lifecycle rule on the Google Cloud storage website that would automatically change any objects in that bucket to the correct Nearline storage class I wanted, instead of the regular and much more expensive multi-region standard class that the files kept getting marked as. Update: In my experience doing this alone did not respect the bucket-level Nearline storage class I had set. Then you just set the Custom Server URL to and provide your Google Cloud credentials and it will just work. At this time the Hyper Backup app does not natively support Google Cloud Storage as a provider, but you can set it up under Amazon S3 if you enable the S3 Interoperability mode on Google Cloud Storage. Google Nearline via the Hyper Backup app. This is a complete backup that also lets me manually browse individual files on the Backblaze site instantly.Īmazon Glacier used via the Synology Glacier Backup app to backup the entire NAS. Today my primary cloud backup services for the NAS include the following:īackBlaze B2 used via the Synology Cloud Sync app to backup my photos shared folder. There is also a debatable stance that it's actually better to buy disks from different manufacturers for a RAID array to be safer. I was worried that the two identical Seagate disks were from the same batch and if one began failing so soon, it could be possible the other disk from the same batch could be on the way out too. hinting at just any drives you had lying around) is that the drives used for your storage volume don't all have to be identical. One of the benefits of Synology SHR (well frankly, RAID itself was made for this and the original acronym stood for redundant array of inexpensive disks. I decided to play it safe and replace it with a 12TB Western Digital Red drive (though Seagate warranty did send a replacement drive that I will keep as a spare). I know these things happen from time to time, but a failing driving within a year was a bit scary.
#Synology cloud station backup too slow update
Update (Aug 1, 2019): My Seagate drives were significantly less than a year old before one disk began failing and the Synology DSM software alerted me to replace the drive. This model has a very easy to access RAM slot - no disassembling the NAS like I had to do with the DS415+. I also added an 8GB stick of RAM (for a total of 10GB). I got two 12TB Seagate IronWolf drives for this (though they do make more expensive 14TB models at this time). 2-bay, dual-core 2GHz, upgraded to 10GB RAMĬombined with the advancement of hard drive storage density over the years I was able to create a larger effective storage array with only 2 mirrored disks.
0 kommentar(er)
