Windows Server 2008 support for SQL Backup

• 
  I have also performed further minor testing with the new SQL Server 2008 RC0 with Windows Server 2008.
  
  All appears to be OK with the fix I provided in my first post above.
  
  Many Thanks
  Eddie
  
  Eddie Davis
  Product Support Engineer
  Red Gate Software Ltd

  Eddie D June 12, 2008 09:37

  - 0 +
• 
  How about the Clustering for Windows 2008? Is it supported as well? I get the question upon installation to supply the Cluster Administrator and Password; however in 2008, there is no Cluster Administrator.
  
  What would be the best answer for this question if it is supported?

  dbarchitect June 13, 2008 13:07

  - 0 +
• 
  The cluster administrator user was used to connect to the Windows Clustering service, find out which cluster group the SQL Server instance was running in, and create a new cluster resource in that group for the SQL Backup Agent service.
  
  During an upgrade, the cluster administrator user was used to connect to the Windows Clustering service, disable the SQL Backup Agent service, and enable it again after the upgrade was completed.
  
  Thus, you should be able to use any user account that has adequate rights to perform the above tasks.

  petey June 16, 2008 04:15

  - 0 +
• 
  I'm having this exact issue on Windows Server 2008, but the link to the patch doesn't work. Is a patch still available for this issue?

  brundaged July 23, 2008 19:30

  - 0 +
• 
  Sorry about that, the link to download that patch was malformed. I have corrected it. Please try downloading the patch again. Thanks.

  petey July 24, 2008 01:01

  - 0 +
• 
  Hi,
  
  I have (since 01/01/09) had several SQL Backup jobs fail with
  "SQL Backup failed with exit code: 586 SQL error code: 0 [SQLSTATE 42000] (Error 50000)"
  but I am running 64bit SQL 2005 SP2 on server 2003 R2.
  
  Will the same fix be relevant or is this another issue altogether?
  
  cheers
  
  Jonathan

  fatherjack2 January 05, 2009 06:26

  - 0 +
• 
  Hi there,
  
  We are using Red Gate Backup 5.2.0.2824 on a SQL 2008 + Windows 2008 machine and I am getting the error above.
  
  The download link is not working, can i get the patch somewhere and will it install correctly on our version?
  
  Thanks!

  tdpg April 30, 2009 10:00

  - 0 +
• 
  Hello,
  
  Sorry, but the information in this topic is rather out-of-date. SQL 2008 and Windows Server 2008 support is now available in the production version of SQL Backup 5.4. All that you need to do is go to Check fro Updates on the console's help menu and get the free upgrade.

  Brian Donahue April 30, 2009 14:14

  - 0 +
• 
  Hi,
  
  I am having the same issue, running 5.3.0.178
  
  And when trying to upgrade via Help I get the infamous "No updates available".
  The link in the first post is timing out.
  
  What to do?

  audun May 27, 2009 09:21

  - 0 +
• 
  Hi,
  
  I am having the same issue, running 5.3.0.178
  
  And when trying to upgrade via Help I get the infamous "No updates available".
  The link in the first post is timing out.
  
  What to do?

  audun May 27, 2009 09:31

  - 0 +
• 
  Hello,
  
  Since the fix is now incorporated in the 5.4 version of SQL Backup, the patch has probably been removed. If Check for Updates doesn't work, you can still get the full update by downloading the demo version from the website. The demo and the full version are exactly the same: when you enter your serial number, the demo becomes the full version. Please see:
  http://www.red-gate.com/products/sql_backup/index_2.htm

  Brian Donahue May 27, 2009 12:36

  - 0 +
• 
  Thanks.
  
  I was hoping I could upgrade the existing version.
  Will I have to uninstall the existing 5.3 version before installing the new 5.4 version?
  
  Regards,

  audun May 28, 2009 02:18

  - 0 +
• 
  The installation of SQL Backup from our website will upgrade the 5.3 components.

  Brian Donahue May 28, 2009 05:38

  - 0 +
• 
  I have a new Win2008 x64 ENT server with SQL 2008 ENT, installed SQL Backup 5 (5.4.0.55) and when I tried a restore I received the error:
  
  Wrong MDAC version,. Download latest MDAC version
  Server: <Server_Name>.
  Windows authentication
  Failed to connect to SQL Server instance: <SQL Instance Name>
  SQL Backup exit code:586
  
  I suggested upgrading to the current version of SQL Backup but we need to keep the versions matched across all of our servers so that's not going to happen right away.
  Any suggestions on where to go from here?

  Mcassuto August 27, 2009 12:57

  - 0 +

Add comment

Please sign in to leave a comment.