Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About KenBrey

  • Rank
  1. Cannot Authenticate to SQL server

    The correct version is posted above. It is 8.05.2004, The others don't work. http://www.microsoft...s.aspx?id=24793
  2. Problems with transferring SQL database backup sets

    I discovered that the confusion is caused by an alphetical dependency between the backup sets. When a log DB set is transfered, the backup set referred to by the destination log backup will be the backup set listed first alphetically. For instance: If I first perform Full and Log backups to the backup set Original, then: When I transfer that backup set to the set Copy, the transfer works properly. The log backup in Copy only refers to other backups in Copy. However, now the log backups in Original also refer to backups in Copy. When I transfer the Original backup set to ZzzCopy, then the log backups in ZzzCopy refer to ZzzCopy and to Copy If I subsequently transfer the backup set from Original to NnnCopy, the log backup in NnnCopy refers to NnnCopy and to Copy. This points to a valid work-around for the case where there is only 1 destination backup set: Make sure that the destination backup set's name is alphetically lower than the source set. Then the transfered set will work properly.
  3. I have a critical DB backup job that I would like to periodically test by restoring the most recent backup to a different SQL server. Retrospect has the ability to script a DB restore, however a static backup instance must be selected. I would like the script to select only the database, and have an option to select the most recent backup of that DB for restore. You do a similar thing for transfering snapshots. Please implement the same for restoring databases.
  4. Problems with transferring SQL database backup sets

    Furthermore, I think I found the cause of some of the "Can't Transfer Intermediate Databases" error. The problem is that if you do enough backup set transfers, eventually backus in the source backup set may point to predicessors in a destination backup set. This is the case here in this image of the Properties of one backup on the Database Backup History report. The backup set, SQL Server 2008, is the source set for all backup set transfers. And it is the destination for all full and log backups of the database. However, after a backup set transfer the history now includes a log backup on another backup set. If I try to transfer this backup set again using the Transfer Intermdiate Databases option, I will get the Can't Transfer Intermediate Databases error. This condition is intermittent.
  5. Problems with transferring SQL database backup sets

    Robin, I just installed Multiserver 8.5.0(136) and was able to demonstate a problem with a simple test. I chose a very small DB, and created 2 new disk backup sets, one called Original and the other called Copy. I performed a Full backup of my DB to Original. Then I performed a Log backup to Original. A quick test of Restore Database shows no problems. If I restore the log backup, it selectes both the log and the full from Original. Next, I performed a Transfer Backup Sets from Original to Copy. I can restore just fine from the Full backup on Copy. But if I try to restore from the Log backup from Copy, it will select the Full backup from Original, and the Log from Copy. If Original weren't available, I could not restore the Log backup. I would be out of luck, even though the full backup I need is right in the same backup set. When a backup set transfer if performed, it should switch the predicessor backup to the destination backup set instead of retaining the original backup set. Otherwise the entire transfered backup set is useless.
  6. Problems with transferring SQL database backup sets

    (using Retrospect MultiServer 8.2.0 (177)) I am seeing the same issue as Servei. When I use the option "transfer intermediate databases", I also get the same error message, "Cannot Transfer intermediate Databases ... Database Backup History Unavailable". If I turn this message off, I can transfer without errors. I attempted to restore a database from my destination backup set. I selected one of the logs for which I recieved an error. Both backup sets, the source and destination, contain the full backup and all log backups up to the one selected. When I chose to restore from the latest log backup on my destination set, it chosses additional log backups and the full back from the source set. The restore completes successfully. However, if I forget my source backup set, simulating the disaster where only my destination backup set survives, and then try to restore my latest log backup, it does not select the full backup or preceeding log backups. Consequently, it does not allow me to restore my DB backup. This indicates the error message I am seeing is real, and not to be ignored by turning off the "transfer intermediate databases" feature.
  7. Cannot Authenticate to SQL server

    I found a more recent version at microsoft. 8.05.2004 http://www.microsoft.com/en-us/download/details.aspx?id=24793 This allows me to connect.
  8. Cannot Authenticate to SQL server

    I now get an error: R6034 An application has made an attempt to load the C runtime library incorrectly Another KB article, http://retrospect.com/en/support/kb/r6034, indicates this is due to the wrong version of 2005 compatibility. However, the article doesn't give any useful solution. I get this error on retrospect program load, and about 3 times when I attempt to set login info for the DB server in retrospect. If I unlicense the DB server, then I don't get the message. According to Programs and Features, I am running MS SQL Server 2005 Backward compatibility version 8.05.1054.
  9. Cannot Authenticate to SQL server

    I found a more recent link: http://www.microsoft.com/en-us/download/details.aspx?id=15748 It has the file SQLServer2005_BC_x64.msi which installs.
  10. Cannot Authenticate to SQL server

    Mayoff, Thanks for your help. I found a link in the knowledgebase article, however it applies to SQL Server 2008. The KB link is here: http://retrospect.com/en/support/kb/sql-2008-databases-do-not-display-in-retrospect-7-6-and-later-windows and it links to this MS download: http://www.microsoft.com/en-us/download/details.aspx?id=6375 Within that download is the SQL server 2005 backward compatibility module: SQLServer2005_BC.msi However, this module does not want to install on Windows Server 2012. Can you point me to the correct link?
  11. I have a new installation of SQL Server that I can't get retrospect to authenticate to. I have installed the latest version of Retrospect: 8.2.0(177) My SQL Server version is 11.0.3128. I have attempted all three authentication options, and have confirmed that I can connect to the DB using SQL Server Management Studio with either the domain or SQL users and passwords that I am using in Retrospect. Why won't it connect?
  12. Lennart, Good thought, but the servers involved are connected by full Gigabit connections to the same managed Gigabit switch. I have even confirmed the connection speed in the switch's port status display. Other network operations, such as FTP go much faster. I can FTP between them at 3660 MB/min (488 Mbps).
  13. I use Retrospect 7.7 Multi-server and am transitioning to a more virtualized server architecture. Currently, about 6TB of files I keep backed up with Retrospect are on network iSCSI drives attached to the server with my LTO tape drive and local disk backup volumes. Incremental backups are painless and Retrospect can backup at a rate of up to 4000 MB/min. I would like to move the iSCSI volume and the file server responsibility to a virtual server, but the virtual server won't have direct access to my tape drive and will have only network access to the disk backup volumes. I have found that backups over the retrospect client top out at about 400 MB/min and I'm not sure what the bottleneck is. All network connections are Gigabit, and CPU usage is low on both the Retrospect Server and the Retrospect Client. How can I increase the speed of Retrospect Client backups?
  14. blm14, I am using 7.7.620. I was able to resolve the issue by re-cataloging the destination tape set. After that it let me add more data to it again.
  15. I am attempting to perform a transfer of an old backup set to new media so I can decommission my old tape drives. I have already transfered about 6 sets to my new set. My destination tape set has just one member, and it is in the drive and succeeds when I perform a Media Verification on it. However, when I attempt a transfer to it again, Retrospect asks for #1 of my destination set, even though it is in the drive. It does not want to proceed with transfer. Any ideas?