[DOCS-8519] Seed a New Secondary from Backup Restore Created: 05/Aug/16  Updated: 04/Nov/16  Resolved: 03/Nov/16

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: post-launch_mongodb-3.4

Type: Improvement Priority: Minor - P4
Reporter: Jake Angerman Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 14 weeks, 5 days ago
Epic Link: C/OM Backup
Story Points: 1

 Description   

There are a few issues on the Seed a New Secondary from Backup Restore page.

1. The Remove the broken secondary from your replica set step should specify that this step is done on the primary (the add it back step at the end already does this). If you don't do it on the primary, you'll get an error message:

demo:SECONDARY> rs.remove("demo-1.mongodbdns.com:27000")
{
    "ok" : 0,
    "errmsg" : "replSetReconfig should only be run on PRIMARY, but my state is SECONDARY; use the \"force\" argument to override",
    "code" : 10107
}

2. The Bring up new node as a standalone step needs to include a z option to the tar command:

tar -zxvf <backupRestoreName>.tar.gz

3. The Bring up new node as a standalone step should use sudo to prevent the ephemeral mongod process from creating files that will be owned by an inappropriate userid. So instead of:

mongod --port <alternatePort> --dbpath /data

... it would be:

sudo -u mongod mongod --port <alternatePort> --dbpath /data

4. The Bring up new node as a standalone step mentions "data" in the mv command without any context. I think it's conveying that the backup image becomes /data as in:

mv <backupRestoreName> /data

5. When you add it back, it is also worth noting that even if the command succeeds, you get a message that reads as if an error occurred:

demo:PRIMARY> rs.add("demo-1.mongodbdns.com:27000")
{
    "ok" : 0,
    "errmsg" : "Found two member configurations with same host field, members.1.host == members.3.host == demo-1.mongodbdns.com:27000",
    "code" : 103
}

Comment on: "tutorial/use-restore-to-seed-secondary.txt"



 Comments   
Comment by Githook User [ 04/Nov/16 ]

Author:

{u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}

Message: (DOCS-8519): Backport for v2.0
Branch: v2.0
https://github.com/10gen/mms-docs/commit/03fcb304d66f5e2cb39f1f94155a6448c15b4ac7

Comment by Githook User [ 04/Nov/16 ]

Author:

{u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}

Message: (DOCS-8519): Updated restore seeding procedure.
Branch: master
https://github.com/10gen/mms-docs/commit/750cbae9f0708380337b93e35cfe8c1add852019

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