# Backing up large Historian DB - Ideas?

**URL:** <https://forum.inductiveautomation.com/t/backing-up-large-historian-db-ideas/19086>\
**Category:** Ignition\
**Created:** [August 3, 2018, 3:37am UTC](https://forum.inductiveautomation.com/t/backing-up-large-historian-db-ideas/19086 "2018-08-03T03:37:29Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![richardNZ15](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richardnz15/32/33373_2.png) [@richardNZ15](https://forum.inductiveautomation.com/u/richardNZ15)\
**Post date:** [October 6, 2020, 3:50am UTC](https://forum.inductiveautomation.com/t/backing-up-large-historian-db-ideas/19086/5 "2020-10-06T03:50:07Z")

</div>

To anyone finding this post, i found this other post which details how to execute a script to backup the Historian database, excluding the latest created partition.

> [@MySQL Linux Backup Script](http://forum.inductiveautomation.com/t/mysql-linux-backup-script/10172):
>
> I’ve written the following script to backup the last closed historical partition and assosiated data tables for the Ignition historian on Linux. You can schedule this with cron tab and store the backups on a remote windows share or something pretty easily. #!/usr/bin/python import sys import os import datetime import mysql.connector from subprocess import call from optparse import OptionParser def main(argv): #----------------------------------------------------------------------------------…

---

_[View the full topic](https://forum.inductiveautomation.com/t/backing-up-large-historian-db-ideas/19086)._