Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

moving files on log shipping secondary Expand / Collapse
Author
Message
Posted Wednesday, August 13, 2014 8:36 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, September 11, 2014 1:05 PM
Points: 59, Visits: 109
been a while and dont have true test enviornment, but I need to detach the database on one of my seconday receiving log shipping server and move a few of the index files around due to space issue. Wanted to make sure but this action would not break the log shipping change in place would it?
Post #1602773
Posted Thursday, August 14, 2014 1:34 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 2:20 AM
Points: 5,231, Visits: 5,106
As the DB is in no recovery or standby mode you wont be able to alter the file locations without dropping the database.

The only way would be to drop the database, restore it to the new locations with norecovery, restore all the logs up to the latest log and then let it all just carry on.

Don't need to make any changed to the log shipping plan, let the backups, and copy jobs run as normal, may want to disable the restore job until you have finished then re-enable it again.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1603140
Posted Saturday, August 23, 2014 9:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, September 14, 2014 10:52 PM
Points: 1, Visits: 24
Hi, if the secondary log shipping database is too large and take long time to restore and create log shipping again. maybe you can try:
1. Set the secondary to recovery mode (because on stand by mode, you cant exec alter database command)
2. Disable all log shipping job
3. Alter your database to modify path: "alter database
Yourlogshippingdb modify file (name = logicalname, filename = 'newpathofyoursecondarydblocation')
4. Stop sql server service on your secondary log shipping server
5. Move your physical file to new location
6. Start sql server service
7. Enable log shipping job
8. Verify your log shipping db

I've done this on my prod server and it works.

Regards
Post #1606721
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse