{
    "content": [
        {
            "type": "text",
            "text": "# RRDDUMP (man)\n\n**Summary:** rrddump - dump the contents of an RRD to XML format\n\n**Synopsis:** rrdtool dump filename.rrd [filename.xml] [--header|-h {none,xsd,dtd}] [--no-header|-n]\n[--daemon|-d address] [> filename.xml]\n\n## Examples\n\n- `To transfer an RRD between architectures, follow these steps:`\n- `1.  On the same system where the RRD was created, use rrdtool dump to export the data to XML`\n- `format.`\n- `2.  Transfer the XML dump to the target system.`\n- `3.  Run rrdtool restore to create a new RRD from the XML dump. See rrdrestore for details.`\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (3 lines)\n- **DESCRIPTION** (30 lines)\n- **EXAMPLES** (9 lines)\n- **ENVIRONMENT VARIABLES** (7 lines)\n- **AUTHOR** (5 lines)\n\n## Full Content\n\n### NAME\n\nrrddump - dump the contents of an RRD to XML format\n\n### SYNOPSIS\n\nrrdtool dump filename.rrd [filename.xml] [--header|-h {none,xsd,dtd}] [--no-header|-n]\n[--daemon|-d address] [> filename.xml]\n\n### DESCRIPTION\n\nThe dump function writes the contents of an RRD in human readable (?) XML format to a file or\nto stdout. This format can be read by rrdrestore. Together they allow you to transfer your\nfiles from one computer architecture to another as well to manipulate the contents of an RRD\nfile in a somewhat more convenient manner.\n\nfilename.rrd\nThe name of the RRD you want to dump.\n\nfilename.xml\nThe (optional) filename that you want to write the XML output to.  If not specified,\nthe XML will be printed to stdout.\n\n--header|-h {none,xsd,dtd}\nBy default RRDtool will add a dtd header to the xml file. Here you can customize this\nto and xsd header or no header at all.\n\n--no-header|-n\nA shortcut for --header=none.\n\nIf you want to restore the dump with RRDtool 1.2 you should use the --no-header\noption since 1.2 cannot deal with xml headers.\n\n--daemon|-d address\nAddress of the rrdcached daemon. If specified, a \"flush\" command is sent to the\nserver before reading the RRD files. This allows rrdtool to return fresh data even if\nthe daemon is configured to cache values for a long time.  For a list of accepted\nformats, see the -l option in the rrdcached manual.\n\nrrdtool dump --daemon unix:/var/run/rrdcached.sock /var/lib/rrd/foo.rrd\n\n### EXAMPLES\n\nTo transfer an RRD between architectures, follow these steps:\n\n1.  On the same system where the RRD was created, use rrdtool dump to export the data to XML\nformat.\n\n2.  Transfer the XML dump to the target system.\n\n3.  Run rrdtool restore to create a new RRD from the XML dump. See rrdrestore for details.\n\n### ENVIRONMENT VARIABLES\n\nThe following environment variables may be used to change the behavior of \"rrdtool dump\":\n\nRRDCACHEDADDRESS\nIf this environment variable is set it will have the same effect as specifying the\n\"--daemon\" option on the command line. If both are present, the command line argument\ntakes precedence.\n\n### AUTHOR\n\nTobias Oetiker <tobi@oetiker.ch>\n\n\n\n1.7.2                                        2022-03-17                                   RRDDUMP(1)\n\n"
        }
    ],
    "structuredContent": {
        "command": "RRDDUMP",
        "section": "",
        "mode": "man",
        "summary": "rrddump - dump the contents of an RRD to XML format",
        "synopsis": "rrdtool dump filename.rrd [filename.xml] [--header|-h {none,xsd,dtd}] [--no-header|-n]\n[--daemon|-d address] [> filename.xml]",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [
            "To transfer an RRD between architectures, follow these steps:",
            "1.  On the same system where the RRD was created, use rrdtool dump to export the data to XML",
            "format.",
            "2.  Transfer the XML dump to the target system.",
            "3.  Run rrdtool restore to create a new RRD from the XML dump. See rrdrestore for details."
        ],
        "see_also": [],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 30,
                "subsections": []
            },
            {
                "name": "EXAMPLES",
                "lines": 9,
                "subsections": []
            },
            {
                "name": "ENVIRONMENT VARIABLES",
                "lines": 7,
                "subsections": []
            },
            {
                "name": "AUTHOR",
                "lines": 5,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "rrddump - dump the contents of an RRD to XML format\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "rrdtool dump filename.rrd [filename.xml] [--header|-h {none,xsd,dtd}] [--no-header|-n]\n[--daemon|-d address] [> filename.xml]\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "The dump function writes the contents of an RRD in human readable (?) XML format to a file or\nto stdout. This format can be read by rrdrestore. Together they allow you to transfer your\nfiles from one computer architecture to another as well to manipulate the contents of an RRD\nfile in a somewhat more convenient manner.\n\nfilename.rrd\nThe name of the RRD you want to dump.\n\nfilename.xml\nThe (optional) filename that you want to write the XML output to.  If not specified,\nthe XML will be printed to stdout.\n\n--header|-h {none,xsd,dtd}\nBy default RRDtool will add a dtd header to the xml file. Here you can customize this\nto and xsd header or no header at all.\n\n--no-header|-n\nA shortcut for --header=none.\n\nIf you want to restore the dump with RRDtool 1.2 you should use the --no-header\noption since 1.2 cannot deal with xml headers.\n\n--daemon|-d address\nAddress of the rrdcached daemon. If specified, a \"flush\" command is sent to the\nserver before reading the RRD files. This allows rrdtool to return fresh data even if\nthe daemon is configured to cache values for a long time.  For a list of accepted\nformats, see the -l option in the rrdcached manual.\n\nrrdtool dump --daemon unix:/var/run/rrdcached.sock /var/lib/rrd/foo.rrd\n",
                "subsections": []
            },
            "EXAMPLES": {
                "content": "To transfer an RRD between architectures, follow these steps:\n\n1.  On the same system where the RRD was created, use rrdtool dump to export the data to XML\nformat.\n\n2.  Transfer the XML dump to the target system.\n\n3.  Run rrdtool restore to create a new RRD from the XML dump. See rrdrestore for details.\n",
                "subsections": []
            },
            "ENVIRONMENT VARIABLES": {
                "content": "The following environment variables may be used to change the behavior of \"rrdtool dump\":\n\nRRDCACHEDADDRESS\nIf this environment variable is set it will have the same effect as specifying the\n\"--daemon\" option on the command line. If both are present, the command line argument\ntakes precedence.\n",
                "subsections": []
            },
            "AUTHOR": {
                "content": "Tobias Oetiker <tobi@oetiker.ch>\n\n\n\n1.7.2                                        2022-03-17                                   RRDDUMP(1)",
                "subsections": []
            }
        }
    }
}