• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 6682 views
  • Users 0 members are here
Options
Related
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

dtghelp
over 6 years ago

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
  • 0 over 6 years ago
    Hi Kerry:
    Probably the quickest fix is to install the agent on that machine. (Make sure that you change the display name of the protected server before removing it if you want to keep the current recovery points; this will avoid a name conflict when protecting the server again; you cannot (easily) change the name of a recovery points only instance).
    The issue is probably related to VSS issues on the Hyper-V host (duh!), specifically, the host being unable to 'link' with the VSS inside the protected machine to properly do the quescing. If you want to use agentless protection, you should open a ticket with us and we will figure it out together.
Reply
  • 0 over 6 years ago
    Hi Kerry:
    Probably the quickest fix is to install the agent on that machine. (Make sure that you change the display name of the protected server before removing it if you want to keep the current recovery points; this will avoid a name conflict when protecting the server again; you cannot (easily) change the name of a recovery points only instance).
    The issue is probably related to VSS issues on the Hyper-V host (duh!), specifically, the host being unable to 'link' with the VSS inside the protected machine to properly do the quescing. If you want to use agentless protection, you should open a ticket with us and we will figure it out together.
Children
No Data