Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

removing clients from a schedule 1

Status
Not open for further replies.

craeg

MIS
Jun 9, 2000
31
US
What is the best way to remove clients from a regular full/cumu inc. schedule?
I want to keep the backups of the boxes for a few weeks - but I dont want them getting backed up every night.
Thanks!
 
I would create an inactive policy called Suspended that has no schedules nor is it active. Then you can place these clients in the policy. If you need to perform a restore, you will still see them in the client list. When you no longer need them, just delete them from the policy.
 
The suggestion is exactly right. Taking it a bit further, here is what I do. There are two inactive classes. Both have no schedules, etc as was suggested. One class is named "dead". This class is for boxes that I have been told are being/have been decommissioned. After a period and confirmation from the server owner, this client is deleted. The second class is called "Problems". It is my repository for clients who are having issues that may or may not be within my jurisdiction to fix. They set there until I or the owner fixes or thinks the box is fixed. Frequently, I can then easily distribute the "Problems" client list to the admins or owners of the boxes to let them know that these units are not being backed up and that someone needs to stand up and take the issue to heart. This is a bit of a PYA scheme.

Hope it gives you ideas. Imagination is more important than knowledge. Albert Einstein.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top