Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by Sburk

  1. Why does Retrospect not truncate the log when performing a full MSSQL backup? This is pretty standard and is the default in which the local sql agent operates. Is this by design? If so, how can I make the log truncate kick off immediately after performing a full backup? I know the obvious is to schedule a log truncate job right after the Full backup, but that proves tricky since the backups run at a variable duration. Thanks!
  2. Very strange. The only other possible session it could be running in would be the console session. Start > Run > mstsc /CONSOLE or just simply hook a monitor to that system and see if it's running there. I'm out of ideas so I'll leave it to Mayoff.
  3. Sburk

    -1004 (database backup/restore error)

    Welp. I'm trying to defend Retrospect but I'm getting heat from the higher ups that we may need to pursue other options, especially for our SQL backups. Nobody has an idea of what this problem could possibly be caused by?
  4. Try logging into 2 RDP sessions simultaneously of the user running retrospect. Do you see it in either session?
  5. Yeah, I'm assuming you're using Remote Desktop. It must be running under a different session. Try logging into that session and you should see Retrospect running.
  6. I looked in the product announcement section of this forum. There was a broken link there: http://kb.dantz.com/article.asp?article=9729&p=2 Where are the 7.7 release notes? Thanks!
  7. I just recently started to receive these errors upon completion of a MSSQL full backup script. I searched and didn't really find any solid answers to this question. So I'm starting a new thread. I'm running Retrospect 7.6.123 Multi Server. Clients are all 7.5.116. MSSQL Server 2005. Any ideas? "..." represents the database name: - 1/12/2010 2:59:48 AM: Verifying MSSQL_Clients2 Generated MD5 digest for file "..." does not match stored MD5 digest. Generated MD5 digest for file "..." does not match stored MD5 digest. Generated MD5 digest for file "..." does not match stored MD5 digest. Generated MD5 digest for file "..." does not match stored MD5 digest. Generated MD5 digest for file "..." does not match stored MD5 digest. Generated MD5 digest for file "..." does not match stored MD5 digest.
  8. Thanks for all your help guys. This happened for 4 weeks straight. Then it magically resolved itself. What the heck? I verified that nothing was changing in the databases throwing the errors during the entire backup/verification pass. I have no idea what could've caused this. Could it have been from a bad retrospect grooming script or something?
  9. Sburk

    -1004 (database backup/restore error)

    Does anyone have a solution for this? At this point I cannot use Retrospect to backup the databases on this server. I am having to use the SQL Agent directly. Which is a huge hassle. It also makes me nervous if it were to happen on additional servers in the future. Thanks!
  10. I cannot launch retrospect. I run retrospect.exe and nothing happens. Nothing reported in Application or System log either. It appears that backups are still happening in some capacity in the background. Has anyone run into this? My Server is running Microsoft Windows Server 2003 Standard.
  11. Sburk

    Cannot launch Retrospect

    I am running Retrospect 7.6 Launching from retrospect.exe didn't work. Retrospect process was not running in the task manager. I restarted the Retrospect Launcher Service and it worked just fine. Strange thing is that even after a reboot, this was still occurring. Had to manually stop and start the service. Thanks much!
  12. Sburk

    -1004 (database backup/restore error)

    Steve, I am also getting the same error and need help. In my case, I have a named instance on the server. Are you using the default SQL instance or a named instance? I seem to be able to backup databases fine on the problem server. When I go to restore, I get the same error you have. I have tried restoring a database that is stored on the problem server. I have also tried restoring a database from an entirely different server to the problem server. Same result. I'm running Retrospect 7.6. I have several database servers. This is the only one I have issues with, and it is the only one with a named instance. Ideas anyone??!
  13. Still getting MD5 mismatches. This is now occuring in the differential backup script as well.
  14. This particular backup script is not encrypted. I will attempt to backup one of the problem databases. I can't run the entire script because it's way to large to place on local storage. I'll report back with what I find. Thanks.
  15. Any ideas? The errors make me very nervous. What is strange is that I have a differential script that is exactly the same as the full backup script. Points to the same backup sets and everything. The backup sets are NAS devices. The differential script completes with 0 errors.
  16. I have a backup script that basically backs up entire drives on several different computers. I noticed that it was attempting to backup mssql file extensions .mdf and .ldf which is causing roughly 130 errors upon backup completion. I added two exclude by name selectors: *.mdf *.ldf In the operations log it is still showing that the script is attempting to backup files with the above extensions. So, I'm still getting 130 errors upon completion. I have included a couple screenshots of the selector setup....the *.mdf and *.ldf selectors are setup exactly the same. Any ideas ladies and gentlemen? Thanks!
  17. I tried your suggestions and still no joy. Excuse my ignorance, but when I run the "check selector" tool, it appears to just pull up an entire list of the entire source drive. I drill down to find a .mdf or a .ldf and both are still selected. Is this expected??
  18. I'm still getting these errors. Any ideas?
  19. The errors are all ...\mssql\data\filename.mdf: can't read, error -1020 (sharing violation) ...\mssql\data\filename.ldf: can't read, error -1020 (sharing violation) Which I think is by design since the sql server is running. I will give your suggestion on the selectors a shot. I'll know if it worked by tomorrow morning and will report back. Thanks!
  20. Thanks rhwalker! Following the below steps worked beautifully for me. 1) Do NOT enter a new license code if Retrospect is requesting a new code, this will result in the backup copy of the preferences to become overwritten. 2) Go to documents and settings/all users/application data/Retrospect 3) Check the modification and creation dates for the configXX.dat and configXX.bak. If the .bak file modify/creation date matches the modify date for the .dat file, then your backup copy of the preferences has probably been overwritten by the corrupt copy of the .dat file. 4) Rename the configXX.dat file to configXX.old. 5) Rename the configXX.bak file to configXX.dat 6) Launch Retrospect. 7) If Retrospect stops asking for a license code and still contains your custom settings, then you have corrected the problem.
  21. I noticed that retrospect was stuck on 'building snapshot' for one of our clients. I attempted to stop retrospect with no luck. So I rebooted the server. (microsoft fix all) Upon reboot I launched Retrospect to find a "Getting Started with Retrospect" window waiting for me. It is now asking for my application license code. I didn't want to proceed until I know that all of my snapshots and retrospect data have not been lost. What is the solution to this problem? And...what the heck happened? Does anyone know? Thanks.
  22. The default location for retrospect 7.6 catalog files is ..\Documents and Settings\All Users\Application Data\Retrospect which in my case is on the C: drive. I want to move the catalog files to a larger drive which is the D: drive. What is the best way to do this? I have just performed the following. I recently moved Retrospect from one server to another. http://kb.dantz.com/display/2n/articleDirect/index.asp?aid=9526&r=0.3837397 Thank you!
  23. I can't get this to work for the life of me. So, I am just going to move Retrospect to a better server and start from scratch. Sounds bad, but I've already wasted 2 days trying to get the catalog files to work Thanks for your help though!
  24. Sorry but this doesn't seem to be groovy. I copy the catalog files to D:\Retrospect_Catalogs. I double click each catalog file (I only have 4) and retrospect opens the backup set configuration...as expected. I try to view snapshots and nothing is listed. I try to run a backup and it says 'configuration not complete'. Do I need to run a repair on the catalogs or something? Thanks!!
  25. Thanks Russ. You are correct, I was trying to link that KB article you posted. Good to know! So basically I can just put them in D:\RetrospectCatlaogs and then follow the steps in the user's guide that you posted and retrospect will play nicely? Also, just to correct myself above. The default location of the catalog files is actually: ..\My Documents\Retrospect Catalog Files