How to avoid first FULL backup being auto triggered when a new policy is created
We have a requirement to avoid FULL backups being triggered when a new policy is created. Any thoughts?
Since the first backup WILL be full, the best way to work this is to ensure that the first backup is the regularly scheduled full.
How do you do this? You have to have standards and procedures. Failing that you create extra work for your self.
You can define and run a script every hour or day checking for newly added clients, and automatically setting them to not backup, or email you with the listing of new clients so you can do it manually.
I have had a few large (multi-TB ) clients, where I have manually manipulated them, but I normally just run a full at my convenience, to prevent the next few days incrementals all being fulls.
It depends on how bad it is, what is your effort/reward? If this is a significant issue, the costs this other group are causing should be enough for management to request they change their procedures.