• January 25, 2020, 02:51:31 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: AWS S3 backups  (Read 2838 times)

jurs

  • Level 1 Member
  • *
  • Posts: 1
AWS S3 backups
« on: November 21, 2013, 01:11:48 AM »

Just bought the DNS-320L beacuse of the AWS sticker on the package.

Now the problem is, the S3 backup feature does not seem to function as I want it to even though the documentation claims something else: "Choose Incremental Backup to write over files with source files that are newer than the target folder files." Contrary to the help documentation, when I choose Incremental backup, in every backup the NAS writes a new directory in S3 (named like '<folder>_20131121090021')!

What I wish to do is to make an rsync-type incremental backup in S3 - to update only the files that have been changed, created or deleted. As you probably know, one has to pay for data transfer between the NAS and S3, so I want to keep the network traffic at minimum - i.e. not to upload my large photo and video archive unnecessarily to S3 every night or so.

I also have versioning enabled in the S3, so once a file is written in S3 (or deleted from there), I will still have access to that file from the versioning history. This S3 feature rules the 'overwrite everything' option out, as I don't want the S3 data multiplying every night, and thus multiplying my S3 bill.

Is this a bug, a feature, or am I doing something wrong?

Oh, and the S3 backup feature shows an error every time when I create a new backup plan, keeping the daily back time at 0.00 am, and that definitely is a bug!

Cheers,

Joni
Finland, Europe
Logged

pittnuma

  • Level 3 Member
  • ***
  • Posts: 107
    • Yorkshire Gliding Club
Re: AWS S3 backups
« Reply #1 on: December 11, 2013, 12:26:18 AM »

I don't think that software has ever properly worked, I have never been able to get it to accept a user, the backup fails because it can't logon.
Logged
Learn from the mistakes of others. You won't live long enough to make all of them yourself.