Page History
...
- After registration, SQL Safe Web Console will list all available instances in your repository. Users have to use the options to Bulk Edit credentials to change credentials for those instances they are not able to monitor
- Users should take into account that time fields for the Policies, Operation History, and Databases tabs in the SQL Safe Web Console are currently expressed in the GMT time zone.
- When uninstalling SQL Safe, users may need to reboot their computers to remove the SQLvdb Filter Service.
- The SQL Safe Web Console is not currently sending e-mail notifications for Restore Operations
- Agent deployment service account changes made in desktop console in the desktop console are not replicating in web consolein the web console.
Known issues for 8.0
- To upgrade from build 8.0.0.423 to Hotfix build (8.0.0.503) users need to follow these steps:
- Open the installer to prompt the upgrade.
- Type the credentials for the newly created SQLsafe REST service.
- When upgrading the instance of SQL Safe, the installer displays the value to be added to the location property.
- Access the web application. When an "exception" message is displayed, select the option "Redirect me to Dashboard."
- Go to the Administration tab of the IDERA Dashboard, select Manage Products, and edit the respective SQL Safe instance. In the Location field, add the value specified during installation.
- Restart the IDERADashboardCoreService (Automatically the IDERADashboardWebAppService service is restarted.)
- After registration, SQL Safe Web Console will list all available instances in your repository. Users have to use the options to Bulk Edit credentials to change credentials for those instances they are not able to monitor.
- Users should take into account that time fields for the Policies, Operation History, and Databases tabs in the SQL Safe Web Console are currently expressed in the GMT time zone.
- The Progress bar of the Operation History tab in the SQL Safe Web Console does not update its progress during the operation execution.
- When uninstalling SQL Safe, users may need to reboot their computers to remove the SQLvdb Filter Service.
- The SQL Safe Web Console is not currently sending e-mail notifications for Restore Operations.
- When uninstalling SQL Safe, users should manually remove the product from their IDERA Dashboard before rebooting their system.
- Users who plan to install Safe 8.0 on the same system as VDB should obtain the VDB 2.1 buddy drop which addresses compatibility issues between the two products. Please contact IDERA Support for more information.
- After installing SQL Safe, existing virtual databases may not be accessible. IDERA recommends to first upgrade with the VDB 2.1 buddy drop, unmount virtual databases, install SQL Safe, and then recreate the respective VDBs. Contact IDERA Support for more information.
...
SQL Safe 7.0 Beta hydration appears to stall at 99% complete when restoring databases that contain read-only file groups. SQL Server triggers InstantRestore hydration when it performs read/write I/O on the database files. Because SQL Server does not perform read/write I/O on the read-only files, hydration does not begin. Eventually, hydration begins when SQL Server performs read I/O on the files. You can deleted delete the database if you experience this issue.
...
The SQL Safe Backup Agent may stop unexpectedly and SQL Safe displays an error similar to, ".NET Runttime Runtime version 2.0…-Fatal Execution Engine Error." Microsoft recommends that users make sure that their environments include the following patches:
...
SQL Safe 7.0 Beta hydration appears to stall at 99% complete when restoring databases that contain read-only file groups. SQL Server triggers InstantRestore hydration when it performs read/write I/O on the database files. Because SQL Server does not perform read/write I/O on the read-only files, hydration does not begin. Eventually, hydration begins when SQL Server performs read I/O on the files. You can deleted delete the database if you experience this issue.
...