Jump to content

AmyJ

Members
  • Posts

    4,843
  • Joined

  • Last visited

Everything posted by AmyJ

  1. Go to Configure > Backup Sets > Properties and look at the Sessions. This will show you exactly which files were backed up in each time the backup ran.
  2. Add the backup set to your list of destinations, and then edit / update your script schedule. You will need at least two schedules in your script - one for each set. For example: Normal backup to Backup Set A every 2 days starting on Monday Normal backup to Backup Set B every 2 days starting on Tuesday
  3. With SQL there absolutely should be error messages in the SQL Logs in the Management Studio because Retrospect gets the errors from SQL. There will also be errors in the Windows Event Application Log. Make sure you are checking the logs on the destination SQL Server. I just ran some backup and restore tests on new databases with "Full Text Indexing" enabled and had no issues with restore. Make sure you're setting a valid restore path in the restore options if not restoring back to the original server
  4. I couldn't tell from the question whether you're asking on how to exclude files greater then 2 gig or how to limit the backup of all files (total copied) from a client to 2 gig. Here is the answer to both: You can create a "selector" to exclude files greater then 2 gig from being copied. You cannot set a limit not to backup more then 2 gig total from a client. Retrospect would not have any way to determine which 2 gig to backup. What if the backup stopped at 2 gig because there were large video files, but did not yet get to the mail file? The best way to pare down the amount of data to backup is to either use subvolumes, selectors or a combination of both. When used properly they give you a great deal of control.
  5. This issue has been reproduced in house. We will be investigating possible solutions. Thank you for all your information.
  6. Check the SQL Logs in the Enterprise Manager to see if there is any additional error information. Are you restoring back to the same version of SQL? To be clear, you have other databases that have no errors on restore? Are they SQL default system databases, or were they created by you or by another application? It would be helpful to note configuration information: OS version(s), Retrospect version(s), SQL version
  7. Recognition was added for the drive. It has not been tested and, while it should work, is not officially supported at this time.
  8. To backup SQL you will need either the Open File or SQL add-on. To restore with the SQL add-on use "Restore Database"
  9. You'll need the "Advanced Tape Support" add on to backup to multiple tape drives simultaneously.
  10. It sounds like there may be a problem with the account you are using with Retrospect. Try going to Configure > Preferences > Security and use a different administrative user account.
  11. You will need to upgrade to Professional edition to use Selectors. Express is geared towards full volume backup.
  12. With these kinds of errors there should be messages in your Event Logs. We're getting these errors returned from the Exchange API. Check the Application Log for information. Also, try a different user account for login with Exchange.
  13. Per the Read Me this Driver Update adds new device support only. We expect to have a release out soon to deal with the -1012 error.
  14. Please see the following link for assert troubleshooting: http://kb.dantz.com/article.asp?article=6306&p=2 You can also go to http://kb.dantz.com/ and click on Solution Finder for a mini troubleshooting wizard.
  15. It is not possible to delete multiple snapshots at one time. You can, however, turn off "Matching" in your script options to make sure all files are backed up again.
  16. AmyJ

    VolSnap Error

    The errors you are getting are related to the Volume Shadow Service (VSS). This is a Microsoft service that Retrospect calls to backup open files. You should consult the Microsoft Knowledgebase for troubleshooting VSS errors.
  17. The configuration files are held in the default location for such data in Vista: C:\Program Data\Retrospect Program Data is a hidden folder - you'll have to set the option to "Show hidden files and folders"
  18. What is the exact version number of Retrospect? 7.5.xxx? What are the xxx's?
  19. It sounds like you may have some corruption in the affected mailboxes. Try this fix on one mailbox and see if you are then able to back it up: http://kb.dantz.com/article.asp?article=8013&p=2 If so, you'll need to apply the fix to all mailboxes generating this error.
  20. See the following KB article: http://kb.dantz.com/article.asp?article=5395&p=2
  21. You should check your Event Logs for additional error information. Additionally, it sounds like a reboot is in order when possible.
  22. Permissions problems will definitely cause the issues you are seeing.
  23. Please see if new configuration files resolves the issue. Go to: C:\Documents and Settings\All Users\Application Data and rename the Retrospect directory. Launch Retrospect, enter your license code(s) and see if you are able to access Exchange without the assert. Also, provide the version of Exchange.
  24. The error -540 will be addressed in the next update. We don't have an availability date, but hope to have it out soon.
  25. The System Volume Information folder contains snapshots for the Microsoft Windows System Restore feature. They can be omitted if you do not use this functionality, or the feature can be turned off in the System Properties box.
×
×
  • Create New...