CloudBacko v4.1.4 now supports Microsoft 365’s Modern Authentication

CloudBacko v4.1.4 supports Microsoft Office 365 Modern Authentication

Microsoft Office 365’s basic authentication uses a pair of Username and Password for client access requests. This method of authentication presented a method for hackers to¬† use brute force or password spray attacks to hack into users’ accounts. Therefore, to tighten their user accounts’ security, Microsoft suggests their users to enable Modern Authentication, and schedules to:

  1. start disabling Basic Authentication in existing tenants with no recorded usage as early as October 2020; and
  2. disable Basic Authentication for the EAS, EWS, POP, IMAP, and RPS protocols in the second half of 2021.

Starting from CloudBacko version 4.1.4, we support the use of Microsoft Office 365’s Modern Authentication when creating Microsoft Office 365 backup set in CloudBacko Pro and Lite backup software. If users are still using Basic Authentication, we also support that until Basic Authentication is not supported anymore.

Ahsay v8.3.6 supports Microsoft Office 365 modern authentication

If you leave the Username and Account Password fields blank, and just click the Test button, you will be using the Modern Authentication mode, and a browser window will be brought up for you to perform authentication.

modern-authen-04-cbk

After successful authentication, an Authentication Code will be provided to you.

modern-authen-05-cbk

Copy and paste this code into CloudBacko software and the software will be linked with your Office 365 account.

modern-authen-07

You can then proceed with the backup set configuration as usual.

modern-authen-08-cbk

To understand how to create a Microsoft Office 365 backup set to backup emails and files in an Office 365 domain, check out this Microsoft Office 365 Backup and Restore Guide.

in News | 239 Words

CloudBacko backup software version 4.1.4.3 released, with the Support of Office 365 Modern Authentication

CloudBacko v4.1.4.3 released with Office 365 Modern Authentication Support

CloudBacko version 4.1.4.3 is just released, with:

1). Support of Office 365 Modern Authentication

2). Quick Multiple Users Selection in Office 365 Backup Set

3). Enhanced Periodic Data Integrity Check, and

4). VMware Version Check for Changed Block Tracking Issues.

As Microsoft is going to enforce the use of Modern Authentication Method and begin disabling Basic Authentication in existing tenants with no recorded usage as early as October 2020, if you are currently running Office 365 backup sets, you MUST upgrade your CloudBacko Pro / Lite to this version before Basic Authentication is disabled.

For the details, please check out this latest Software Release Notes.

8 Reasons for Using CloudBacko Backup as Carbonite Alternative

Use CloudBacko as Carbonite alternative

Looking for an alternative to Carbonite backup? These are the 8 reasons why you should consider using CloudBacko backup software instead.

1). Bring your own storage

Unlike Carbonite’s backup which limits you to use their own cloud storage, CloudBacko lets you choose your favorite storage listed here as the backup destinations. It can simultaneously back up to multiple destinations, e.g. one to your local NAS and another to Google Drive or OneDrive. Therefore, CloudBacko is much more flexible on storage.

2). No speed limit on upload and download

Carbonite will automatically impose speed limitation after you have backed up a certain size of data. We also found negative comments on their download speed. CloudBacko won’t have such limitation that caps your usable upload and download bandwidth, unless you want to impose speed limitation during certain hours by yourself.

3). Backup all file types

Carbonite has a long list of file types that couldn’t be backed up. While using CloudBacko, you won’t experience such limitation as you can backup all file types with it.

4). Select entire folder to backup

Carbonite basic plan does not allow users to select a full folder of videos to backup, thus you need to select the files one by one. When using CloudBacko, you won’t experience such hassle as you can simply select the whole video folder to backup. With such selection, whenever if you have added new videos to the same folder, those new videos will be backed up automatically without the need for manual selection again.

5). Customizable schedule

Carbonite offers limited scheduling options, while CloudBacko offers much flexible scheduling options, such as per minute, daily, weekly, monthly, yearly. You can also setup multiple schedules for each backup set if needed.

6). Unlimited versioning

Carbonite only keeps the latest 12 versions of your data, while CloudBacko offers customizable versioning options which lets you keep as many versions as needed, as long as you are willing to use more space on the storage end. CloudBacko Pro edition even allows you to set advanced Retention Policy to let you configure how you want to keep the old versions, such as Grandfather-Father-Son retention policy that is commonly used in tape backup implementation.

7). Run on Linux

Carbonite’s client only supports Windows and Mac, not Linux, but CloudBacko Pro edition offers the support of Linux OS.

8). One-Time Payment

Unlike Carbonite’s annual charging pricing, CloudBacko’s pricing is perpetual based, meaning you just need to pay once to buy and own the current version software. The pricing includes software maintenance for the current version that covers Ticket Support and Software Update within this version. When next version released and you want to upgrade, then the upgrade fee will be 40% of the list price of all your software and modules. If you don’t upgrade, you can still use the version that you bought without any problem. Our Pro edition for servers is only US$99 per device (not annual), and the Lite for workstations is only US$25. So, much more affordable in long run than Carbonite’s solution.

Still skeptical? Download CloudBacko and try it now.

 

 

 

CloudBacko Backup Software v4 Supports Office 365 SharePoint, Exchange and OneDrive with an affordable price tag

CloudBacko Backup Software v4 Supports Office 365 SharePoint, Exchange and OneDrive with an affordable price tag

[April 15, 2020] CloudBacko, a fast growing cloud backup software developer targeting small businesses, today announces the release of their fourth generation software. The latest version of their flagship backup software, CloudBacko Pro, now supports Office 365 SharePoint, Exchange and OneDrive backup. Businesses can utilize this tool to automatically back-up mission critical data within their entire Office 365 domain to local on-premise storage, or to other non-Microsoft cloud storage for disaster recovery protection. The solution remains at very affordable price tag for small businesses across the world to use.

“Today, many businesses’ have moved their mission critical operations to the cloud, specifically the Office 365. We’ve received many requests from those businesses, asking for a robust yet affordable backup solution for protecting their Office 365’s data. Therefore, we spent quite some time and effort developing it. Now, it’s finally available for them to use.” said Schubert Chong, the CEO at CloudBacko Corporation.

“Unlike many other backup solution who offer yearly subscription licensing option, our CloudBacko backup software offers one-time perpetual pricing to our customers, meaning they can buy and own the version that they have purchased for lifetime. We believe such pricing model can better fulfill most small businesses’ needs. Especially during this coronavirus outbreak period, we understand most businesses are tight with IT budget. Therefore, we kept the price unchanged while offering more features for businesses to properly protected their IT systems”. Schubert continued.

Besides the enhancement in Office 365, this latest version 4 also comes with the support of Microsoft Exchange Server 2019, SQL Server 2019 and Hyper-V 2019. It also natively supports Wasabi and Backblaze B2 as the cloud backup destinations. These 2 cloud storage provides exceptionally low price for small businesses to store that backup data securely on the cloud.

About CloudBacko

CloudBacko is a cloud backup software vendor specialized in developing cloud backup solution for small businesses. Its price starts from US$25 only for a lifetime ownership of its desktop edition. The Pro edition for administration starts from US$99. Visit CloudBacko website at http://www.cloudbacko.com to download CloudBacko for 30 days free trial. No personal or creditcard info is required.

PR Contact

Ronnie Chan
CloudBacko Corporation
Address: 28/F, Ford Glory Plaza, No.37 Wing Hong Street, Lai Chi Kok, Hong Kong
Web: www.cloudbacko.com

CloudBacko v4 Released with enhanced Office 365, VMware, Hyper-V, SQL, and Exchange Server backups

CloudBacko has just released the long-awaited version 4 today, with these enhancements:

1). Now with SharePoint Online, OneDrive, and Outlook backups with Office 365 module

2). New versions of Hyper-V, VMware, SQL, Exchange Server supported

3). Native Backblaze B2 and Wasabi cloud storage support

4). Enhanced index structure and data integrity verification

5). Support direct selection of UNC path as backup source without the need to map it to a drive letter first

and many more…

Check out the latest Software Release Notes for details.

Hotfix to OneDrive for Business destination “storage quota exceeded” error

If you are using the latest v3.7.0.0 CloudBacko Pro/Lite paid version, or CloudBacko Home and got the captioned error, it’s because Microsoft had changed their API without prior noticing us partners. Now we got their update and thus made a fix for it.

Download the hotfix from here:
http://download.ahsay.com/dev/hot-fixes/37/37010/cb-all-hotfix-task26862.zip

Then follow these steps to apply it to your CloudBacko:
1. Close CloudBacko software interface
2. Stop CloudBacko service
3. Extract the hotfix into your CloudBacko installation folder to overwrite the contents in the existing “bin” folder
4. Restart CloudBacko software

It should fix your problem. If not, please submit a Support Ticket to us thru here:
https://www.cloudbacko.com/en/cloudbacko-advanced-cloud-local-server-workstation-amazon-S3-google-backup-software-ticket-sla.jsp

How to setup SSL connection for OpenStack cloud object storage (Swift)?

CloudBacko backup software allows you to backup data to OpenStack cloud object storage (swift). The article aims to show you how to enable the SSL in OpenStack for your backup users.

If you are new to OpenStack, you should check with their documentation on general setup available at http://docs.openstack.org/

If you already have a running OpenStack, you can follow our steps to enable SSL.

Assumptions:

Here are the OpenStack version used in the following examples:

  • OpenStack Havana Series, Release 2013.2.3
  • Swift version: 2.0.2
  • Keystone version: 0.7.1

Here are the values used in the following examples:

  • OpenStack admin user name: admin
  • OpenStack admin user password: admin
  • Tenant (project) name: mybackup
  • Keystone server IP: 10.7.54.7
  • Keystone user authentication URL: https://10.7.54.7:5000/v2.0
  • Keystone admin URL: https://10.7.54.7:35357/v2.0
  • Keystone admin token: 7b05dab9722d44e7b9a82dc0d1ff74ea

Note: The value of the Keystone admin token can be found in the variable name “admin_token” defined inside the keystone configuration file at /etc/keystone/keystone.conf .

Requirements and preparations:

Please setup the following variables in bash profile and filters in the proxy-server.conf before you setup a tenant (project), user, roles and storage quota etc.

Step 1: Add the environment variable in the .bash_profile

Example (/root/.bash_profile)

----------------------------------------------------------------------------------------------------
    :
    :
  Trimmed
    :
    :
export OS_USERNAME=admin
export OS_PASSWORD=admin
export OS_TENANT_NAME=mybackup
export OS_AUTH_URL=https://10.7.54.7:5000/v2.0
export OS_SERVICE_ENDPOINT=https://10.7.54.7:35357/v2.0
export OS_SERVICE_TOKEN=7b05dab9722d44e7b9a82dc0d1ff74ea
    :
    :
  Trimmed
    :
    :
----------------------------------------------------------------------------------------------------

Please login again for profile to take effect.

Note: The value of the OS_SERVICE_TOKEN can be found in the variable name “admin_token” defined inside the keystone configuration file at /etc/keystone/keystone.conf .

Step 2: Setup SSL connection for keystone and swift

To setup the SSL certificates, edit the file /etc/keystone/keystone.conf

Assume you have valid certificate files in

/etc/keystone/ssl_cert.pem

/etc/keystone/ssl_key.pem

/etc/keystone/cacert.pem

which

ssl_cert.pem is the public key file,

ssl_key.pem is the private key file, and

cacert.pem is the CA root certificate file.

Since the format of the certificate issued by CA may be different, please always check with your CA with the correct instruction on chaining the certificates.

Example (/etc/swift/proxy-server.conf)

----------------------------------------------------------------------------------------------------
    :
    :
    :
  Trimmed
    :
    :
    :

[ssl]
enable = True
certfile = /etc/keystone/ssl_cert.pem
keyfile = /etc/keystone/ssl_key.pem
ca_certs = /etc/keystone/cacert.pem

    :
    :
    :
  Trimmed
    :
    :
    :
----------------------------------------------------------------------------------------------------

Step 3: Restart keystone service

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# service openstack-keystone restart
Stopping keystone:                                         [  OK  ]
Starting keystone:                                         [  OK  ]
[root@os ~]#
----------------------------------------------------------------------------------------------------

Step 4: List existing service and mark down the id for the swift

It is required to use the ‘–insecure’ switch if an untrusted SSL cert is used.

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# keystone --insecure service-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+------------+--------------+--------------------------------+
|                id                |    name    |     type     |          description           |
+----------------------------------+------------+--------------+--------------------------------+
| 5f805cc7df2a43eb90db6fe11ed682f6 | ceilometer |   metering   |   Openstack Metering Service   |
| 3134116675a8420a88ef01cdcb0c8728 |   cinder   |    volume    |         Cinder Service         |
| b703b91737954d01a2d180f6c3d575ba | cinder_v2  |   volumev2   |       Cinder Service v2        |
| cc787cf0258e46d6a342e1502e7bf6be |   glance   |    image     |    Openstack Image Service     |
| b3af7d0a95d34aa7883629df7a7f7f56 |  keystone  |   identity   |   OpenStack Identity Service   |
| 10f1a022ada246138aba5834e3622a91 |  neutron   |   network    |   Neutron Networking Service   |
| 218b5356d65e4d8382297f72d65c8bbb |    nova    |   compute    |   Openstack Compute Service    |
| a809ad43f380400cb55ff2520bb27ab0 |  nova_ec2  |     ec2      |          EC2 Service           |
| 8b517bd82d4345c895384f9596a29880 |   swift    | object-store | Openstack Object-Store Service |
| 11882e74696547b0ba1e4d276074ae37 |  swift_s3  |      s3      |      Openstack S3 Service      |
+----------------------------------+------------+--------------+--------------------------------+
[root@os ~]#
----------------------------------------------------------------------------------------------------

The swift id is shown in bold.

Step 5: List existing swift service endpoints

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# keystone --insecure endpoint-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+-----------+---                     ---+----------------------------------+
|                id                |  region   |    ......Trimmed......    |            service_id            |
+----------------------------------+-----------+---                     ---+----------------------------------+
| 00a39b6e21a24562b470b61a1b82902d | RegionOne |  h                     )s | 218b5356d65e4d8382297f72d65c8bbb |
| 047f9c3dd19743e280a553d8a34a9202 | RegionOne |    ......Trimmed......    | 10f1a022ada246138aba5834e3622a91 |
| 2b89407a81574b2c8f0fdef9eefc507a | RegionOne |                           | 5f805cc7df2a43eb90db6fe11ed682f6 |
| 47b6d5974d744c21a04b6ca2781f57a0 | RegionOne |                        )s | b703b91737954d01a2d180f6c3d575ba |
| 485ba5a748fc4f1e865d08774fae8ff7 | RegionOne |                           | b3af7d0a95d34aa7883629df7a7f7f56 |
| 90bb1d878b7045f086e2ada7ce853308 | RegionOne | ht ......Trimmed...... )s | 3134116675a8420a88ef01cdcb0c8728 |
| 9ac0472cb48f49b3b44cb4e3365be01a | RegionOne |                           | 11882e74696547b0ba1e4d276074ae37 |
| a1af6685d3e04e5fa7b71f6c244f1393 | RegionOne | ht                        | 8b517bd82d4345c895384f9596a29880 |
| a9b9c9fbef6a44669788c1946a3c8e48 | RegionOne |                           | cc787cf0258e46d6a342e1502e7bf6be |
| c370061d0cc64386a470a5a0fb01e424 | RegionOne |    ......Trimmed...... n  | a809ad43f380400cb55ff2520bb27ab0 |
+----------------------------------+-----------+---                     ---+----------------------------------+ 
[root@os ~]#
----------------------------------------------------------------------------------------------------

Lookup the endpoint for the swift service with the service_id=8b517bd82d4345c895384f9596a29880

Step 6: Delete the insecure swift service endpoint

Delete the service endpoint with the id a1af6685d3e04e5fa7b71f6c244f1393 which can be found in the same row in the swift service.

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# keystone --insecure endpoint-delete a1af6685d3e04e5fa7b71f6c244f1393
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
Endpoint has been deleted. 
[root@os ~]#
----------------------------------------------------------------------------------------------------

Step 7: Recreate the endpoint with https:// instead

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# keystone --insecure endpoint-create --region RegionOne --service-id=8b517bd82d4345c895384f9596a29880 
--publicurl 'https://10.7.54.7:8080/v1/AUTH_%(tenant_id)s' --adminurl 'https://10.7.54.7:8080/v1' --internalurl '

https://10.7.54.7:8080/v1/AUTH_%(tenant_id)s'

WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+-------------+----------------------------------------------+
|  Property   |                   Value                      |
+-------------+----------------------------------------------+
|  adminurl   |           https://10.7.54.7:8080/v1          |
|     id      |        fb937c038fd34724bd7415fff3ee7736      |
| internalurl | https://10.7.54.7:8080/v1/AUTH_%(tenant_id)s |
|  publicurl  | https://10.7.54.7:8080/v1/AUTH_%(tenant_id)s |
|   region    |                 RegionOne                    |
| service_id  |       8b517bd82d4345c895384f9596a29880       |
+-------------+----------------------------------------------+ 
[root@os ~]#
----------------------------------------------------------------------------------------------------

Step 8: Setup the /etc/swift/proxy-server.conf for swift

Edit the file proxy-server.conf , add the contents that are highlighted in red in the below example.

Assume you have valid certificate files in

/etc/swift/ssl_cert.pem

/etc/swift/ssl_key.pem

which

ssl_cert.pem is the public key file, and

ssl_key.pem is the private key file.

Since the format of the certificate issued by CA may be different, please always check with your CA with the correct instruction on chaining the certificates.

Example (/etc/swift/proxy-server.conf)

----------------------------------------------------------------------------------------------------
# This file is managed by puppet.  Do not edit
#
[DEFAULT]
bind_port = 8080
bind_ip = 10.7.54.7
    :
    :
    :
  Trimmed
    :
    :
    :
cert_file = /etc/swift/ssl_cert.pem
key_file = /etc/swift/ssl_key.pem
    :
    :
    :
  Trimmed
    :
    :
    :

[filter:authtoken]
    :
    :
    :
  Trimmed
    :
    :
    :
auth_protocol = https
auth_uri = https://10.7.54.7:5000
insecure = true
----------------------------------------------------------------------------------------------------

Step 9: Restart the swift related services

Restart the swift related service after you have modified the config file /etc/swift/proxy-server.conf .

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# swift-init main restart
Signal proxy-server  pid: 17166  signal: 15
Signal container-server  pid: 17167  signal: 15
Signal account-server  pid: 17168  signal: 15
Signal object-server  pid: 17169  signal: 15
object-server (17169) appears to have stopped
container-server (17167) appears to have stopped
account-server (17168) appears to have stopped
proxy-server (17166) appears to have stopped
Starting proxy-server...(/etc/swift/proxy-server.conf)
Starting container-server...(/etc/swift/container-server.conf)
Starting account-server...(/etc/swift/account-server.conf)
Starting object-server...(/etc/swift/object-server.conf)
WARNING: SSL should only be enabled for testing purposes. Use external SSL termination for a production deployment.

[root@os ~]#
----------------------------------------------------------------------------------------------------

Step 10: Test with the swift command

Example

----------------------------------------------------------------------------------------------------
[root@os ~]# swift --insecure stat

       Account: AUTH_49f2482ecff9431bae1d32fa2a004026
    Containers: 8
       Objects: 480
         Bytes: 189030388 
Meta Quota-Bytes: 10737418240
   X-Timestamp: 1412574345.10669
  Content-Type: text/plain; charset=utf-8
 Accept-Ranges: bytes
[root@os ~]#
----------------------------------------------------------------------------------------------------