This is indicitive of a different issue.  Unless you have your VMs snapshotting constantly, you should not see this kind of topology churn.   Even using TSM-VE, which constantly is shapshotting VMs as part of it's mechanism, we don't see this issue, in a much larger environment.  Definately need to open a support ticket and get this looked at right away, as there is a good reason for this limit, to prevent debilitating topology churn.
I have received the following error and followed the process in the support link. But I'm still getting the error in the FMS log. Has anyone run into this issue before and succesfully modified the variable to not have this message appear anymore. What happens when you cannot create a topology for an object? [URL] I did create the VMWsnapshot variable and set it first to 20000 then 30000 and still get the error in the log.  [IMAGE]  [IMAGE]   [IMAGE]
Foglight limit instances