October 9, 2012 at 1:27 pm
Log Shipping is set from Server A to Server B for database X
SQL Server 2008 Std Edn 64 bit on both servers
Database X State at Secondary Server (B): Restoring
Problem: DB's Log file containing drive got full-What to do?
Please suggest any plans to overcome this situation other than to reconfigure it.
Thanks in advance,
Regards,
Ankur
October 9, 2012 at 9:46 pm
What is ur drive size in which your log files are and what is the size of the Database that is being logshipped.
October 10, 2012 at 1:16 am
ankur_libra (10/9/2012)
Log Shipping is set from Server A to Server B for database XSQL Server 2008 Std Edn 64 bit on both servers
Database X State at Secondary Server (B): Restoring
Problem: DB's Log file containing drive got full-What to do?
Please suggest any plans to overcome this situation other than to reconfigure it.
Thanks in advance,
Regards,
Ankur
Which location is full, the backup location on the primary or the copy location on the secondary?
What retention values did you set for your LS plan?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 10, 2012 at 6:14 am
Hi,
Mahesh:
Drive size in which DB log file is placed at secondary server: 25 GB
Size of the Database that is being logshipped: 23 GBs
Perry:
Databse log file containing drive at secondary server is full. All other locations like the backup location on the primary, the copy location on the secondary has enough disk space.
What retention values did you set for your LS plan?
Delete Copied files after 3 days
Thanks,
Regards,
Ankur
October 10, 2012 at 7:06 am
OK, so how often are the restores being applied by the restore job?
If they're restored hourly you could probably reduce the retention on the secondary, either that or get more disk space to support the retention period.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 10, 2012 at 2:08 pm
Hi Perry:
Restore job runs after every 15 minutes. Suggested points are Ok for future perspective.
Can you please suggest as per current scenario, where Log file containing disk at secondary server got full? Do we have any other optioin to resolve this issue apart from reconfiguring log shipping?
Thanks,
Regards,
Ankur
October 10, 2012 at 3:04 pm
ankur_libra (10/10/2012)
Restore job runs after every 15 minutes.
OK, so you probably don't need a 3 day retention period
ankur_libra (10/10/2012)
Can you please suggest as per current scenario, where Log file containing disk at secondary server got full?
Check the server and see what's filling up the drive!!
ankur_libra (10/10/2012)
Do we have any other optioin to resolve this issue apart from reconfiguring log shipping?
Why do you want to reconfigure Log Shipping?
You can change the retention without reconfiguring LS.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply