How do I find Backend Services that are not used anywhere (Unused Entries)?
Short answer
In the Backend Services list, Unused Entries is selected in the selector opened with the Usage Filter button or in the Used in card of the Filter strip; the list shows the Backend Services that are not used in any vService or rule. If a cleanup is to be done, these rows are selected and deleted in bulk with Delete; since the deletion cannot be undone, a copy of the table is first taken with Export. The same filter also exists in the Backend Groups list.
Problem: Accumulated, Unused Records
Over time, Backend Services created for removed vServices, moved servers and trials remain in the list. Unused records crowd the list, lead to the wrong record being selected, and create confusion in audits.
Solution
Unused records are found with the list filter. The filter is opened from two places: the Usage Filter button in the toolbar or the Used in card in the Filter strip; both use the same Unused Entries value.
Unused Entries Filter
- How it works When Usage Filter is turned on, the search box turns into a vService selector; the Unused Entries option at the very bottom of the selector lists the records that are not used in any vService or rule.
- Where it is openedLoad Balancer → Backend Services → Usage Filter button (or Filter → Used in)
- Requirement None
- Scope Backend Services and Backend Groups lists
Step-by-Step Configuration
In the Load Balancer → Backend Services list, the network-icon Usage Filter button in the toolbar is clicked; the search box turns into a vService selector and the first option is selected automatically.
The faded Unused Entries option at the very bottom of the selector is selected; the list is filtered to the unused Backend Services. The same result is also obtained by opening the Used in card in the Filter strip and selecting the Unused Entries value; this path allows filtering together with other cards such as Health.
If a deletion is to be made, the table is first downloaded as Excel, CSV or PDF with the Export button.
The rows to be deleted are checked; to see them all on a single page, Page Size is set to All (its default value is 20).
Delete is clicked; the confirmation window shows the number of records to be deleted, and when it is confirmed, the records are deleted. When Clustering is on and Manual Sync Mode is off (default), the deletion is also transferred to the peer device automatically.
Verification
When a Backend Service in the filtered list is clicked, the Used in tab does not appear in the preview panel that opens.
No Used in tabAfter the deletion, the list stays empty while the Unused Entries filter is on.
No unused records leftCommon Mistakes
- Assuming that a record used in a rule is "not used". A Backend Service selected as the target in a Traffic Mirroring action does not appear in Unused Entries; this usage is seen not in the vService filters but only with the action name on the Used in tab of the preview.
- Leaving the filter on. When Usage Filter is left on, the list is assumed to be incomplete; the filter is removed by clicking the button again.
- Deleting in bulk without taking a copy. The deletion cannot be undone; a copy of the table is first taken with Export.
- Looking for a special "delete unused" button. There is no such operation; the filtered rows are selected and deleted with Delete.
How it is done in the documentation
