Re: Migrating logs to SAN

In SQL 2008 full-text catalogs can be log shipped or mirrored.

In SQL 2005 this might work as long as the same drive structure is observed, and you have the same database IDs.

"GJP, NY" <GJP, NY@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0A9D4934-F197-4460-8061-E64E39A5A052@xxxxxxxxxxxxxxxx
Our IT department wants to achieve automatic server replication for our SQL
Server host via SAN.

As our server is now configured, all logs are on a local drive, which
creates replicability problems. The server is running dozens of databases
with many, many full-text indexes. We'd like migrate the logs from the local
drive to a SAN device without having to rebuild/repopulate the FTIs, which
would not be a trivial undertaking.

I'm wondering if subscribers to this group have any insight into whether it
would be feasible to:

1) Stop the SQL server
2) Do a bit-level copy of the local drive containing the logs to a SAN drive
3) Assign the local drive a new ID.
4) Assign the SAN device the drive letter previously claimed by the local
drive
5) Start SQL server

It seems that this would be a way to enable SAN-based SQL server replication
without having to tear down and rebuild all our indexes.

.

Relevant Pages

  • Re: Does NTBackup backup SQL Express?
    ... In which case I assume the logs do NOT get flushed so this is not an option ... as I know enough that the logs must be flushed during every full backup. ... and the SBS server I regularly use runs MySQL not SQL ... I've always scripted my SQL Server backups separatly. ...
    (microsoft.public.windows.server.sbs)
  • Missing DLL during re-installation
    ... The installation appeared to complete successfully and I ... SQL Server Setup failed to execute a command for server configuration. ... Refer to the server error logs and Setup ...
    (microsoft.public.sqlserver.setup)
  • Re: Where did the connections come from?
    ... Actually we've seen varioius login failures. ... It would be great for the SQL logs to include the information like ... trusted SQL server connection. ...
    (microsoft.public.sqlserver.security)
  • Re: Are multiple transaction logs used concurrently or sequentially?
    ... The way the SQL Logs work is sequential... ... I support the Professional Association of SQL Server and it's community of SQL Server professionals. ... > It'd be nice to have redundant transaction logs, maybe even one on a> mapped drive, but I read in one post here that SQL Server considers> all transaction logs to be one big log file. ...
    (microsoft.public.sqlserver.server)
  • Re: Migrating logs to SAN
    ... I should have specified that we're running SQL 2000. ... could you amplify how database IDs might come into play? ... Stop the SQL server ... Assign the SAN device the drive letter previously claimed by the local ...
    (microsoft.public.sqlserver.replication)