Post reply

Restoration of transaction logbackup failing in log shipping due to insufficient disk space

  • July 16, 2008 at 6:56 am

    #189684

    Restoration of log is failing as there is insufficient disk space, the database is marked is still under restoring state, I tried to restore the same log backup file by trying to move one of the databse file to different location.

    It says that The file cannot be moved by this restored operation.

    When I try to restore log backup as it is, it is failing with a message there is insufficient disk space.

    I have a question here, can I restore the failing transaction log backup? If so how?

    If not is the only solution is to restore full backup.

  • July 16, 2008 at 9:44 am

    #843893

    You have to restore the full backup with norecovery before restoring the log backup anyway. You can specify a new physical location for the database files by using "WITH MOVE" in the RESTORE DATABASE statement. That will assign the logical files to the new physical file.

    Greg

  • July 16, 2008 at 10:07 am

    #843906

    Thanks Greg,

    I have already started doing that as that is my last option.

    I am trying to find is there any way we can get out of this situation.

  • July 16, 2008 at 11:53 am

    #843975

    I just noticed that the title of your original post says you're doing log shipping. I recommend you stop the log backups until you can find more space on the destination server then start over with a new full backup. If you're going to keep the databases in sync, you'll need at least the same amount of disk space as the original database.

    Greg

  • July 16, 2008 at 12:32 pm

    #844000

    Thanks Greg.

    I have restored database by moving couple of database files where there is ample room to grow for data files.

Viewing 5 posts - 1 through 4 (of 4 total)

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