Skip to content

Commit ef6de2f

Browse files
author
Bob Grabar
committed
DOCS-156 fixing links
1 parent 0f9c215 commit ef6de2f

7 files changed

+21
-22
lines changed

source/administration/backups.txt

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,30 +4,33 @@ Backup and Restoration Strategies
44

55
.. default-domain:: mongodb
66

7-
This document provides an inventory of database backup strategies for
7+
This document describes database backup strategies for
88
use with MongoDB. This document contains the following sections:
99

1010
- :ref:`backup-overview` and :ref:`backup-considerations` describe the
1111
approaches for backing up your MongoDB environment.
1212

13-
- :ref:`block-level-backup` and :ref:`database-dumps` describe specific
14-
strategies.
15-
1613
- :ref:`sharded-cluster-backups` describes considerations specific to
1714
:term:`sharded clusters <sharded cluster>`.
1815

1916
- :ref:`replica-set-backups` describes considerations
2017
specific to :term:`replica sets <replica set>`.
2118

19+
See also:
20+
21+
- :doc:`/tutorial/backup-databases-with-filesystem-snapshots`
22+
23+
- :doc:`/tutorial/backup-databases-with-binary-database-dumps`
24+
2225
.. _backup-overview:
2326

24-
Backup Overview
25-
---------------
27+
Backup Strategies
28+
-----------------
2629

27-
Production systems should always have some consideration and strategy
30+
For MongoDB production systems, you should implement a strategy
2831
for taking and restoring backups. The goal of a backup strategy is to
29-
produce a full and consistent copy of the data that you can use to
30-
bring up a new or replacement database instance. However, in some
32+
produce a full and consistent copy of the data to use to
33+
bring up a new or replacement database instance. In some
3134
cases, taking backups is difficult or impossible, given large data
3235
volumes, distributed architectures, and data transmission speeds.
3336

@@ -36,15 +39,15 @@ Nevertheless, with MongoDB, there are two major approaches to backups:
3639

3740
- Using system-level tools, like disk image snapshots.
3841

39-
See :ref:`block-level-backup`.
42+
See :doc:`/tutorial/backup-databases-with-filesystem-snapshots`.
4043

4144
- Using various capacities present in the :program:`mongodump` tool.
4245

43-
See :ref:`database-dumps`.
46+
See :doc:`/tutorial/backup-databases-with-binary-database-dumps`.
4447

4548
The methods described in this document operate by copying the data file
4649
on the disk level. If your system does not provide functionality for
47-
this kind of backup, see the section on :ref:`database-dumps`.
50+
this kind of backup, see :doc:`/tutorial/backup-databases-with-binary-database-dumps`.
4851

4952
Ensuring that the state captured by the backup is consistent and usable
5053
is the primary challenge of producing backups of database systems.

source/administration/replication-architectures.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ dedicated :ref:`hidden member <replica-set-hidden-members>` for the
163163
purpose of creating backups.
164164

165165
If this member runs with journaling enabled, you can safely use standard
166-
:ref:`block level backup methods <block-level-backup>` to create a
166+
:doc:`block level backup methods </tutorial/backup-databases-with-filesystem-snapshots>` to create a
167167
backup of this member. Otherwise, if your underlying system does not
168168
support snapshots, you can connect :program:`mongodump` to create a
169169
backup directly from the secondary member. In these cases, use the

source/reference/mongodump.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ from :term:`secondary` members of the set.
212212
Usage
213213
-----
214214

215-
See the ":ref:`backup guide section on database dumps <database-dumps>`"
215+
See the :doc:`/tutorial/backup-databases-with-binary-database-dumps`
216216
for a larger overview of :program:`mongodump` usage. Also see the
217217
":doc:`mongorestore`" document for an overview of the
218218
:program:`mongorestore`, which provides the related inverse

source/reference/mongorestore.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -230,8 +230,8 @@ Options
230230
Usage
231231
-----
232232

233-
See the ":ref:`backup guide section on database dumps
234-
<database-dumps>`" for a larger overview of :program:`mongorestore`
233+
See :doc:`/tutorial/backup-databases-with-binary-database-dumps`
234+
for a larger overview of :program:`mongorestore`
235235
usage. Also see the ":doc:`mongodump`" document for an overview of the
236236
:program:`mongodump`, which provides the related inverse
237237
functionality.

source/tutorial/backup-databases-with-binary-database-dumps.txt

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,6 @@ Backup Databases Using Binary Database Dumps
44

55
.. default-domain:: mongodb
66

7-
.. _database-dumps:
8-
97
This section describes the process for writing the entire contents of
108
your MongoDB instance to a file in a binary format. If
119
disk-level snapshots are not available, this approach
@@ -19,7 +17,7 @@ provides the best option for full system database backups.
1917
these documents.
2018

2119
If your system has disk level snapshot capabilities, consider the
22-
backup methods described in :ref:`block-level-backup`.
20+
backup methods described in :doc:`/tutorial/backup-databases-with-filesystem-snapshots`.
2321

2422
Database Dump with ``mongodump``
2523
--------------------------------

source/tutorial/backup-databases-with-filesystem-snapshots.txt

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,6 @@ Backup Databases Using Block Level Backup Methods
44

55
.. default-domain:: mongodb
66

7-
.. _block-level-backup:
8-
97
This section provides an overview of using disk/block level
108
snapshots (i.e. :term:`LVM` or storage appliance) to backup a MongoDB
119
instance. These tools make a quick block-level backup of the device

source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ shard.
7878
#. Back up the replica set members of the shards that you locked. You
7979
may back up the shards in parallel. For each shard, create a
8080
snapshot. Use the procedures in
81-
:ref:`block-level-backup`.
81+
:doc:`/tutorial/backup-databases-with-filesystem-snapshots`.
8282

8383
#. Unlock all locked replica set members of each shard using the
8484
:method:`db.fsyncUnlock()` method in the :program:`mongo` shell.

0 commit comments

Comments
 (0)