Best Practices for SQL Server ?

[LVI]

Hello

I am testing to restore a SQL server (Windows 2003/SQL 2000, C: for system and D: for datas)

on a new server which hardware is different from the old.

BESR 7 is used to backup C: and BEWS 9.1 for D: + SystemState on C:

Although I can restore C: on the new server (no driver issue, all is fine) with BESR ;

I can't restart the SQL service because an error message appears, something as

"dependancy issue"

Note that the backup by BESR is made with SQL service running... (surely not a good choice...)

 I tried to desinstall/reinstall SQL Server but it is worse...

Can you tell me what is your "strategy" when you backup an SQL server with BESR, or

which best practices must be applied

Many thanks

LVI

[David_F]

 Backup can be made while SQL services are running, we use VSS to quiet the service long enough for us to take a snapshot. We recommend that both the system/SQL binaries along with its information stores are backup within the same BESR job to stay consistent; which is why I suspect the last restored failed. Be sure VSSADMIN LIST PROVIDERS shows the Symantec provider listed for proper functioning.

[LVI]

Hello David

Thanks for your reply, some of your information sound good !!!

However, about VSSadmin List Providers, I have checked it on some servers

and obtain the same answer :

C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
 

How can I proceed to set it correctly ?

Many thanks

LVI