Azure Database Migration Service - awaria połączenia ze źródłową bazą danych

# Typowe komunikaty bledow w DMS:
# "The connectivity check to the source server failed"
# "Failed to connect to source SQL Server. Reason: A network-related or instance-specific error occurred"
# "Login failed for user 'dms_migration_user'. Reason: The server is not configured to allow remote connections"
# "TCP Provider: No connection could be made because the target machine actively refused it"

# Sprawdz status taska migracji via Azure CLI
az dms project task show \
  --resource-group rg-migration \
  --service-name dms-prod-westeurope \
  --project-name sql-to-azure-project \
  --name full-migration-task \
  --query '{status:properties.state, errors:properties.errors}'

# Lista wszystkich taskow w projekcie migracji
az dms project task list \
  --resource-group rg-migration \
  --service-name dms-prod-westeurope \
  --project-name sql-to-azure-project \
  --query '[].{name:name, state:properties.state}' -o table

# Sprawdz eventy DMS w Activity Log
az monitor activity-log list \
  --resource-group rg-migration \
  --start-time $(date -u -d '2 hours ago' +%Y-%m-%dT%H:%M:%SZ) \
  --query "[?contains(resourceId,'dms-prod-westeurope')].{time:eventTimestamp, status:status.value, message:properties.statusMessage}" \
  -o table

# Znajdz NSG przypisana do subnetu DMS
az network vnet subnet show \
  --resource-group rg-network \
  --vnet-name vnet-migration \
  --name subnet-dms \
  --query 'networkSecurityGroup.id' -o tsv

# Wylistuj reguly outbound NSG
az network nsg rule list \
  --resource-group rg-network \
  --nsg-name nsg-subnet-dms \
  --query "[?direction=='Outbound'].{name:name, priority:priority, access:access, destPort:destinationPortRange, destAddr:destinationAddressPrefix}" \
  -o table

# Dodaj regule zezwalajaca na ruch do zrodlowego SQL Server (port 1433)
az network nsg rule create \
  --resource-group rg-network \
  --nsg-name nsg-subnet-dms \
  --name Allow-SQL-Source-Outbound \
  --priority 200 \
  --direction Outbound \
  --access Allow \
  --protocol Tcp \
  --source-address-prefixes "10.1.0.0/24" \
  --destination-address-prefixes "192.168.1.50" \
  --destination-port-ranges 1433 \
  --description "Allow DMS subnet to reach source SQL Server"

# Jesli DMS laczy sie przez peered VNet - sprawdz czy peering jest aktywny
az network vnet peering show \
  --resource-group rg-network \
  --vnet-name vnet-migration \
  --name peering-to-onprem-vnet \
  --query '{state:peeringState, allowForwarded:allowForwardedTraffic, useRemoteGw:useRemoteGateways}'

# Z poziomu Azure CLI - sprawdz stan SHIR (Integration Runtime)
az datafactory integration-runtime show \
  --resource-group rg-migration \
  --factory-name adf-migration-prod \
  --name shir-onprem-agent \
  --query '{state:properties.state, version:properties.version, autoUpdate:properties.autoUpdate}'

# Jesli SHIR jest w stanie "NeedRegistration" - zarejestruj ponownie
# 1. Pobierz nowy klucz z portalu lub CLI:
az datafactory integration-runtime list-auth-key \
  --resource-group rg-migration \
  --factory-name adf-migration-prod \
  --name shir-onprem-agent \
  --query 'authKey1' -o tsv

# Sprawdz rozwiazywanie DNS z poziomu SHIR lub VM w subnecie DMS
nslookup sql-source.corp.local
# Jesli nie rozwiazuje - dodaj wpis w Private DNS Zone lub hosts

# Sprawdz czy Private DNS Zone jest zlinkowana do VNetu DMS
az network private-dns zone list \
  --query "[].{name:name, vnetLinks:numberOfVirtualNetworkLinks}" -o table

az network private-dns link vnet list \
  --resource-group rg-dns \
  --zone-name corp.local \
  --query "[].{name:name, vnetId:virtualNetwork.id, registrationEnabled:registrationEnabled}" -o table

# Jesli brakuje linka - dodaj VNet DMS do Private DNS Zone
az network private-dns link vnet create \
  --resource-group rg-dns \
  --zone-name corp.local \
  --name link-vnet-migration \
  --virtual-network /subscriptions/<sub-id>/resourceGroups/rg-network/providers/Microsoft.Network/virtualNetworks/vnet-migration \
  --registration-enabled false

# Ponowne uruchomienie taska migracji po naprawie polaczenia
az dms project task restart \
  --resource-group rg-migration \
  --service-name dms-prod-westeurope \
  --project-name sql-to-azure-project \
  --name full-migration-task

# 1. Test polaczenia sieciowego z subnetu DMS (z VM diagnostycznej lub SHIR)
# Na maszynie w subnecie DMS:

# 2. Sprawdz status taska DMS po ponownym uruchomieniu
az dms project task show \
  --resource-group rg-migration \
  --service-name dms-prod-westeurope \
  --project-name sql-to-azure-project \
  --name full-migration-task \
  --query '{state:properties.state, migrationType:properties.taskType}' -o json
# Expected: state = "Running" lub "Succeeded"

# 3. Sprawdz postep migracji (liczba zmigrowanych tabel)
az dms project task show \
  --resource-group rg-migration \
  --service-name dms-prod-westeurope \
  --project-name sql-to-azure-project \
  --name full-migration-task \
  --query 'properties.output[?resultType==`MigrationLevelOutput`].{status:migrationState, startedOn:startedOn, tables:summary.tableCount}' \
  -o table
# Expected: migrationState = "MIGRATION_IN_PROGRESS" lub "MIGRATION_COMPLETED"

# 4. Weryfikacja SHIR connectivity
az datafactory integration-runtime show \
  --resource-group rg-migration \
  --factory-name adf-migration-prod \
  --name shir-onprem-agent \
  --query 'properties.state' -o tsv
# Expected: "Online"

# 5. Weryfikacja ze dane plyna do Azure SQL Database
az sql db show \
  --resource-group rg-azure-sql \
  --server sql-target-prod \
  --name TargetDB \
  --query '{status:status, currentSku:currentSku.name, size:maxSizeBytes}' -o json