Jose, have you opened a ticket by chance?

did it make the trick?

Hi Hector,
What is the DB size? We back up MS SQL databases by using native tools to perform a backup to a temporary location and after that processing the output file.
Have you opened a ticket with our support?

Thanks,
Anton

What is the version of the agent you're writing with?
Starting 6.0 agent for windows we support uploads continue in case it was interrupted.

It's safe to delete it. Syncing repository most likely will be required.

Versioning works for updated files, not interrupted uploads.

Thanks,
Anton

Hi Ryan,
Where do you see it no longer checked?
Have you tried to check the endpoint it's connecting to using Wireshark?
Have you reached out to our support team and provided diagnostic into to them about this issue?
Let's first make sure it's taking too the regular endpoint and if so, see why it's happening like that.
With your help we'll have this sorted.

Thanks.
Anton

There are 2 different ways to add local filesystem account.
1. Centrally managed from the web console (on the Storage tab, where you found it already).
2. The second way is to configure it for that specific machine. Go to Remote management page, click on the gear button on the right. Then Edit -> Edit Local Filesystem Accounts.
Here you go.

Hi Jay,
Not to have those limitations in the cloud backup you can use Azure (if you're a Microsoft shop).

From here: https://support.office.com/en-ie/article/invalid-file-names-and-file-types-in-onedrive-onedrive-for-business-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa#filenamepathlengths

In Azure this limitation is 1024 characters:
https://blogs.msdn.microsoft.com/jmstall/2014/06/12/azure-storage-naming-rules/

The NTFS file system actually supports file paths of up to 32,767 characters. There was a limitation of
https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file

Thanks,
Anton

Hi Matthew,
If anything happens to your server you can download Cloudberry Backup on any other server, configure AWS account there and point it to the same bucket where you backed it up and after that, by picking the right prefix from the drop-down menu you will be able to get the list of backed up files and restore some or all of them.
Andy has provided the right link (see above).

Thank you, and for your emails. It's resolved now.
Please feel free to drop me an email or post here if you will see any issues.

You can edit the backup plan to upload files to Intelligent tier from now on and also create a life cycle policy to move objects to Intelligent tier after, say, 1 day.
Once lifecycle policy moves all objects to that tier you can delete it.
Thanks
Anton

Hi all,
Sorry for a late response.

Indeed, last night there was an issue on one of our nodes that affected some customers.
The issue was identified and mitigated.
Currently, we're thoroughly investigating it to make sure it won't appear again in the future.
And of course, we'll make sure that all the numbers reflected in the console are correct.
I'll be updating this thread.

Thank you!
Anton

Hi all,

The SAS (Shared Access Signatures) for Azure storage is now live for the MBS (web portal version 4.4)
https://forum.cloudberrylab.com/discussion/752/mbs-web-console-release-update-4-4-march-5-2019
and supported in our windows agent in 6.0.0.245.
https://forum.cloudberrylab.com/discussion/766/cloudberry-mbs-backup-agent-release-update-6-0-march-6-2019

Before now it worked the following way (and still works for older agents)
Backup Agent in APAC before sending data to the cloud storage in APAC has to sign all requests to the storage on MBS which is located in US East. Considering amounts of data to be transferred it turns to a huge wait.

Now, with SAS backup agents requests a token in our environment in US East and works with the token for a defined period of time of token validity.

For more information about SAS please read here:
https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1

Thank you.

Hi Sephira,
Yes, they will see each other's backups.
What would be the perfect scenario for you?

Thanks

Thank you for the feedback James!
This is something we have on mid-term roadmap. Can't promise any time frame for the update but I will defenitely try to prioritize this task.

5.9.2.22 released (August 3, 2018)

Support for ESXi 6.7
Internal fixes and optimizations.

5.9.1.75 released (July 25, 2018)

Supported Finland Region in GCP

Want to bring some clarity here.
Google's safebrowsing ML (machine learning) model had tripped backup for Office365 and G Suite backup as it had Microsoft and Google logos there (very typical for phishing sites) which has triggered that false alarm.
Now it's whitelisted and the alarm will not longer appear.

4.1.14 (May 24, 2018)

What's new:
- Backup Support Pack
https://mspbackups.com/Admin/Help.aspx?c=Contents/backupsupportpack.html

4607 Added Advanced Rebranding license to the Buy window
4798 RMM page - new menu if to click on gear button

2.4.3.11 (May 15, 2018)

1576 Ubuntu package being installed with incorrect permissions
1516 Backed up file to Oracle can't be restored if compressed
1454 Backup to Oracle Cloud fails -"I dont know this error type" - "Token not found in cache"

2.4.2.7 (May 7, 2018)

1181 MBS backup dialogs rebranding
1404 False Failed status on Backup - reason not logged(?)
1507 Support for new Osaka region in Amazon
988 Ignore icon files in macOS (don't show error)
451 Linux debian 8.0 & 7 support
458 When running 'cbb listPlans' getting: Segmentation fault
462 Backup completed” in Restore plan email notifications
464 MBS mac and Linux - Long passwords not supported
468 Incorrect product name in Applications folder and Menu bar
484 When typing "cbb account -l", typo in error message.
489 Compression does not work on Centos 6 and RHEL 6
496 Wrong elapsed time calculation
530 Add status overdue in reporting if the backup plan is missed for X days (Mac/Linux)
1067 Temporary files created for restore process are not removed if plan is failed
1177 Autoupdate crash on step restart GUI
1498 "Back up symlinks only" doesn't work
1511 File permissions after restore from FS account
1539 Clicking on Legend in Restore Wizard crashes GUI
1543 Memory limit set to 2048 MB or more - is written to config as negative value
1551 Backup corrupted symlink "Specified path does not exist"
1553 Ubuntu package being installed incompletely if Display Name and Product Name are equal
1558 No Legend in restore plan
1564 In CLI Chunk size limit set to 50000 MB or more