[DOCS-4670] Explain the usage of "Pre-Configure New Daemon" in Ops Manager Created: 15/Jan/15  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Linda Qin Assignee: Anthony Sansone (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 7 years, 29 weeks ago
Epic Link: OM Backup Daemon
Story Points: 2

 Description   

There is a button "Pre-configure New Daemon" on the "Admin => Daemons" page. However it is not clear the usage of it in the following document:

It would be nice to add the documentation for it:

When a new Daemon is started, it will automatically register itself and appear on the Admin: Backup: Daemons page. If a Daemon is started in this fashion, it is started with all Config options checked and an "indeterminate" disk type.

If you would like to bring up a new Daemon with the intention of reserving it only for a single very large job which you are going to manually assign to this Daemon, (for example, if you only want this Daemon to work on Restore jobs), you can use “Pre-Configure New Daemon” to pre-configure the Backup Daemon and uncheck all the other Config options before starting the Daemon.

Otherwise, if the Daemon is started and automatically registered, all the job types are initially checked. This means that a different new job like a Backup job could get assigned to it, before you has the chance to go un-check the "Backup Jobs" box.



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:48:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.