Idle connections will be closed.' - Retry continually on 'The network connection was lost' error, unless the user clicks 'Stop' Fixed: - Fixed an Arq Pro issue where initialization may not have created the right files in the case of a backup set that's migrated from an older version of Arq Arq Backup Version 7.21.3 Fixed: - Fixed an issue which could cause a "missing backupfolders.json" error if an Arq5-created backup set was adopted, edited, and then a new backup was run - When restoring a single file, create the file without its parent directories - Fixed an issue which caused an "authorization header is malformed" error when adding an S3 storage location Arq Backup Version 7.21.0 Improved: - Added Import and Export buttons for a backup plan's file selections - Added support for new AWS regions - Added "Use Dual-Stack AWS Endpoint" checkbox for AWS storage locations - Added support for Arq Pro - When restoring a folder containing "deleted" items (because "keep deleted files in subsequent backup records" option was checked in the backup plan, don't restore those "deleted" items.
#Arq backup my map file and player password
Arq Backup Version 7.24 New Features: - Added support for backing up to a shared drive in Google Drive - Added support for backing up to any folder in Google Drive instead of only 'Arq Backup Data' Fixedd: - Fixed an Arq Pro issue where an app password was set in Arq but shown as not set in the web console - Fixed an issue which could cause Arq to start, stop, then start the backup plan unnecessarily on the next run after modifications to the backup plan - Fixed an issue which could cause Arq Agent to crash on startup when encountering unexpected configuration files - Fixed an issue which could cause Arq Pro sync to fail when the computer is first added to a group - Fixed an Arq Pro issue which could cause 'encryptedkeyset.dat not found' errors on new backup plans Arq Backup Version 7.23 Changed: - Changed ArqMonitor to show a notification every 8 hours if it can't connect to ArqAgent - Changed timeout for most transactions to storage locations from 20 minutes to 3 minutes - Retry on the very rare AWS 400 error 'Your socket connection to the server was not read from or written to within the timeout period.
0 kommentar(er)
