Highlighted

MS SQL 2000 backup using BE 2012

Hi,

We have the following details.

Database - MS SQL 2000 SP4 (32bit).

OS - MS Windows 2008 R2 Std.

Now, as BE 2014 is not able to take backup of MS 2000 database server, we went ahead with BE 2012 R3.

We will go ahead with a DEMO first then we will go for Live envt.

As I have checked the BE 2012 compatbilities Docs and found is OK but with a note that we need to install a hotfix.

As I have checked the link as provided in the docs ( Link- http://support.microsoft.com/?kbid=913100 ). and found that the hotfix is for Windows 2003 server (32bit).

Please, guys let me know the possibilities pors and corns of this infra.

Will I need to take care of some cautions any tech note ...best practice

Thanks.

6 Replies

Hi,   the BE 2012 SCL shows

Hi,

 

the BE 2012 SCL shows that Microsoft SQL 2000 SP4 is supported, so no hassles there.

Point #13 in the SCL relating to SQL 2000 SP4 links to the website below:

http://support.microsoft.com/?kbid=913100

thanks!

Do you actually have SQL 2000

Do you actually have SQL 2000 on a Win 2008 R2 server ? If yes, then its not-supported by MS itself - http://technet.microsoft.com/en-us/library/aa176565%28v=sql.80%29.aspx

This in turn means that the

This in turn means that the user's configuration is not supported by BE, although the individual software is supported.

Hi, The Link have the Win

Hi,

The Link have the Win 2003 hotfix..but we are using the Win 2008 R2...

The hotfix itself I have tried but the exe file is not executing...

The file is required for Win 2008 server's version.

 

Thanks.

Hi, I have executed the

Hi,

I have executed the backup of the MS SQL 2000 database.

All the database were skipped with the below errror (Exceptions)

*********************************************************************

Backup started on 8/6/2014 at 4:07:02 PM.
Backup Set Detail Information
Database \master was not found, or could not be accessed.
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).


The item db64.CMCL.CO.IN\MSSQLSERVER\master in use - skipped.
Database \msdb was not found, or could not be accessed.
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).


The item db64.CMCL.CO.IN\MSSQLSERVER\msdb in use - skipped.
Database \MPL_1314 was not found, or could not be accessed.
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).


The item db64.CMCL.CO.IN\MSSQLSERVER\MPL_1314 in use - skipped.

********************************************************************

I have checked the vssadmin and belo wis the output.

with commond "vssadmin list writers" on the MS SQL 2000 server (OS - Win 2008 R2) the output is

*****************************************************************************************************

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {848d338f-7bee-4b62-a0c6-cd3395149212}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {52093e0f-7bc8-4656-b1fa-998c928c3cd6}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {28338dd6-3b3f-4329-8a13-ed2c67be6c24}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {eaa44844-45d7-4ca6-a270-01d59efe9b63}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e68df6d1-4d1a-4e2f-8887-430ce667290c}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {1ebadfbf-3c25-4b03-8cb2-f0c103289585}
   State: [1] Stable
   Last error: No error

 

******************************************************************************

Is the MSDE writers required for taking MS SQL 2000 database backup.

 

Thanks.

 

In case, you have missed what

In case, you have missed what is written earlier, your configuration is NOT supported by both Microsoft and BE