Jump to content
NAKIVO Community Forum

Recommended Posts

Hello,

I'd like to inquire what the best way is to set up backup to cloud - Amazon S3.

I don't have much Amazon S3 experience but would like to keep the backups fast & the cost low, and I'm not sure how to proceed.

* If I set up backup with incrementals & weekly full backups, my S3 costs will surely be low because I don't download anything.  However, my weekend backups will be fulls and take considerable time.  Correct?

* If I set up backup with incrementals & synthetic fulls, does that work well with S3?  Will my backups be faster or will S3 use my local transporters to merge the backups and create high costs due to downloading from S3?

* In a local test (not to S3) I saw that backup copy jobs ignore the synthetic setting and revert to full backups - in normal backup jobs it works.  Is this true for S3 also?

I'd love to read some advice from people running backups to S3 at this moment so I make the right choice?

Thanks!

 

  • Like 1
Link to post
Share on other sites

@TonioRoffo Hello, Thank you for getting back to us! 

If I set up a backup with incremental & weekly full backups, my S3 costs will surely below because I don't download anything. However, my weekend backups will be fulls and take considerable time. Correct? >>>>> yes, this is correct.

If I set up a backup with incremental & synthetic fulls, does that work well with S3?  Will my backups be faster, or will S3 use my local transporters to merge the backups and create high costs due to downloading from S3? >>>>> With S3, we highly recommend using Active full backups:

- With Synthetic full, there will be read operations from S3 -> increasing of costs.

- Simultaneous read/write operations with S3 during Synthetic full backups show significantly lower performance than during Active full backup.

To create a Synthetic Full backup, NAKIVO needs to read repository data, create full backup locally on a transporter and write it to S3.

In a local test (not to S3), I saw that backup copy jobs ignore the synthetic setting and revert to full backups - in normal backup jobs, it works. Is this true for S3 also? >>>>>

Please clarify your test in detail, as I do not completely understand what was done/compared. Using a few separate repositories/jobs, they have completely independent rules for full/incremental backups. The best solution for you would be to create and send a support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) to support@nakivo.com for further investigation of the issue. Thank you for understanding.

Link to post
Share on other sites

Thank you,

I understand that Active full will be needed for cloud backup.

This impacts my use case for Nakivo for clients that are on a smaller budget, which do no have the upload capacity for full active backups.

I'm hoping someday the "Forever incremental" method will be changed or leveraged to be able to be used with S3 compatible storage (if needed, with a transporter on EC2 doing the work)

It's so much more effective to store data in the cloud in this way.  Backup software (non virtual machines though) with similar storage formats do run in the cloud well (Like duplicacy for example)

Thank you.

  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...