Order of directive processing in the Preferred Network properties

NetBackup sorts all directives into decreasing order by subnet size so that the more specific network specifications, such as complete host names or IP addresses, match first. (For example, a /24 subnet matches before a /16 subnet.) In this way, NetBackup can honor host-specific overrides.

If NetBackup considers the directives of multiple networks to be equal in specificity (a tie), NetBackup looks at the order in which the networks are listed.

See Order of directives can affect processing.

NetBackup processes each resolved address in the network list according to specific rules. Directives that contain addresses that do not apply to the host are ignored.

Table: Order of directive processing describes how NetBackup determines whether an address can be used for communication.

Table: Order of directive processing

Step	NetBackup considers the target	Target is selected or processing continues
1	If the target is not a match for the directive, and if the directive is an Only directive...	...then the target is treated as Prohibited, and processing stops for that target. NetBackup considers the next target.
2	If the target is a match for the directive, and if the directive is a Prohibited directive...	...then the target is treated as Prohibited and processing stops for that target. NetBackup considers the next target.
3	If the target is not a match...	...then the processing continues. NetBackup considers the next directive in the list.
4	If the target is a match...	...then the directive is either Only or Match and further directive processing stops. An Only match is treated like a Match in terms of source binding computation. If no rules ever match, then the target is allowed, and no source binding is enforced.

Order of directive processing in the Preferred Network properties

Feedback

Feedback