This has also caused an interruption in our Veeam-dependant services as we have noticed that with the increased number of snapshots on VMs, backup/replication performance of Veeam 7 has suddenly dropped to such a level that it cannot give us full backup and replication of our whole platform.
This is an immensely stressful work as our platform is relatively large and each VM has now accumulated about 20 snapshots (10 for backup jobs and 10 created by replication jobs). However, whilst all new jobs do clean their snapshots now, old snapshots are still left for us to clean manually. We have spoken to the Veeam support, they have done clean up of few tables and update of one store procedure on the database.
It is disappointing that this had to happen and that it was not caught during your internal testing. Thanks Vladimir, we also found the KB1810 which clearly explains why this has happened to us and what the recommended steps are to rectify this situation.
0 kommentar(er)
