This is a known issue. As a workaround, do the following:
- Stop the Deep Security Manager service.
- Back up the database.
- Using the Microsoft SQL Server Management Studio, execute the following SQL command on the database where the Deep Security Manager is located. You can verify the database name from the DSM console under Administration > System information.
update hosts set virtualpowerstate=0 where virtualpowerstate=1