This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
About infrags
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About infrags
12-13-2022
4Posts
1Like
1Solution
Dec 13, 2022Last Visited
User
Activity
User
Profile
Latest posts by infrags
| Subject | Views | Posted |
|---|---|---|
| 2017 | 11-29-2021 05:11 AM | |
| 2133 | 11-18-2021 04:50 AM | |
| 2208 | 11-17-2021 05:31 AM | |
| 2380 | 11-16-2021 06:08 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 11-16-2021 06:08 AM |
User Badges
Community Statistics
| Member Since | 03-24-2020 06:47 AM |
| Date Last Visited | 12-13-2022 02:49 PM |
| Posts | 4 |
| Total Likes Received | 1 |
11-29-2021
05:11 AM
Hello everyone, after some weeks of analyzes and debug finally we solved the problem. Due different disk sector size on azure VMs, 512 bytes on premises and 4k on azure, we must enable sql trace flag 1800 on on-premises VMs. After that the sql replication is working like a charm. Find below KB about this issue. https://support.microsoft.com/en-us/topic/kb3009974-fix-slow-synchronization-when-disks-have-different-sector-sizes-for-primary-and-secondary-replica-log-files-in-sql-server-ag-and-logshipping-environments-ed181bf3-ce80-b6d0-f268-34135711043c
... View more
11-18-2021
04:50 AM
Hi, yes I did configure this at security policy. Unfortunately I can't edit mtu on azure side, cause I'm using azure native virtual gateway.
... View more
11-17-2021
05:31 AM
Yes. I did on security rule by checking Disable Server Response Inspection, also I have create an application override for mssql server always on port (5022).
... View more
11-16-2021
06:08 AM
1 Kudo
Hi folks, I'm facing some throughput issues with a site to site vpn between my onprem site (vm-300) and azure (VpnGw1). Scenario: - Windows cluster + SQL Always on Availability Groups (async commit) - 2 nodes on premises (sql01 and sql02) - 1 node on azure (sql03). - Link speed 150Mbps - Latency between on prem and azure: 15ms Ipsec tunnel is working, running some generic tests (iperf and smb copies) the throughput hits: on-prem to azure: 80Mbps azure to on-prem: 150Mbps The issue is when SQL trying to replicate. The sql01 is my primary, so it is the one who replicate data to secondaries (sql02 and sql03) Throughput replication from sql01 to sql02 it's around 2.5Mbps (lan connection) Throughput replication from sql01 to sql03 it's around 1Mbps. (which goes through the vpn). Changes made: - Tunnel MTU to 1400 - Disable Anti replay protect I did some captures with packet-capture and I could observe high TCP out-of-order and TCP Previous segment not captured. Hope some one could help me.
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks