meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 5 months |
| seen | Apr 1 at 13:08 | |
| stats | profile views | 4 |
|
Mar 18 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup What's the deal with not being able to edit my own comments? The above should say "...from every 5 minutes for all 3 databases to every 20 minutes for 2 databases and every 5 minutes for 1 database. ..." |
|
Mar 18 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup A bit of an update: 1) I changed log backup frequency from every 5 minutes for all 3 databases to every 2 minutes for 2 databases and every 5 minutes for 1 database. I also staggered them in time. This seems to take care of log backup failures and "insufficient memory" messages. 2) I also removed mirroring from 2 databases completely (every mirrored database accounts for 2 connections) and left it active for 1. Timeouts are still occurring. |
|
Mar 15 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup Highest wait by pct_wait_time is DBMIRROR_SEND (82.7%, 5022 ms) but could it be skewed because I kept mirroring suspended for the last several hours for one of the databases? Second highest is PAGEIOLATCH_SH (11.0%, avg 94.2 ms) |
|
Mar 15 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup Mirroring is set to "High Safety without automatic failover". There is no witness. Insert/update activity on the primary is really low, so I don't think mirror not being able to keep up is an issue. |
|
Mar 15 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup 4) 99% log backups take 0 sec to complete, the rest are 1-3 sec. 5) Staggering log backups, making them less frequent and upgrading hardware is being considered (yes, that server is probably 6-8 years old) |
|
Mar 15 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup Mike, Your reply us appreciated. Here are answers and more questions: 1) Will enabling AWE at least help some with 4 GB of RAM? I can give SQL 2.5 GB max memory for instance. 2) I ran query for wait stats you linked to. In the first set of results (since server was started) this is what it looks like for BACKUPTHREAD : sum_wait_time_ms=5796846 pct_wait_time=0.1 sum_waiting_tasks=236073 avg_wait_time_ms=24.6 3) SQL Server: Buffer Manager -> Page Life Expectancy is about 54,000 (avg) - is that considered low? |
|
Mar 15 |
comment |
Getting timeouts and backup errors after mirroring and log shipping is setup Databases are not that large - one is 300 MB, another is 500 MB and another is 1.2 GB. Memory/Available MB counter i 1048 Min, 1081 Max |
|
Mar 15 |
asked | Getting timeouts and backup errors after mirroring and log shipping is setup |
|
Mar 12 |
awarded | Supporter |
|
Mar 12 |
asked | Can the same database be log-shipping secondary and primary at the same time? |
|
Mar 3 |
awarded | Tag Editor |
|
Mar 3 |
revised |
sql-server wiki description Updated edition description |
|
Mar 3 |
suggested | suggested edit on sql-server tag wiki |
|
Nov 28 |
awarded | Scholar |
|
Nov 28 |
accepted | Renaming SQL Server Agent operator |
|
Nov 28 |
asked | Renaming SQL Server Agent operator |
|
Nov 28 |
awarded | Student |
|
Aug 30 |
asked | SQL Server 2008 log shipping via JungleDisk |
