Ran out of space on secondary server

Question

Post reply

Ran out of space on secondary server

vsm198

Old Hand

Points: 340
More actions
July 1, 2010 at 2:14 pm

#387265

Hello Gurus
Please advice ASAP
Ran out of space on secondary server. What need to be done immediately. The databses on this server are participating in log shipping. How should I gain back space.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Jason Messersmith SSC Eights! Points: 824 More actions · Answer 1

Take a look at the database sizes, if it has a lot unallocated shrink it. If the log file is huge take a backup.

vsm198 Old Hand Points: 340 More actions · Answer 2

this is a secondary server, databses are in stanby/read-only mode, how can we shrink.

Jason Messersmith SSC Eights! Points: 824 More actions · Answer 3

vsm198 (7/1/2010)
this is a secondary server, databses are in stanby/read-only mode, how can we shrink.

I think you can shrink the primary database and it will shrink the other database.

Steve Jones - SSC Editor SSC Guru Points: 736162 More actions · Answer 4

You likely need to also add space. Shrinking is a temporary fix. As data grows, reindexes, etc., the files will grow again.

george sibbald SSC Guru Points: 104210 More actions · Answer 5

If you ran out of space on the secondary but not the primary sounds like they are not sized the same, they really should be.

For what its worth a shrink of the databases on the primary will be carried over to the secondary. However unless you use the truncateonly option in the shrink you will fragment the data in your database and you don't want to do that. As Steve said they will only grow again anyway.

---------------------------------------------------------------------

vsm198 Old Hand Points: 340 More actions · Answer 6

Thank you Gurus

I shrinked the PR databse , took a full backup then restored it on Secondary server. This gave space to breathe.

Thank you again

george sibbald SSC Guru Points: 104210 More actions · Answer 7

Shrink, backup log, apply log through log shipping would have worked as well.

---------------------------------------------------------------------

vsm198 Old Hand Points: 340 More actions · Answer 8

This happend due to a huge transaction log, so I shrinked the log file on PR, and then took a full backup of db and then restored. This gave some space, now we are in the process of adding space to drive which should be the permanent fix.

Thank You again.