Migiration of DB from one storage sub system to another vendor

DB is 150GB and I cannot take it offline long enough to apply logs to a back up.
I am moving from one sub storage system to another.
Any mirroring ideas?
ThanksNot sure what you mean by applying the logs? You don't need to take sql
server offline to do backups. Mabye these will help:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"eudamon" <max789@.yahoo.com> wrote in message
news:cf4ef727.0401071937.136fb59d@.posting.google.com...
> DB is 150GB and I cannot take it offline long enough to apply logs to a
back up.
> I am moving from one sub storage system to another.
> Any mirroring ideas?
> Thanks|||Standard backs would work, but then I have a existing transactions on one server with sub storage system and a restored back up to a new sub storage system DB. Plus the time is takes to copy a couple 100gb. I was hoping for some way to mirror the existing DB to a new copy on the seperate storage subsystem. Hope this makes sense|||Are you talking about just a one shot deal or do you want to keep the two up
to sync all the time? If so you can use Log Shipping or replication but in
either case you need to get the whole DB there to start and that usually
involves a copy or some sort.
--
Andrew J. Kelly SQL MVP
"eudamon" <anonymous@.discussions.microsoft.com> wrote in message
news:7E1B5A95-DFC2-4A52-958D-3F411F824569@.microsoft.com...
> Standard backs would work, but then I have a existing transactions on one
server with sub storage system and a restored back up to a new sub storage
system DB. Plus the time is takes to copy a couple 100gb. I was hoping for
some way to mirror the existing DB to a new copy on the seperate storage
subsystem. Hope this makes sense|||If your're trying to move the DB files to a new storage system on the same
server then your best bet is to detach/move/re-attach the DB. If you aren't
able to be down long enough to be able to do this I think your only option
is to mess around with filegroups. Create new file(s) in an existing
filegroup on the storage system and use DBCC SHRINKFILE('file_name',
EMPTYFILE) which will move the data from that file to other files in the
filegroup. Or create a new filegroup with new file(s) on the new storage
system and rebuild clustered indexes specifying the new filegroup, which
will cause the table to be moved. You'll actually have to rebuild all
indexes specifying ON 'filegroup' if you use this method.
I don't believe there are any options for mirroring in SQL Server. Maybe a
third-party like Veritas has something that could mirror/unmirror live
volumes.
Mike Kruchten
"eudamon" <max789@.yahoo.com> wrote in message
news:cf4ef727.0401071937.136fb59d@.posting.google.com...
> DB is 150GB and I cannot take it offline long enough to apply logs to a
back up.
> I am moving from one sub storage system to another.
> Any mirroring ideas?
> Thanks