02-17-2014 06:07 AM
Solved! Go to Solution.
02-17-2014 08:40 AM
I guess you could create that file and just leave it blank or pipe out a simple option as the normal notify scripts do.
I can see no documentation that mentions this notify file to have any idea what you can put into it - does it actually cause a backup failure or just appear in its log?
To make sure it supports CBT you can look in the Policy itself - when browsing for machines you can set the columns to show "Change Tracking Support" to see if your client is detected as having that support
02-17-2014 07:06 AM
Pretty sure that message is just a warning - not sure why you would get it when going to tape but not to disk and it is just refering to an option script
BLIB being usable is all down to the VM's themselves having CBT enabled (ESX 4.x and above and vmx-07 or above) http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103187...
02-17-2014 07:59 AM
Hi Mark,
thanks for your reply,
It means that the backup will still be incremental not a full backup as the backup size is 2.5 TB.
Do you know if we can resolve this warning issue ?
Thanks.
02-17-2014 08:40 AM
I guess you could create that file and just leave it blank or pipe out a simple option as the normal notify scripts do.
I can see no documentation that mentions this notify file to have any idea what you can put into it - does it actually cause a backup failure or just appear in its log?
To make sure it supports CBT you can look in the Policy itself - when browsing for machines you can set the columns to show "Change Tracking Support" to see if your client is detected as having that support