[DOCS-13536] Ops Manager Backup Daemon ports 27500-27503 missing Created: 19/Mar/20  Updated: 27/Oct/23  Resolved: 20/Mar/20

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

Type: Bug Priority: Minor - P4
Reporter: Felicia Hsieh Assignee: Unassigned
Resolution: Works as Designed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 3 years, 46 weeks, 5 days ago

 Description   

Description

Last mention of the Backup Daemon ports is in Ops Manager 1.6 under Firewall Configurations

https://docs.opsmanager.mongodb.com/v1.6/reference/firewall-configuration/index.html

Backup Daemon ports are not really a Firewall configuration, but the ports (27500-27503) should be listed somewhere on Ops Manager docs.

These listing of the Backup Daemon ports are missing in Ops Manager version 3.4, 3.6, 4.0, and 4.2

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Anthony Sansone (Inactive) [ 20/Mar/20 ]

Per xiang.gao, closing.

Comment by Xiang Gao [ 20/Mar/20 ]

Daemon is running on the same machine as HEAD db starting 3.4: CLOUDP-23739. Nobody accesses head db from outside, so no need to open the ports in firewall.

Comment by Felicia Hsieh [ 20/Mar/20 ]

The backup is different than the backup daemon, to which is what I believe you're referring.
 
"The base port is 27500, the upper level depends on how many worker threads the daemon has. It might be something they have to worry about if they insist on knowing all ports for selinux"
 

Comment by Anthony Sansone (Inactive) [ 20/Mar/20 ]

felicia.hsieh: Those ports aren't needed because the Backup Daemon can connect to whichever mongod port it wants, usually the default of 27017. The backup team, john.morales and cory.mintz reviewed the PR. Nothing was flagged at that time.

Further, the Backup Daemon no longer applies to MongoDB FCV 4.2 or later, so this would not be an issue for this version.

cc: xiang.gao: If something changed in this case, please let me know.

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