New Features
PROJECT-1651: Many improvements have been made to performance and responsiveness when dealing with hundreds of SQL Server configurations.
A limit has been placed on the number of simultaneous backup or restore operations started on each instance, so it is now feasible to start hundreds of operations at once without overloading the system. This limit defaults to 10; if you need to change it, please contact Dbvisit Support.
PROJECT-1834: It is now possible to control whether backup compression is used for the database backups created when initially creating or re-synchronizing a standby database and for the log backups created when keeping a standby database up to date. This feature is only available if the primary SQL Server instance supports it, which is the case for Standard and Enterprise Editions, but not Express or Web Editions.
Improvements
PROJECT-1323:When creating multiple SQL Server configurations at once, validation of custom backup locations could fail, preventing creation of the configurations, even if the locations were valid. This bug has been fixed and creation of the configurations will now succeed.
PROJECT-1330: Memory consumption during service startup has been greatly reduced.
PROJECT-1386:Some minor bugs relating to the scheduled read-only mode feature have been fixed: if the database is offline at the scheduled switch time, a warning event is created; if the Observer triggers an automatic failover while the standby database is in read-only mode, the icon on the dashboard that indicates scheduled read-only mode was left incorrectly activated; if the standby database was already in the target mode at the time of scheduled mode switch, the event incorrectly stated that it had been switched, when in fact it had simply been left as is.
PROJECT-1753:A confusing message related to scheduled read-only mode was added to the end of Graceful Switchover tasks even if the scheduled read-only mode feature was not in use. This message has been reworded to be less confusing and is suppressed when the feature is not in use.
PROJECT-1888:Transaction log backups could fail to be applied when Standby Update Delay is enabled and the SQL Server instance used a non-English default locale. This feature has been fixed to work in all locales.
PROJECT-1892: In rare cases, a transaction log backup could not be read immediately after creation due to an unknown process having to file open. When this happens, the operation is now retried after a short delay.
PROJECT-1905: When there were two standby databases for one primary, and one of the configurations was switched over, transaction log backups could be deleted before being applied to both standby databases. This has been fixed and transaction log backups are now only deleted once they have been applied or transferred for all relevant configurations.
PROJECT-1906: A component process of the dbvagentmanager service could exit unexpectedly shortly after startup if the Control Center could not be reached, potentially causing problems with Automated Standby Update. This has been fixed.
PROJECT-2060: When there were many unapplied transaction log backups on the standby host, a very large number of debug messages were written to the trace log file on the standby host, leading to increased CPU usage. The debug log messages have been reduced in both number and size.
PROJECT-2070: When there were two (or more) standby databases for one primary, and one of the configurations was switched over, events were created saying that Automated Standby Update had failed, even though it was working correctly. These false failure events are now no longer created.
PROJECT-2079 When a large number of configurations exist between a single pair of instances, the button to collapse and expand the instance pair on the dashboard was missing, leaving the configurations permanently collapsed in some cases. This button has been restored.
General
PROJECT-1909: The dbvagentmanager activate command was not working. This command has been fixed. Note that this command (and some others) are deprecated in this release.
PROJECT-2072: The contents of the conf directory from the StandbyMP installation and a detailed listing of all files in the StandbyMP installation directory are now included in all support packages. This will help Dbvisit Support to diagnose problems.
Oracle
PROJECT-2095 Creating a time-based support package for Oracle configurations was not possible when the language was set to Japanese or Chinese due to an issue with time formats. This has been corrected and support package creation is now functional for all languages.
Comments