+91 9619904949

Shared Client IP Pool for Email Sending

A shared client pool is essential for email sending as it allows us to maintain a collection of IP addresses and resources that multiple clients can use. This approach optimizes resource management, ensures load balancing, and provides a stable service—especially for smaller senders or new customers who lack the email volume to justify their own dedicated IP.

Why Do We Need Shared Client Pools?
1. IP Pool Management

By pooling IP addresses, we can rotate and manage sending IPs effectively.
This prevents overloading any single IP, which could lead to deliverability issues.
Pooling also enables better management of sender reputation by distributing email traffic across different IPs.

2. Pre-Warmed Reputation

If the majority of senders follow good practices, the pool benefits from an established positive reputation.
Smaller senders or new accounts can achieve good deliverability without needing to build their own reputation from scratch.

3. Inconsistent and Low Volumes

Shared IP pools are ideal for clients with low or inconsistent email volumes.
ISPs like Yahoo, Microsoft, and Google deprioritize emails from low-volume or inconsistent IPs, making shared pools a more reliable option.

4. Warm-Up

Shared IPs are already warmed up and actively used, eliminating the need to gradually increase email volume as required for a dedicated IP.

5. Cost-Management

Dedicated IPs come with additional fees, whereas shared IP pools provide better deliverability at a lower cost.
Depending on one or two dedicated IPs increases the risk of deliverability issues, but shared pools distribute traffic across multiple IPs, mitigating that risk.

6. Reputation Management

A shared client pool helps maintain a consistent sender reputation.
We use shared reputation scores for IPs and domains, benefiting all clients by improving overall deliverability.

7. Minimize the Risk

Clients with similar sending patterns can be grouped together, minimizing risks and ensuring consistent deliverability across the shared pool.

Shared client pools are crucial for maintaining reliable email deliverability. They are especially beneficial for small or new senders by providing cost-effective, reputation-enhancing, and risk-reducing email sending solutions compared to dedicated IPs.

11-Email Email Metrics Calculator

Email Metrics Calculator

Fill in the boxes below to calculate your metrics. Each input field corresponds to a value required for the calculation.

Email Metrics Calculator Formula:-

Delivery Rate: Delivery Rate = (Emails Delivered / Emails Sent) × 100
Bounce Rate: Bounce Rate = (Bounced Emails / Emails Sent) × 100
Open Rate: Open Rate = (Emails Opened / Emails Delivered) × 100
Click-Through Rate (CTR): CTR = (Unique Clicks / Emails Delivered) × 100
Click-to-Open Rate (CTOR): CTOR = (Unique Clicks / Unique Opens) × 100
Spam Complaint Rate: Spam Complaint Rate = (Spam Complaints / Emails Delivered) × 100
Unsubscribe Rate: Unsubscribe Rate = (Unsubscribes / Emails Delivered) × 100
Engagement Rate: Engagement Rate = (Unique Opens + Unique Clicks / Emails Delivered) × 100
Inbox Placement Rate (IPR): IPR = (Emails in Inbox / Emails Delivered) × 100
Email ROI: ROI = (Revenue from Campaign – Cost of Campaign / Cost of Campaign) × 100
Hard Bounce Rate: Hard Bounce Rate = (Hard Bounces / Emails Sent) × 100
Soft Bounce Rate: Soft Bounce Rate = (Soft Bounces / Emails Sent) × 100
Effective Delivery Rate: Effective Delivery Rate = (Emails Delivered – (Spam Complaints + Unsubscribes) / Emails Sent) × 100
Read Rate: Read Rate = (Emails Read / Emails Delivered) × 100
Forward/Share Rate: Forward/Share Rate = (Emails Forwarded or Shared / Emails Delivered) × 100
List Growth Rate: List Growth Rate = (New Subscribers – Unsubscribes – Bounced Emails / Total Subscribers) × 100
Retention Rate: Retention Rate = (Active Subscribers / Total Subscribers) × 100
Email Engagement Index (EEI): EEI = (Open Rate Weight × Open Rate + Click Rate Weight × Click Rate + Reply Rate Weight × Reply Rate)
Revenue Per Email Sent (RPE): RPE = Total Revenue from Campaign / Emails Sent
Conversion Rate: Conversion Rate = (Conversions / Emails Delivered) × 100
Engagement Score: Engagement Score = (Opens + Clicks + Replies / Emails Delivered)
Spam Rate: Spam Rate = (Emails Marked as Spam / Emails Sent) × 100
Reactivation Rate: Reactivation Rate = (Reactivated Subscribers / Total Inactive Subscribers) × 100
Churn Rate: Churn Rate = (Unsubscribes + Complaints / Total Subscribers) × 100
Average Revenue Per Subscriber (ARPS): ARPS = Total Revenue / Total Subscribers
Engagement Drop-off Rate: Engagement Drop-off Rate = (Unsubscribes + Inactive Users / Total Subscribers) × 100
Reply Rate: Reply Rate = (Replies / Emails Delivered) × 100

09-Email Learn Advanced Email Deliverability Techniques

Topics to Learn for Advanced Email Deliverability Techniques.

Mail Server Management: In-depth study of configuring and managing servers such as PowerMTA, Zimbra, Postfix, Strongmail, Qmail, and Exim.
Advanced Email Authentication: Best practices for implementing SPF, DKIM, DMARC, and BIMI, and managing DMARC reports for insights.
Bounce Management: Strategies for handling soft and hard bounces to improve email deliverability.
Spam Filters and Reputation Management: Tools like SpamCop, Watchguard, and Project Honey Pot to manage spam complaints and sender reputation.
Blacklist Management: Techniques for avoiding and recovering from IP or domain blacklisting.
Email Warm-up Strategies: Current methods for warming up domains, IPs, and email accounts to ensure high deliverability.
Content Optimization: Advanced techniques for avoiding spam filters, such as refining message headers, HTML coding, and keyword filtering.

ISP and ESP-Specific Expertise

Tools: Learn advanced features of ReturnPath, Google Postmaster Tools, Microsoft SNDS, 250Ok (now part of Validity), and Email On Acid.
ISP-Specific Compliance: Understanding the delivery mechanisms of Gmail, Yahoo, Outlook, and AOL.
ESP Tools: Hands-on experience with platforms like SendGrid, SES, Mailchimp, Benchmark, MailWizz, Interspire, Sendy, and MailTrain.

Marketing Automation & Analytics

Email Segmentation: Master advanced segmentation techniques based on user behavior, engagement, and demographics.
A/B Testing and Optimization: Learn how to conduct systematic testing for subject lines, email content, and CTAs to optimize performance.
Behavioral Triggers: Setting up automated workflows based on user interactions and lead scoring.
ROI-Driven Campaign Management: Using analytics to improve open rates, click rates, and conversions for campaign optimization.

Emerging Email Trends

AI and Machine Learning: Leverage AI for personalized email campaigns, predictive deliverability analysis, and insights into user behavior.
Zero-Party Data Utilization: Use voluntarily shared data from users to enhance segmentation and personalization strategies.
Dark Mode Optimization: Designing email templates that are optimized for dark mode compatibility across various devices.
AMP for Email: Explore dynamic content delivery within emails using AMP.
Domain Alignment and BIMI: Strengthen brand trust by ensuring domain alignment and implementing BIMI (Brand Indicators for Message Identification).

Lead Generation and Outreach

LinkedIn Outreach: Creating targeted LinkedIn campaigns, advanced research using Sales Navigator, and automating LinkedIn lead generation.
Data Collection: Online research for lead sourcing and utilizing email validation and enrichment tools like Snovio and SalesQL.
Social Media Outreach: Best practices for DM campaigns on platforms like Instagram, Facebook, and Twitter.

eCommerce and Advanced Campaigns

eCommerce Platforms: Master the integration of Klaviyo with Shopify, WooCommerce, and BigCommerce, and crafting pre-purchase, cart abandonment, and post-purchase flows.
Segmentation and Personalization: Learn advanced segmentation techniques and how to personalize campaigns based on user behavior for better targeting.

Email Marketing Tools

Tool Mastery: Deep-dive into tools like Gmass, Sendinblue, Mailchimp, Sendgrid, Mailer Lite, Mailer Cloud, Blue Core, and Mailtester and compare their features and use cases for email campaigns.

Compliance and Legal Considerations

Email Marketing Laws: Understand and comply with global email marketing laws like GDPR, CAN-SPAM, and CCPA to ensure legal compliance in all campaigns.

Additional Tools and Certifications

Tool Certifications:
HubSpot Email Marketing Certification
Google Analytics for Marketers
Klaviyo Email Marketing Certification
Salesforce Pardot Specialist
Marketo Certified Expert

Deliverability & Anti-Spam Certifications:
Certified by ReturnPath (Validity)
Certified Email Marketing Professional (CEMP)
M3AAWG Training on Anti-Abuse & Deliverability Practices

Cloud Platforms:
AWS SES and Pinpoint
Google Cloud (Cloud DNS for email-related configurations)
Microsoft Azure (SMTP and transactional email setups)

Technical Skills

DNS Management: Master advanced configurations for SPF, DKIM, DMARC, and MX records.
Postfix and PowerMTA Tuning: Optimize performance and queue management.
Python for Email Analytics: Use Python for data analysis, automation scripts, and email deliverability audits.

Soft Skills

Email Copywriting: Learn to craft compelling, conversion-driven email content.
Cross-Channel Strategy: Integrate email marketing with LinkedIn, SMS, and other outreach channels for comprehensive campaigns.

Recommended Tools to Master

Deliverability Monitoring Tools:
250Ok (Validity)
GlockApps
Postmaster by Gmail
EmailConsul
Warmbox

Anti-Spam Monitoring & Reputation Tools:
MXToolbox
Talos Intelligence
Barracuda Central

Marketing Automation:
ActiveCampaign
HubSpot
Autopilot

Testing & Preview Tools:
Litmus
Email on Acid

Lead Generation & Outreach Tools:
Instantly
Lemlist
Apollo.io
Woodpecker.co
Data Tools:
Hunter.io
Snov.io
Clearbit

10-Email Optimizing Bounce Handling For Marketers

In email marketing, maintaining a low bounce rate is crucial for deliverability, sender reputation, and the overall success of email campaigns. Bounces occur when an email fails to reach the intended recipient, leading to lost opportunities for engagement.

There are two types of bounces: hard bounces (permanent failures) and soft bounces (temporary issues). If these bounces aren’t handled properly, they can significantly affect email deliverability, damage IP and domain reputation, and reduce the effectiveness of marketing efforts.

This case study explores a scenario where an email marketing team at an e-commerce company struggled with high bounce rates, particularly after launching a series of new promotional campaigns. The goal was to improve bounce handling practices, reduce bounce rates, and enhance overall deliverability.

Objective:

To reduce bounce rates and improve email deliverability by optimizing the management of bounced emails, ensuring list hygiene, and enhancing email campaign strategies.

Initial Challenges:

The marketing team faced several issues that contributed to high bounce rates:

Poor List Hygiene: The team had not cleaned their email list regularly, resulting in a significant number of invalid email addresses.
Insufficient Bounce Management: Hard bounces were not removed promptly, and soft bounces were being retried too frequently, leading to repeated delivery failures.
Lack of Authentication: The emails lacked proper authentication protocols, such as SPF and DKIM, causing many ISPs to reject them or flag them as suspicious.
Content Triggers: Certain campaigns had high bounce rates due to content flagged by spam filters, such as overly promotional language and excessive use of images.

Step-by-Step Approach to Optimize Bounce Handling:

Error Identification Process:

  • Bounce Codes: Analyze bounce codes provided by ISPs. These codes indicate specific issues, such as invalid addresses (hard bounce), temporary server issues (soft bounce), or content-related rejections.
  • Authentication Failures: Monitor failures related to SPF, DKIM, and DMARC authentication. Failures in these protocols may result in delivery rejections.
  • Feedback Loops (FBL): Set up FBLs with major ISPs to receive spam complaint data. High complaint rates are a warning sign of errors in targeting or list quality.
  • ISP-Specific Issues: Monitor inbox placement reports from ESPs and tools like Return Path to check if any ISPs are particularly resistant to your emails.
  • Domain Reputation: Use reputation monitoring tools (e.g., Google Postmaster, SenderScore) to identify domain or IP reputation issues.
  • Spam Filters: Check if your emails are being flagged by spam filters due to content triggers, poor formatting, or overly promotional language.

1. Email List Hygiene

Problem: The marketing team was sending emails to an outdated list containing inactive, invalid, and misspelled addresses.
Solution:
=> List Cleaning: The team conducted an in-depth list cleaning process using email verification tools like ZeroBounce and NeverBounce to remove invalid and undeliverable addresses. This helped reduce hard bounces immediately.

=> Double Opt-In: They implemented a double opt-in process for new subscribers to ensure email validity from the start, reducing the chances of fake or incorrect email addresses entering the list.

Outcome: Hard bounce rates dropped by 50% after the first round of list cleaning, leading to an immediate improvement in sender reputation.

2. Hard and Soft Bounce Management

Problem: The team was retrying failed email deliveries excessively, especially for soft bounces, which annoyed some ISPs and further damaged sender’s reputation.

Solution:
=> Hard Bounce Removal: They set up automated processes to remove hard bounces immediately after the first occurrence, ensuring they weren’t included in future sends.
=> Soft Bounce Handling: Soft bounces were monitored more closely, with a threshold set to retry emails only twice. After three soft bounces over consecutive campaigns, the email addresses were moved to a suppression list.

    Threshold: Depending on your email sending frequency and strategy, the exact number may vary, but 3 to 5 soft bounces is a common rule of thumb.
ISP Guidelines: Some ISPs may have their own soft bounce limits, and monitoring the responses can help you fine-tune your threshold.

Best Practices:

  • Use a Bounce Management System: Centralized bounce handling can be done using email service provider (ESP) tools that automatically capture, analyze, and report bounce codes.
  • Real-Time Bounce Tracking: Implement real-time tracking for bounces so that your system can immediately process and react to bounce types (soft vs. hard).
  • Create Suppression Lists: Set up centralized suppression lists for hard bounces, invalid addresses, and users who have marked emails as spam. This ensures that bounces are managed across all campaigns and tools.
  • Consolidate Bounce Logs: Integrate your bounce logs from multiple sending platforms to avoid duplication and ensure every email address is handled properly across campaigns.
  • Monitor Feedback Loops (FBL): Centralize spam complaint data from ISPs to ensure prompt removal of flagged addresses.

Outcome: The team saw a significant reduction in the volume of emails sent to non-deliverable addresses, and overall soft bounce rates fell by 30%.

3. Improving Authentication Protocols

Problem: A lack of proper email authentication led ISPs to reject or filter out legitimate emails.
Solution:
SPF and DKIM: The team implemented SPF and DKIM authentication to prove that emails were being sent by authorized servers and hadn’t been altered during transit.
DMARC Policies: They also configured DMARC policies to further enhance security and provide reporting on email authentication issues.

Outcome: With SPF, DKIM, and DMARC properly set up, bounce rates related to authentication failures were minimized, and deliverability improved by 15%.
4. Content Optimization

Problem: Some campaigns triggered spam filters due to poor content choices, such as using all caps in subject lines, too many promotional keywords, and unoptimized images.
Solution:
Subject Line Testing: The team ran A/B tests to find more balanced and effective subject lines that didn’t trigger spam filters.
HTML Optimization: They optimized the HTML structure of their emails, reducing image-heavy content and ensuring the code was clean and responsive.
Avoiding Spammy Language: The team reduced the use of overly promotional words and phrases like “FREE,” “BUY NOW,” and “LIMITED TIME,” which often triggered spam filters.

Outcome: After optimizing content, spam complaints decreased, and soft bounces related to content issues dropped by 20%.
5. Throttling and Sending Practices

Problem: Sending too many emails at once was overwhelming some ISPs, resulting in delivery blocks.
Solution:
Throttling: The team introduced email throttling to gradually send emails, preventing large volumes from being sent in a short period.
Segmentation: By segmenting their audience, they prioritized sending emails to the most engaged users first, which improved their overall sender reputation.

Segmentation Rating System & Strategies:

  • Engagement Metrics: Use engagement rates like open rates, click-through rates, and conversion rates to assign scores to each email address.
    • High-engagement users (e.g., those who open or click frequently) should be rated highly.
    • Low-engagement or inactive users can be assigned a lower score or flagged for a re-engagement campaign.
  • Bounce and Complaint History: If an email address has a history of bounces or spam complaints, it should be given a low rating or suppressed altogether.
  • Segmentation: Create separate ratings for each list segment based on factors such as the age of the list, source (organic vs. purchased), and engagement history.
  • List Age: Older lists that haven’t been cleaned or engaged with in a while may warrant a lower rating.
  • Assign Ratings:
    • A-Rating: Highly engaged and active users.
    • B-Rating: Moderately engaged, possible re-engagement candidates.
    • C-Rating: Inactive or unengaged users, likely to be pruned or re-engaged.

Segmentation Strategies:

  • Engagement-Based Segmentation:
    • Active Subscribers: Create a segment of users who frequently open or click emails. These are your most valuable subscribers and should be targeted with more frequent or personalized content.
    • Inactive Subscribers: Segment users who haven’t opened or clicked an email in a defined time frame (e.g., 6 months). You can send them a re-engagement campaign or move them to a suppression list if they remain inactive.
  • Demographic-Based Segmentation:
    • Use demographic data like location, gender, or age to send targeted offers. For example, if you’re marketing a retail brand, you can send location-specific promotions.
  • Behavioral Segmentation:
    • Purchase History: Segment users based on their purchase behavior. Send follow-up emails, upsell offers, or loyalty rewards based on past purchases.
    • Browsing Activity: For e-commerce businesses, segment users based on their browsing behavior on your website (e.g., sending product recommendations based on recently viewed items).
  • Content Preferences: Based on user preferences (from past interactions or surveys), send segmented content that matches their interests, whether it’s product-focused, informative, or educational.
  • Re-Engagement Segmentation: Create segments specifically for re-engagement campaigns targeting users who have not interacted in a certain period.

 By using segmentation, you’ll improve the relevance of your emails, reduce bounce rates, and enhance engagement. Well-segmented campaigns also help ISPs recognize your emails as valuable and legitimate, boosting your deliverability.

Outcome: Throttling reduced ISP-related blocks, and segmentation ensured better engagement, further improving sender reputation and reducing bounces.

Results:
By implementing these bounce-handling optimizations, the email marketing team was able to achieve the following:
Reduced Hard Bounce Rates by 50%: Thanks to improved list hygiene and prompt hard bounce removal.
Lowered Soft Bounce Rates by 30%: Through better handling of soft bounces and limiting retries.
Increased Deliverability by 20%: Authentication improvements and content optimization helped emails bypass spam filters and reach the inbox.
Boosted Sender Reputation: Throttling, proper segmentation, and feedback loop monitoring led to fewer complaints and higher engagement rates.

Conclusion:

This case study demonstrates the importance of effective bounce handling and how it can significantly impact email marketing performance. By focusing on list hygiene, proper bounce management, authentication, and content optimization, the marketing team not only reduced bounces but also improved deliverability and engagement. Email marketers should continually monitor their bounce rates, sender reputation, and email content to maintain a healthy email marketing program.

Key Takeaways:

List hygiene is critical to reducing bounces and maintaining a clean email list.
Hard and soft bounce handling should be automated and managed carefully to avoid damage to sender’s reputation.
Authentication protocols (SPF, DKIM, DMARC) are essential for gaining ISP trust and improving email deliverability.
Content optimization helps prevent spam filtering and keeps bounce rates low.
Throttling and segmentation can reduce delivery blocks and improve engagement.

By following these best practices, email marketers can ensure a more effective, high-deliverability email strategy.

Great DB Mongo

Great DB Mongo

There are more than 379 database servers in use around the world today. Among them, MongoDB stands out as a top performer, surpassing databases like HBase, Neo4j, Riak, Memcached, RavenDB, CouchDB, and Redis. Tech giants like Google, Yahoo, and Facebook rely on MongoDB in their production environments.In the DB-Engines ranking, MongoDB holds the 5th position overall, following:

Oracle
MySQL
Microsoft SQL Server
PostgreSQL
MongoDB

Notably, MongoDB is also ranked as the number one NoSQL database.

RDBMS Mongo
Database database
table Collection
Record Document
Joins Embedded Object/Document

Mongo works perfectly with most all programming languages.
Also, mongo works with Windows and Linux with the same performance and without issues.
Mongo provides Replication, Sharding, Aggregation, and indexing features.
Mongo is an object-oriented and schema-less database.

Mongo is based on JavaScript, and all documents (Records) are presented in JSON format. Also, in Mongo, everything is an object. In Mongo 1st field, the compulsory field is _id which is not skippable.

{
_id: numeric or numeric-alphabetical string or,it set automatically. Mongo id is a 12-byte Object id that is a 4-byte time-stamp with 5 bytes of any random value and 3 bytes of a counter value.
}

mongo document stores like
the document content single field, array, sub-document (join), or, an array of sub-document.
{
_id: 1
First name: Anil,
middle name : Jasvantray,
last name: Jalela
Mobile: [9619904949,2573335,2567580]
}

install mongo:-

1 add Repo echo “deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/6.0 multiverse” > /etc/apt/sources.list.d/mongodb-org-6.0.list
2 add Key wget -qO – https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add –
3 update package list apt-get update
4 install mongo server apt-get install -y mongodb-org && apt-get install mongodb-org-server
5 change dir for modification cd /etc/
6 rename conf mv mongod.conf mongod.conf_org
7 vi mongod.conf  and add the below content into this.
8 # mongod.conf

# for documentation of all options, see:
# http://docs.mongodb.org/manual/reference/configuration-options/

# Where and how to store data.
storage:
  dbPath: /var/lib/mongodb
# engine:
# wiredTiger:

# where to write logging data.
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log

# network interfaces
net:
  port: 27017
  bindIp: 0.0.0.0

# how the process runs
processManagement:
  timeZoneInfo: /usr/share/zoneinfo

security:
  keyFile: /etc/keyfile-mongo
authorization: enabled

#operationProfiling:

#replication:
#  replSetName: “election01”

#sharding:

## Enterprise-Only Options:

#auditLog:

#snmp:

9 kerate key file on master for replica set openssl rand -base64 756 > /etc/keyfile-mongo
10 change permission chmod 600 /etc/keyfile-mongo && ll /etc/keyfile-mongo
11 change onership of files chown mongodb:mongodb /etc/mongod.conf /etc/keyfile-mongo
12 start  mongo sudo systemctl start mongod
13 start mongo on system boot sudo systemctl enable mongod
14 check mongo status sudo systemctl status mongod
15 mongo login command mongosh
16 use mongo database use admin
17 set mongo password db.createUser(
{
user: “mongoadmin”,
pwd: passwordPrompt(),
roles: [ { role: “root”, db: “admin” }, “readWriteAnyDatabase” ]
}
)
18   mongosh –username=mongoadmin –password=yourpass –authenticationDatabase admin
19 create database  use nitwings
20 drop database “use nitwings” and then “db.dropDatabase()”
21 create database-specific user db.createUser({
user: “blackpost”,
pwd: passwordPrompt(),
roles: [
{ role: “readWrite”, db: “nitwings” }
],
mechanisms: [“SCRAM-SHA-256”],
authenticationRestrictions: [
{
clientSource: [“0.0.0.0/0”]
}
]
})
22 drop user “use admin”  and then db.dropUser(“blackpost”);
23 show users
db.getUsers()
24 create collection use nitwings
db.createCollection(“testCollection”) 
25
Insert One Document into collection
db.testCollection.insertOne({ name: “test”, value: 123 })
26 Insert many Document into collection
db.testCollection.insertMany([{ name: “blackpost”, value: 789 }, { name: “nitwings”, value: 456 }])
27
create Index
db.testCollection.createIndex({ name: 1 });
28 check index created or not for collection
db.testCollection.getIndexes()
29 find document
nitwings> db.testCollection.findOne({ name: “blackpost” })
{
_id: ObjectId(’66d485a63c3f4eb31f5e739c’),
name: ‘blackpost’,
value: 789
}
30 update document
nitwings> db.testCollection.updateOne({ name: “blackpost” }, { $set: { name: “aniljalela” } })
{
acknowledged: true,
insertedId: null,
matchedCount: 1,
modifiedCount: 1,
upsertedCount: 0
}
nitwings> db.testCollection.findOne({ name: “aniljalela” })
{
_id: ObjectId(’66d485a63c3f4eb31f5e739c’),
name: ‘aniljalela’,
value: 789
}
nitwings>
31 delete document
nitwings> db.testCollection.deleteOne({  name: “aniljalela” })
{ acknowledged: true, deletedCount: 1 }
nitwings>
  show collections and drop collection
nitwings> show collections

nitwings> db..drop()

32 backup database mongodump –db nitwings –out /opt/backup/ –username mongoadmin –password yourpass –authenticationDatabase admin
33 backup database from remote mongodump –host 10.10.10.10 –port 27017 –db nitwings –out /opt/backup/ –username mongoadmin –password yourpass  –authenticationDatabase admin
34 mongo all database mongodump –out /backups/all_databases_backup –username mongoadmin –password yourpass –authenticationDatabase admin

 

35 mongo all database from remote  mongodump –host 10.10.10.10 –port 27017 –out /path/to/backup /opt/backup/ –username mongoadmin –password yourpass –authenticationDatabase admin
36 restore database dump
mongorestore –host 10.10.10.10 –port 27017 –db nitwings –username mongoadmin –password yourpass –authenticationDatabase admin /opt/backup/nitwings
37  drop existing DB and restore db
mongorestore –host 10.10.10.10 –port 27017 –db nitwings –username mongoadmin –password yourpass –authenticationDatabase admin –drop /opt/backup/nitwings
38  restore all databases
mongorestore –host 10.10.10.10 –port 27017 –username mongoadmin –password yourpass –authenticationDatabase admin /opt/backup/
39
drop and restore all databases
mongorestore –host 10.10.10.10 –port 27017 –username mongoadmin –password yourpass –authenticationDatabase admin –drop /opt/backup/
40  restore specific collection
mongorestore –host 10.10.10.10 –port 27017 –db nitwings –collection –username mongoadmin –password yourpass –authenticationDatabase admin /opt/backup/nitwings/.bson

 

If the –drop option is not used with mongorestore, MongoDB restores data without dropping existing collections. If a collection already exists, mongorestore merges the backup with the current data. Documents with the same _id are not overwritten; instead, they are skipped to avoid duplicates. New collections from the dump are created if they don’t exist. This approach can lead to inconsistent or duplicated data, especially if the data structure has changed since the backup was created, potentially causing incorrect query results. Indexes are restored as in the dump, but existing indexes are not recreated, and mismatched index specifications may cause the restore to fail.

Replica set:-
1.1.1.1 production-mongodb-01 master-node1
2.2.2.2 production-mongodb-02 slave-node1
3.3.3.3 production-mongodb-03 slave-node2

(1) Install Mongo on all  servers using the above steps from 1 to 17
(2) un-comment below lines from conf

replication:
  replSetName: “election01”

(3) keyFile: This is used for internal authentication between MongoDB instances in a replica set or sharded cluster.
It ensures that only authorized MongoDB instances can communicate with each other.

scp  /etc/keyfile-mongo  2.2.2.2: /etc/keyfile-mongo
scp  /etc/keyfile-mongo  3.3.3.3: /etc/keyfile-mongo

(4) restart  master and slave and log in to Mongo to start replication

1 login master mongosh –username=mongoadmin –password=yourpass –authenticationDatabase admin
2 Initiate replication rs.initiate()
3 add replica rs.add(“2.2.2.2”)
rs.add(“3.3.3.3”)
4 check replication status rs.status()
5 remove the replica from the replication rs.remove(“hostname:port”)
6 rs.reconfig({})
7 db.serverStatus()
8 db.currentOp()
9 db.repairDatabase()
10 db.stats()
db.collection.stats()