QNAP NAS Community Forum

• Added support for IBM Cloud.
• Added support for Amazon S3 Transfer Acceleration.
• Added a multi-cloud storage function for cloud jobs.
• Added "US East (Ohio)" as a region for Amazon S3.
• Google Docs files can now be converted to Microsoft Office formats.
• Added synchronization support for shared Google Drive accounts.
• For ARM models: Added support for multi-version backup to cloud storage accounts.

• Fixed an issue that prevented the setup of RTRR connections.
• Fixed an issue that caused one-way sync jobs with OneDrive and Dropbox to fail.
• Fixed an issue that caused backup jobs with Amazon Glacier and WebDAV to fail.
• Fixed an issue that caused real-time two-way sync jobs with Amazon Drive and Box to fail.
• Fixed an issue that caused RTRR backup jobs using SSL connections to fail.
• Fixed an issue that caused rsync to fail.
• Fixed some issues found in specific cloud sync jobs.
• Fixed an issue that prevented HBS from resolving conflicts according to the conflict policy for cloud two-way sync jobs.
• For ARM models: Fixed an issue that prevented users from enabling multi-version backup.

• Improved the rsync server and storage space settings.
• Improved the Microsoft Azure settings.
• Improved the job creation process.
• Improved the job notifications.

Bob Zelin wrote: ↑Tue Sep 03, 2019 5:48 am
P3R is one of the best people on this forum - I would like to know why you find this version terrible.

Bob Zelin

1. Not all existing jobs from previous versions will work after the upgrade. I had a versioned job that failed. Making sure conversions of existing jobs work should be one of the first and most important things to test I think.
2. It look like they broke backward compatibility with older HBS versions. I'm not completely sure about this yet, it may change when support get back to me on #1.
3. Creating a versioned backup job now forces the use of QuDedup. Existing converted jobs will still work the way they used to but I can't change anything in them or create new jobs working the way they used to. One consequence of this is that everyone that have used versioned backups will have to reinitialize that and throw their old versioned backups (which could be 6 or more months of backup) away when they need to change anything! In my opinion one of the greatest advantages with the previous HBS versions was that it didn't have a proprietary backup format locking the customer in. That have now changed...
4. They've now limited the allowed characters in job names and if you use one of the now banned characters in a converted job you now need to change the name if you want to change anything else in the job.

P3R wrote: ↑Tue Sep 03, 2019 7:58 am @Bob Zelin,

1. Not all existing jobs from previous versions will work after the upgrade. I had a versioned job that failed. Making sure conversions of existing jobs work should be one of the first and most important things to test I think.
2. It look like they broke backward compatibility with older HBS versions. I'm not completely sure about this yet, it may change when support get back to me on #1.
3. Creating a versioned backup job now forces the use of QuDedup. Existing converted jobs will still work the way they used to but I can't change anything in them or create new jobs working the way they used to. One consequence of this is that everyone that have used versioned backups will have to reinitialize that and throw their old versioned backups (which could be 6 or more months of backup) away when they need to change anything! In my opinion one of the greatest advantages with the previous HBS versions was that it didn't have a proprietary backup format locking the customer in. That have now changed...
4. They've now limited the allowed characters in job names and if you use one of the now banned characters in a converted job you now need to change the name if you want to change anything else in the job.

#1 and possibly #2 are very bad. #3 is a disaster and #4 is time consuming and annoying.

I'm reluctant to change anything now in HBS while I wait for support to get back to me so I haven't used it very much but on the plus side I noticed that scheduling have been improved and that's great.

Of course the addition of QuDedup is a fantastic improvement for many users but make it optional and don't take existing functionality away from us!

nslookup myhost.myqnapcloud.com
Non-authoritative answer:
Name:    myhost.myqnapcloud.com
Addresses:  2a02:101:1011:101:101:1111:1111:1111
                  92.49.13.191

nslookup myhost-ipv4.myqnapcloud.com
Non-authoritative answer:
Name:    myhost-ipv4.myqnapcloud.com
Addresses:  92.49.13.191

nslookup myhost-ipv6.myqnapcloud.com
Non-authoritative answer:
Name:    myhost-ipv6.myqnapcloud.com
Addresses:  2a02:101:1011:101:101:1111:1111:1111

alokeprasad wrote: ↑Tue Sep 10, 2019 8:54 am "Creating a versioned backup job now forces the use of QuDedup"

I upgraded to HBS 3 and my BU of my NAS (with versioning) to attached USB seems to be working.

I'm not aware that I'm using QuDedup. How do I verify that everything is working as it should be?

PS: How do I selectively delete some of my older incremental backups? In Filestation?

Toxic17 wrote: ↑Fri Aug 30, 2019 11:21 pm [*]For ARM models: Added support for multi-version backup to cloud storage accounts.[/list]

ebf82 wrote: ↑Tue Sep 10, 2019 4:28 pm Now, is there any way to backup individual files within a folder?

I've got folder "example" that contains a file (or a few files) that I want to do incremental backups for but they don't show. Selecting the directory they're in forces you to backup all subfolders too.

P3R wrote: ↑Tue Sep 10, 2019 2:15 pm
I edited my job (changed the start time) and QuDedup option was still greyed out.Not enabled. No change.
Maybe because I don't have any SSD's? It says that an x86 based system w SSD is recommended for Qudedup.

I formatted my USB drive a few days ago and started over. Thus the short history of past backups.