I am in a situation currently in which I will ALWAYS receive a success with exception (unless it fails of course). The exception I am receiving is below:
V-79-40960-38519 - The virtual machine was backed up, but the data that resides on pass-through disks that are associated with this virtual machine was not backed up. Use the Backup Exec Agent for Windows on the virtual machine for backup and restore operations of the volumes that reside on the pass-through disks
I am fine with this, and have scheduled the seperate job that is required to cover the pass through disk. That job is passing every day.
I now would like to ignore this particular exception so my jobs are marked as succesful.
I am pre-empting lots of people saying "but what is the point it was successful anyway". My counter to this is that when it passes with exceptions, I need to check the status every day to ensure the exception WAS actually this one and not another which could cause issues.
We are a company with over 100 clients with backups to check...having to do this every day will be a massive time consumption.
Can anybody advise please?
Solved! Go to Solution.
Is the Remote agent installed inside these VMs ?
Have a look @ this KB - http://www.symantec.com/business/support/index?page=content&id=TECH216403
You could try the following backup strategy:
Back the VM up once a week as a Full, and then the rest of the week as a Physical machine.
This will get the Virtual disks backed up and then the rest of the server can be protected via RAWs. You will still receive the exception once a week, when the full VM runs.
So are you refering to:
Friday -> Full Hyper-V backup selected from the hosts selection list
Monday - Thursday -> Incrimental by selecting the Virtual Machine as a physical machine.
My 2 questions are:
Let me clarify:
You would need to run 2 separate jobs.
One full job for the Hyper-V backup ran once a week and a second job for the RAWS backup the remaining days.
The Hyper-V license covers backing it up as a physical machine, as it licenses ALL guests on that host for agents. However, it would not cover any extra licensing, for example the Application and Database license
Ok I think I understand.
If I understand correctly though it would require having 2 full backups per week, which we would not have enough storage space (full backup is 6TB).
The backup also takes 48 hours to complete so we would not have enough time to fit a second full backup in during the week as we cant run backups during the day due to speed impacts.
Surely there is a way in Backup exec similar to the "auto respond to alerts" that simply says ignore all V-xxxxxx-xxxxxx exceptions?
PKH is right in saying there is no way to avoid the exception and I have confirmed this with our Engineering Support Team. You best bet would be what I already recommended to you, earlier in the thread:
“Back the VM up once a week as a Full, and then the rest of the week as a Physical machine.
This will get the Virtual disks backed up and then the rest of the server can be protected via RAWs. You will still receive the exception once a week, when the full VM runs.”
You would still need to run two separate jobs, but the exception would been seen once a week instead of daily. Let me know if this helps.
Well he said that he can not run two fulls because he does not have the storage required for it. Then I would do as pkh said, back it up as a physical machines. That would give you proper succes status.
Although It is a bit rubbish that there isnt the facility to do this, I accept this as a solution and have recreated the entire job as a physical machine instead.
Maybe this is something Symantec should examine for future versions.
>> You should exclude this machine
That seems like an extreme solution just to avoid the warning. Backing up the Hypervisor along with its clients and to the exclusion of the pass-through disks is a legitimate technique advocated by Veritas Support.
Perhaps the job could be configured with an option to suppress the warning. If such options are non-existent, then perhaps they could be provided in the future.