Not the answer you need?
Register and ask your own question!

Not able to do successful backup

deepaklodeepaklo Current User Role Contributor

[[email protected] log]# cat /root/deepakmongo.yaml 

storage:

 type: filesystem

 filesystem:

  path: /mongo-backup

[[email protected] log]# 

Answers

  • deepaklodeepaklo Current User Role Contributor

    [[email protected] log]# pbm backup --mongodb-uri="mongodb://127.0.0.1:27017"

    Starting backup '2020-11-10T13:59:16Z'.................................

    Error starting backup: no confirmation that backup has successfully started. Replsets status:

    <no replset has started backup>

  • deepaklodeepaklo Current User Role Contributor

    > rs.status()

    {

    "ok" : 0,

    "errmsg" : "not running with --replSet",

    "code" : 76,

    "codeName" : "NoReplicationEnabled"

    }

    > quit

    -- Unsure how to proceed?

  • Akira KuroganeAkira Kurogane Percona Percona Staff Role

    Hi Deepaklo.

    You've encountered the point that PBM is only made to be used with MongoDB running with replication enabled. This is an expectation because production support for Percona Server for MongoDB (or MongoDB Community or Enterprise editions) is only offered when replica sets are used. It is a necessity for making consistent backups because the oplog content is used during restore to return all data to as it was at a single, exact point of time.

    If you have a standalone mongod process you can use mongodump instead of PBM, though.

    Akira

  • deepaklodeepaklo Current User Role Contributor

    Yes , thanks figured out to tweak config and set the replication as it needs for pbo.


    Was able to run successfully.


    Appreciate percona team on the help.

  • Akira KuroganeAkira Kurogane Percona Percona Staff Role

    No worries. Have a good day.

Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.