Database Backup in 7

[Mayoff]

Retrospect 7.0.249 for Windows users backing up Microsoft Exchange or SQL data to a disk Backup Set with grooming enabled should only perform Full backups. Users performing Differential, Incremental and Log backups may run into problems where a Full backup is deleted during the automated grooming process and they are left with only Differential. Incremental or Log backups. A Full database backup is required to restore database data. This bug will be resolved in the next update to Retrospect 7. Until this issue is resolved, we recommend turning off Backup Set Grooming if you perform anything other then Full database backups. We expect this issue to be fixed with a Driver Update in the near future.

[Mayoff]

Hello,

 

Earlier today EMC Dantz released a major update to Retrospect 7.0. This new 7.0.265 version contains the following changes and is highly recommended for all Retrospect 7 users. To download this update, please visit http://www.dantz.com/updates

 

In addition to the 7.0.265 update, EMC Dantz has released a new Retrospect Driver Update (7.0.3.101) also available at the above web address.

 

A list of changes can be found below:

 

Grooming database backups: This build of Retrospect fixes a problem with the grooming of SQL and Exchange database backups to disk Backup Sets.

 

Assertion failures: When Retrospect encounters a serious error, it crashes and display an assert dialog. EMC Dantz has addressed the following asserts based on reports from Retrospect users:

 

Assertion failure at "arc.cpp-2951"

Assertion failure at "module.cpp-460"

Assertion failure at "scsitools.cpp-503"

Assertion failure at "provider.cpp-989"

Assertion failure at "scsitoolsntpt.cpp-1962"

Assertion failure at "tstring.cpp-2183"

 

Catalog out of sync: In some situations, Retrospect was reporting "Catalog out of sync" errors for disk Backup Sets with grooming enabled. This has been fixed.

 

Grooming and password protection: Retrospect is now able to groom password-protected disk Backup Sets (but not encrypted Backup Sets).

 

Validating scripts: Under certain circumstances Retrospect was erroneously reporting "Media for script scriptname unavailable" when checking media using the Automate>Manage Scripts command. This has been fixed.

 

Hanging on launch: Certain backup computer configurations were causing Retrospect to hang when it was launched. This problem has been fixed.

 

Backup Wizard script destination selection: When creating a backup script using the Backup Wizard, you can choose "Backup now" from the summary screen to run the script immediately. If there are multiple destination Backup Sets available, a drop-down menu allows you to choose which Backup Set to use. Previously, Retrospect always used the first Backup Set in the list, no matter which one you selected. Now Retrospect correctly uses the Backup Set you choose from the list.

 

Retrospect Single Server and Exchange mailboxes: Retrospect Single Server with the Exchange Database/Mailbox Add-on is now able to add Exchange mailboxes to an Exchange Server that is logged in as a Retrospect Client.

 

Can't grant necessary user privileges: Previously, Retrospect reported this error when trying to run as a specified user on a Windows NT 4.0 Secondary Domain Controller. This is no longer the case.

 

Exporting the Operations Log: When the "Export the backup report and operations log" preference is selected, Retrospect exports the entire Operations Log to the file "operations_log.utx". Previously, Retrospect only exported the Operations Log for the most recent operation.

 

Resource in use errors: This version of Retrospect addresses some situations that were incorrectly generating error -843 (resource is in use by another operation).

 

 

Thank you

 

EMC Dantz