Have you any recommandations about backup Windows failover nodes ?
We have configured one policy to backup user data with logical cluster name. That's OK.
When cluster nodes switch (secondary become primary), next backup, incremental schedule, is running in full mode. I've see that by compare volume and files number.
Maybe you can help me to understand what's happen.
This part of status details can help... but how to fix it ?
28 avr. 2020 21:44:13 - Info bpbrm (pid=704) There is no complete backup image match with track journal, a regular full backup will be performed.
You can move the track log to the shared drive and then link to the default path.
Please have a look at this excellent article: https://vox.veritas.com/t5/Articles/Accelerator-backup-of-Windows-Cluster-systems/ta-p/813666