This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Agentless VM KEEPS doing Base image

We have about 20'ish VM running on a 3 node Hyper-V cluster, I'm using agentless backups for most of them.  I've had a few issues with a small number of the VM's but I have one with an issue I can't seem to solve.

One of the VMs KEEPS DOING BASE IMAGES! It'll do the odd incremental but always seems to do a Base.  Its just a server 2012r2 VM running our building control software (HVAC, etc) nothing special its only around 25Gb in size, and has VERY little data churn!

 

I could put up with the constant base images as performance, bandwidth, repo size isn't an issue, BUT as it keeps doing a base it breaks replication to our offsite Core giving a duplicate base image has been found error and replication stops.

 

Any ideas WHY its doing a base and how to stop it!

 

Regards

Kerry 

Parents
  • Is this happening when the VM is being migrated over to another host? If that was the case, or if you wanted to check you could migrate it over to another host to validate if that was the case (of course if it was that would create another base).

    Does it fail a backup and then take a base?

    Just curious is the hard disk a .vhd or a .vhdx file (I have seen this happen on a .vhd however that is due to the fact that it isn't supported).

    Anything else scheduled to run on the host during this VMs backup? Or is simply in the same schedule as the others?
Reply
  • Is this happening when the VM is being migrated over to another host? If that was the case, or if you wanted to check you could migrate it over to another host to validate if that was the case (of course if it was that would create another base).

    Does it fail a backup and then take a base?

    Just curious is the hard disk a .vhd or a .vhdx file (I have seen this happen on a .vhd however that is due to the fact that it isn't supported).

    Anything else scheduled to run on the host during this VMs backup? Or is simply in the same schedule as the others?
Children
No Data