MyFavMirrors/moonfire-nvr
1
0
Fork 0
mirror of https://github.com/scottlamb/moonfire-nvr.git synced 2024-12-28 08:05:55 -05:00
Code Issues Packages Projects Releases Wiki Activity

more fixes to the upgrade guide

Browse Source
This commit is contained in:
Scott Lamb 2018-01-30 21:14:53 -08:00
parent 9a8ed69047
commit d192d98129
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
guide/schema.md
View File

@ -26,20 +26,23 @@ read-only mode prior to deleting the old database.
First ensure there is sufficient space available for four copies of the First ensure there is sufficient space available for four copies of the
SQLite database: SQLite database:
1. the primary copy, which will be upgraded * copy 1: the copy to upgrade
2. a copy you create manually as a backup so that you can restore if you * copy 2: a backup you manually create so that you can restore if you
discover a problem while running the new software against the upgraded discover a problem while running the new software against the upgraded
database in read-only mode. If disk space is tight, you can save this database in read-only mode. If disk space is tight, you can save this
to a different filesystem than the primary copy. to a different filesystem than the primary copy.
3. internal copies made and destroyed by Moonfire NVR and SQLite during the * copies 3 and 4: internal copies made and destroyed by Moonfire NVR and
upgrade: SQLite during the upgrade:
* during earlier steps, possibly duplicate copies of tables, which * during earlier steps, possibly duplicate copies of tables, which
may occupy space both in the main database and the journal may occupy space both in the main database and the journal
* during the final vacuum step, a complete database copy * during the final vacuum step, a complete database copy
If disk space is tight, and you are _very careful_, you can skip these If disk space is tight, and you are _very careful_, you can skip these
copies with the `--preset-journal=off --no-vacuum` arguments to copies with the `--preset-journal=off --no-vacuum` arguments to
the updater. If you aren't confident in your ability to do this, *don't the updater. If you aren't confident in your ability to do this, *don't
do it*. If you are confident, take additional safety precautions anyway: do it*. If you are confident, take additional safety precautions anyway:
* double-check you have the full backup described above. Without the * double-check you have the full backup described above. Without the
journal any problems during the upgrade will corrupt your database journal any problems during the upgrade will corrupt your database
and you will need to restore. and you will need to restore.
@ -84,11 +87,11 @@ Run the upgrade procedure using the new software binary (here referred to as
`new-moonfire-nvr`; if you are installing from source, you may find it as `new-moonfire-nvr`; if you are installing from source, you may find it as
`target/release/moonfire-nvr`). `target/release/moonfire-nvr`).
$ sudo -u moonfire-nvr new-moonfire-nvr --upgrade $ sudo -u moonfire-nvr new-moonfire-nvr upgrade
Then run the system in read-only mode to verify correct operation: Then run the system in read-only mode to verify correct operation:
$ sudo -u moonfire-nvr new-moonfire-nvr --read-only $ sudo -u moonfire-nvr new-moonfire-nvr run --read-only
Go to the web interface and ensure the system is operating correctly. If Go to the web interface and ensure the system is operating correctly. If
you detect a problem now, you can copy the old database back over the new one. you detect a problem now, you can copy the old database back over the new one.