SQL Integration Services (SSIS) + VMotion Issues

Occasionally our SQL DBAs complain about issues with their SQL Server Integration Services (SSIS) jobs losing access to their log files. This seems to happen whenever DRS causes an automated VMotion event to happen behind the scenes.

During the VMotion event, in **Windows Event Log** has MSSQLSERVER errors like: “*FileMgr::StartLogFiles:: Operation system error 2(The system cannot find the file specified.) occurred while creating or opening file ‘E:\SQL_Logs\SSISDB4.ldf’.*”

Behind the scenes, the ESXi hosts are communicating via 8GbE FC SANs with no sign of resource contention on the storage side through a blade environment.

So far, the only solution I’ve found is to write a VM/Host Rule to “pin” a single SQL Server VM to a single host. This is great for a stability standpoint but completely defeats any sort of resiliency / failover.

Has anyone else encountered any issue with an application being ***this*** sensitive? Any tips on how to handle it? We’ve had no (*discovered*) issues with regular SQL Server DB services, SSAS (*to my knowledge*), etc. This is strictly with SSIS which seems a lot more sensitive than the other applications.

View Reddit by DjaestheticView Source

Related Articles

One Comment

  1. As long as your rule is a “should”, not a “must” rule, in the event of a failover, your VM will migrate over, but will prevent it from moving otherwise.

    Sorry I can’t help on the SQL side though.

Leave a Reply