![]() ![]() ![]() All database files and backups are on E: drive and the database status is in loading state. This is how SQL Server was configured 5 years back but been working on this server from past 1.5 years. If we do defragmentation today and will go worse in 1 or 2 days due to backups. Because backups will be deleted and recreated, obviously there will be a huge fragmentation on the disk. The reason why DiskKeeper will not work for us because we have SQLServer backups on the same disk where data & log files are residing. RESTORE DATABASE is terminating abnormally.Ĭannot apply the backup on device LiteSpeed 2005 backup file to database 'PROD'.Ĭould anyone suggest me what could be the reason? I know that PROD and DR servers configuration should be almost similar. MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file. Now log-shipping is failing and I couldn't able to restore log files or differential backup to DR server.īelow is the error when I'm trying to restore log file:Ĭould not adjust the space allocation for file 'DB_LOG'. We did this because we have an issue with Disk I/O due to heavy disk fragmentation. Yesterday, we added extra storage to PROD server and I resized data files. We have a production server that was configured for log-shipping and logs being transported to DR server for every 15mints. I don't know whether you faced this problem or not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |