• Brian P
    0
    I’ve been evaluating CloudBerry Backup for Windows Server and plan on purchasing a license. In a low bandwidth environment, which of these approaches is less problematic for file/folder based backups, not images, to Backblaze B2? It’s about 90GB of data on a 2mbps upload.

    1) Continually stopping the files backup plan during business hours and starting it again at night.

    2) Stand up a clone of the file server, using a bare metal restore, to a different location with more upload bandwidth available to perform the initial backup. Once completed, export the Cloudberry configuration to the live server and continue backups from there.

    I’m not sure of the implications for the Repository, synchronization or consistency checks using either approach. Thank you.
  • David Gugick
    118
    You can try this approach using an external hard disk and moving the data to the cloud using site with better upstream bandwidth and then continuing the backups at the slower site: https://help.cloudberrylab.com/cloudberry-backup/miscellaneous/seeding-data/step-1.-backing-up-data-to-external-storage
  • Anton Zorin
    30
    , there are 3 options:
    1. Copy data to another disk and back it up on a faster connection. Once done, sync repo on the computer and proceed with incremental.
    2. Use Backblaze Fireball which is a NAS that you order, upload your data there and send it out to Backblaze.
    3. Configure bandwidth throttling with a schedule to shower it down during business hours and to use the full bandwidth during nights and weekends.

    What's your download bandwidth? Is it enough to restore data in case of a disaster?
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment