- Posts: 125
- Liked: 3 times
- Joined: Mar 23, 2009 4:44 pm
- Full Name: Matt
Here is the Windows log from the SQL Server for the backup startup:
08:01:04 AM - The Volume Shadow Copy service entered the running state.
08:01:04 AM - The VeeamVssSupport service was successfully sent a start control.
08:01:04 AM - The VeeamVssSupport service entered the running state.
08:01:08 AM - The Microsoft Software Shadow Copy Provider service was successfully sent a start control.
08:01:08 AM - The Microsoft Software Shadow Copy Provider service entered the running state.
08:01:35 AM - The VeeamVssSupport service was successfully sent a stop control.
08:01:35 AM - The VeeamVssSupport service entered the stopped state.
08:04:34 AM - The Volume Shadow Copy service entered the stopped state.
08:07:34 AM - The Microsoft Software Shadow Copy Provider service entered the stopped state.
There are no log entries entered for backup completion.
Here is what virtualcenter is reporting is happening during the backup event
11/18/2009 8:01:01 AM - User logged event: Source: Veeam Backup Action: Job "wksql01" Operation: Started Status: Success ID: 08e74771-ac6a-41bf-ba4f-5a7212a1fe0e Description:
11/18/2009 8:01:20 AM - Create virtual machine snapshot
11/18/2009 8:02:43 AM - Release disk lease
11/18/2009 9:29:57 AM - Release disk lease
11/18/2009 9:56:16 AM - Release disk lease
11/18/2009 9:57:17 AM - Create virtual machine snapshot
11/18/2009 9:57:22 AM -Remove snapshot
11/18/2009 9:58:50 AM - Remove snapshot
11/18/2009 9:59:34 AM - Reconfigure virtual machine
11/18/2009 9:59:35 AM - Reconfigured virtual machine
11/18/2009 9:59:38 AM User logged event: Source: Veeam Backup Action: Job "wksql01" Operation: Stopped Status: Success ID: 08e74771-ac6a-41bf-ba4f-5a7212a1fe0e Description:
I'm trying to verify (or understand) a few things:
1. Why am I dropping connections during startup of the backup. Is this due to VSS or the Snapshot creation, or both?
2. Based on my log above, how long am I technically dropping connections during the startup - 31 seconds?
3. Why don't those connections just queue somewhere using VSS? Is that part of VSS or how the app is written?
During Backup Completion
-Example error message: Exception Message: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
4. Why am I dropping connection during backup completion. My assumption is that because of the snapshots being merged.
5. Based on my logs above, can I tell how long I'm dropping connections upon backup completion.
6. Is there anything I can do to minimize or eliminate these kinds of SQL drops while still using Veeam as the backup method?
7. What is the communities/Veeam's recommended method to achieve say hourly or bi-hourly backups of an SQL server? Is it Veeam, trans log backups, log shipping, active/passive?
Thank you all for your help
- Chief Product Officer
- Posts: 31002
- Liked: 6412 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
On backup completion, connections should not be dropped either. With ESX4, VMware ensures that VM freeze on last snapshot commit is a few seconds (I did extensive stress testing on this back in time). But please check if SQL VM has some other snapshots, as this is known to create long delays and VM freezes on snapshot commit.
I will think more on all this and also talk to devs tomorrow.