Forum Discussion

gpn43's avatar
gpn43
Level 3
10 years ago

Hyper-V VM Incrementals same size as full

Hello,

My hyper-v VM incremental backups are the same size as my full backups. The backups are going through the hyper-V host, they have GRT enabled, unticked box to run VM as full if inc is not supported, and verified agent is installed on host and VM's. BE2014 server is 2008r2, and Hyper-V host and VM's are 2008r2. Not really sure what else to try here, and I was told my symantec that this would work properly. I do not want to do agent based backups on these VM's. See attachment for picture of storage. 

Any suggestions would be appreciated. 

2014
Agent for Microsoft Hyper-V
Backing Up
Backup and Recovery
Backup Exec
Windows Server (2003-2008)
  • jurgen_barbieur's avatar
    jurgen_barbieur
    10 years ago

    have a compare between the job log of the full backup and the joblog of an incremental backup.

    if I take a look in the job-log you provided, I see 3 backup sizes, and if I sum them together, the result is approx. 16 GB, which possibly is the size of an incremental. In the picture you show it just give the title "SIZE". 

    Maybe there is some problem in backupexec not showing the correct size in your backupsets summary.

    open a case at symantec to have a better look on this issue

6 Replies

Sort By
  • jurgen_barbieur's avatar
    jurgen_barbieur
    Level 6
    10 years ago

    Is the sizing exactly the same or almost the same?

    because of the unticked box to run full if inc is not supported, if this was the issue the job has to fail. Because of a successfull backup it seems that he does run a inc backup. 

    can you attach the job log? I think the log will tell us if it is a full or incr backup.

  • gpn43's avatar
    gpn43
    Level 3
    10 years ago

    And in answer to your question - the sizing is the exact same.

  • VJware's avatar
    VJware
    Level 6
    10 years ago

    I would recommend to log a formal support case so that we can review the debug logs to figure out why the incremental is being processed as a full.

  • jurgen_barbieur's avatar
    jurgen_barbieur
    Level 6
    10 years ago

    have a compare between the job log of the full backup and the joblog of an incremental backup.

    if I take a look in the job-log you provided, I see 3 backup sizes, and if I sum them together, the result is approx. 16 GB, which possibly is the size of an incremental. In the picture you show it just give the title "SIZE". 

    Maybe there is some problem in backupexec not showing the correct size in your backupsets summary.

    open a case at symantec to have a better look on this issue

  • gpn43's avatar
    gpn43
    Level 3
    10 years ago

    Job log attached from last night. It appears that is is running an incremental. However, would it have anything to do with BE not reading the .VHD file correctly or detecting changes within that? I think it is just detecting a change in the .VHD and then taking a full backup of it again.

    Agent based backups are working correctly, its just the VM's that are having problems with incrementals. 

    Thanks!