Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sqltec
Starting Member
3 Posts |
 Posted - 2007-10-16 : 14:48:19
|
| Is it possible to copy the whole MSSQL directory from one server to another without stopping the SQL server service? If not, what errors would occur?Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-16 : 15:10:47
|
| If you are looking for a speedy switch over [Are you?] then there are ways to use Full and Differential (or even Transaction) backups to Prep. a transfer first, and then very quickly transfer just the "changed data" so the downtime is minimal.But that may not be the answer to your question??!!Kristen |
 |
|
|
sqltec
Starting Member
3 Posts |
Posted - 2007-10-16 : 15:15:01
|
| Just to give a little background information what is being done and what I try to do. We tried to set up a standby sql server by cloning of the production sql server. However, on production server, the SQL server was installed partly on C:\ drive (MSSQL\Bin, Instal, Upgrade folders) and partly on F:\ (include Backup, Data, FTDAta, Jobs, log, Repldata folders). the server team was able to clone c:\ partition on the standby server but not F:\ drive. My question is if it is possible for me to copy the remaining of MSSQL directory on F:\ drive from Production server to the standby server without stoping the sql service on the production. Once this is done, we hope the standby server can start up and function like the production server for business continuity in case the production one crashes. Thanks |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-16 : 15:17:13
|
| You will need to use log shipping, replication, or some other tool to keep your standby server up to date.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-16 : 15:30:02
|
| My gut feeling is that it would be better if the two machines were configured the same.Even though you can Log Ship [or whatever] to a server that is set up completely differently, on Disaster Day it will be much easier if you can type "F:" and it behaves the same as the original server.Personally I would change it now, before it becomes "too difficult"Also, if the machines are configured identically you can just copy over the database files to start the Replication / log shipping off. Which is probably going to be easier than a "Restore" route.Kristen |
|
|
|
|
|
|
|
|
Copying MSSQL directory