And, despite the choice of “Incremental” backup strategy, it attempts to start over from the beginning each time, and hence never completes. Timvracer and mkrosse: I was wondering if either or both of you are actually having success with the out-of-the-box configuration of recurring incremental Cloud backups to S3 of large data volumes (100s of GB and 10,000s or 100,000s of files)?Īs described in another forum post (under the “My Cloud Mirror” section, but I understand the devices may share the same firmware), myself and some others are finding that each backup run fails after uploading a reasonably large number of files. You can change the folder storage class to “infrequent-access”, and that should change all the files/folders within it to that storage class. So for now, after your backup completes, select each folder created underneath your bucket (I run several distinct backup jobs, so I have distinct backup folders created under the main bucket) and select PROPERTIES.

However, this would require WD to alter the firmware to support this option. Unfortunately, I don’t see any way to set the default for new files uploaded to “infrequent-access” in S3, but do believe the API supports the default setting.

Using Infrequent-Access Storage option (saves many $$) .You can create a bucket specific for your NAS backup, and then create other buckets for other purposes. In the S3 dashboard, when logged an on the S3 dashboard, when you are on the “All Buckets” screen, you need to create a top level bucket here, an that is the name you use. I was also getting a failure because I was trying to specify a folder like “bucket_name/folder-name”. Remote Path - it was not clear to me what this is, but it is in fact simply the name of the TOP LEVEL bucket you create (indeed, there is only such a thing as a top-level bucket, within a bucket you can have folders). Since there is also a private/public key pair option with S3, this can be confusing Simply use the Secret Access Key for the Private Key. The WD app asks for “Access Key” and “Private Key”, but you will see that Amazon will create an Access Key and a Secret Access Key.

To get S3 access working, a few tips that are not well done in the documentation.

S3 glacier for personal backup