FreeBSD PKG Backup
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
As I'm finally getting around to reading through the FreeBSD Handbook, I discovered that PKG is taking daily backups of the package database (defined in periodic.conf). My questions are as follows:
- Is a daily pkg backup necessary for a desktop environment?
- What would be the downside to disabling the backup (
daily_backup_pkgdb_enable="NO")? - Why would I ever need to restore a backup of the package database?
freebsd pkg
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
asked Nov 28 at 13:18
bgregs
1379
|
show 1 more comment
up vote
1
down vote
favorite
As I'm finally getting around to reading through the FreeBSD Handbook, I discovered that PKG is taking daily backups of the package database (defined in periodic.conf). My questions are as follows:
- Is a daily pkg backup necessary for a desktop environment?
- What would be the downside to disabling the backup (
daily_backup_pkgdb_enable="NO")? - Why would I ever need to restore a backup of the package database?
freebsd pkg
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
asked Nov 28 at 13:18
bgregs
1379
The package database contains details of every port and package installed on the desktop. If it became corrupted, it may be difficult to update the desktop without doing a fresh installation. All of my installs are scripted, so if the package database became corrupted, I wouldn't even bother with the pkgdb backup.
– Richard Smith
Nov 28 at 17:50
Thanks Richard! Scripting installs sounds like a much better idea (once I settle on a core group of packages). Do you happen to know if the pkg db gets updated after each new package is installed? Or are the daily backup and manually running the backup process the only 2 options (aside from skipping this altogether and running install scripts of known packages)? Just trying to decide if I should keep it automated, or if I disable it, will I need to remember to backup the pkg db manually with each new install?
– bgregs
Nov 28 at 18:07
Why do you want to turn it off? Is there a problem you are attempting to solve?
– Richard Smith
Nov 28 at 18:27
There is no issue I'm trying to solve, I'm just a firm believer in trying to understand what's running in the background. This question stems from my lack of understanding definitely. When I read "automated backup", I got the impression of a lot of wasted space. If it only keeps one daily copy and just overwrites it each day, I'm fine with that approach. Ultimately, I just couldn't find any straightforward answer to the pkg db's role, and wanted to understand it.
– bgregs
Nov 28 at 18:36
1
It keeps about 7 copies. But it is configurable. See/usr/local/etc/periodic/daily/411.pkg-backup.
– Richard Smith
Nov 28 at 18:42
|
show 1 more comment
up vote
1
down vote
favorite
up vote
1
down vote
favorite
As I'm finally getting around to reading through the FreeBSD Handbook, I discovered that PKG is taking daily backups of the package database (defined in periodic.conf). My questions are as follows:
- Is a daily pkg backup necessary for a desktop environment?
- What would be the downside to disabling the backup (
daily_backup_pkgdb_enable="NO")? - Why would I ever need to restore a backup of the package database?
freebsd pkg
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
asked Nov 28 at 13:18
bgregs
1379
As I'm finally getting around to reading through the FreeBSD Handbook, I discovered that PKG is taking daily backups of the package database (defined in periodic.conf). My questions are as follows:
- Is a daily pkg backup necessary for a desktop environment?
- What would be the downside to disabling the backup (
daily_backup_pkgdb_enable="NO")? - Why would I ever need to restore a backup of the package database?
freebsd pkg
freebsd pkg
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
asked Nov 28 at 13:18
bgregs
1379
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
asked Nov 28 at 13:18
bgregs
1379
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
edited Nov 28 at 15:01
Rui F Ribeiro
38.4k1478127
38.4k1478127
asked Nov 28 at 13:18
bgregs
1379
asked Nov 28 at 13:18
bgregs
1379
asked Nov 28 at 13:18
bgregs
1379
1379
The package database contains details of every port and package installed on the desktop. If it became corrupted, it may be difficult to update the desktop without doing a fresh installation. All of my installs are scripted, so if the package database became corrupted, I wouldn't even bother with the pkgdb backup.
– Richard Smith
Nov 28 at 17:50
Thanks Richard! Scripting installs sounds like a much better idea (once I settle on a core group of packages). Do you happen to know if the pkg db gets updated after each new package is installed? Or are the daily backup and manually running the backup process the only 2 options (aside from skipping this altogether and running install scripts of known packages)? Just trying to decide if I should keep it automated, or if I disable it, will I need to remember to backup the pkg db manually with each new install?
– bgregs
Nov 28 at 18:07
Why do you want to turn it off? Is there a problem you are attempting to solve?
– Richard Smith
Nov 28 at 18:27
There is no issue I'm trying to solve, I'm just a firm believer in trying to understand what's running in the background. This question stems from my lack of understanding definitely. When I read "automated backup", I got the impression of a lot of wasted space. If it only keeps one daily copy and just overwrites it each day, I'm fine with that approach. Ultimately, I just couldn't find any straightforward answer to the pkg db's role, and wanted to understand it.
– bgregs
Nov 28 at 18:36
1
It keeps about 7 copies. But it is configurable. See/usr/local/etc/periodic/daily/411.pkg-backup.
– Richard Smith
Nov 28 at 18:42
|
show 1 more comment
The package database contains details of every port and package installed on the desktop. If it became corrupted, it may be difficult to update the desktop without doing a fresh installation. All of my installs are scripted, so if the package database became corrupted, I wouldn't even bother with the pkgdb backup.
– Richard Smith
Nov 28 at 17:50
Thanks Richard! Scripting installs sounds like a much better idea (once I settle on a core group of packages). Do you happen to know if the pkg db gets updated after each new package is installed? Or are the daily backup and manually running the backup process the only 2 options (aside from skipping this altogether and running install scripts of known packages)? Just trying to decide if I should keep it automated, or if I disable it, will I need to remember to backup the pkg db manually with each new install?
– bgregs
Nov 28 at 18:07
Why do you want to turn it off? Is there a problem you are attempting to solve?
– Richard Smith
Nov 28 at 18:27
There is no issue I'm trying to solve, I'm just a firm believer in trying to understand what's running in the background. This question stems from my lack of understanding definitely. When I read "automated backup", I got the impression of a lot of wasted space. If it only keeps one daily copy and just overwrites it each day, I'm fine with that approach. Ultimately, I just couldn't find any straightforward answer to the pkg db's role, and wanted to understand it.
– bgregs
Nov 28 at 18:36
1
It keeps about 7 copies. But it is configurable. See/usr/local/etc/periodic/daily/411.pkg-backup.
– Richard Smith
Nov 28 at 18:42
The package database contains details of every port and package installed on the desktop. If it became corrupted, it may be difficult to update the desktop without doing a fresh installation. All of my installs are scripted, so if the package database became corrupted, I wouldn't even bother with the pkgdb backup.
– Richard Smith
Nov 28 at 17:50
The package database contains details of every port and package installed on the desktop. If it became corrupted, it may be difficult to update the desktop without doing a fresh installation. All of my installs are scripted, so if the package database became corrupted, I wouldn't even bother with the pkgdb backup.
– Richard Smith
Nov 28 at 17:50
Thanks Richard! Scripting installs sounds like a much better idea (once I settle on a core group of packages). Do you happen to know if the pkg db gets updated after each new package is installed? Or are the daily backup and manually running the backup process the only 2 options (aside from skipping this altogether and running install scripts of known packages)? Just trying to decide if I should keep it automated, or if I disable it, will I need to remember to backup the pkg db manually with each new install?
– bgregs
Nov 28 at 18:07
Thanks Richard! Scripting installs sounds like a much better idea (once I settle on a core group of packages). Do you happen to know if the pkg db gets updated after each new package is installed? Or are the daily backup and manually running the backup process the only 2 options (aside from skipping this altogether and running install scripts of known packages)? Just trying to decide if I should keep it automated, or if I disable it, will I need to remember to backup the pkg db manually with each new install?
– bgregs
Nov 28 at 18:07
Why do you want to turn it off? Is there a problem you are attempting to solve?
– Richard Smith
Nov 28 at 18:27
Why do you want to turn it off? Is there a problem you are attempting to solve?
– Richard Smith
Nov 28 at 18:27
There is no issue I'm trying to solve, I'm just a firm believer in trying to understand what's running in the background. This question stems from my lack of understanding definitely. When I read "automated backup", I got the impression of a lot of wasted space. If it only keeps one daily copy and just overwrites it each day, I'm fine with that approach. Ultimately, I just couldn't find any straightforward answer to the pkg db's role, and wanted to understand it.
– bgregs
Nov 28 at 18:36
There is no issue I'm trying to solve, I'm just a firm believer in trying to understand what's running in the background. This question stems from my lack of understanding definitely. When I read "automated backup", I got the impression of a lot of wasted space. If it only keeps one daily copy and just overwrites it each day, I'm fine with that approach. Ultimately, I just couldn't find any straightforward answer to the pkg db's role, and wanted to understand it.
– bgregs
Nov 28 at 18:36
1
1
It keeps about 7 copies. But it is configurable. See
/usr/local/etc/periodic/daily/411.pkg-backup.– Richard Smith
Nov 28 at 18:42
It keeps about 7 copies. But it is configurable. See
/usr/local/etc/periodic/daily/411.pkg-backup.– Richard Smith
Nov 28 at 18:42
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484663%2ffreebsd-pkg-backup%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The package database contains details of every port and package installed on the desktop. If it became corrupted, it may be difficult to update the desktop without doing a fresh installation. All of my installs are scripted, so if the package database became corrupted, I wouldn't even bother with the pkgdb backup.
– Richard Smith
Nov 28 at 17:50
Thanks Richard! Scripting installs sounds like a much better idea (once I settle on a core group of packages). Do you happen to know if the pkg db gets updated after each new package is installed? Or are the daily backup and manually running the backup process the only 2 options (aside from skipping this altogether and running install scripts of known packages)? Just trying to decide if I should keep it automated, or if I disable it, will I need to remember to backup the pkg db manually with each new install?
– bgregs
Nov 28 at 18:07
Why do you want to turn it off? Is there a problem you are attempting to solve?
– Richard Smith
Nov 28 at 18:27
There is no issue I'm trying to solve, I'm just a firm believer in trying to understand what's running in the background. This question stems from my lack of understanding definitely. When I read "automated backup", I got the impression of a lot of wasted space. If it only keeps one daily copy and just overwrites it each day, I'm fine with that approach. Ultimately, I just couldn't find any straightforward answer to the pkg db's role, and wanted to understand it.
– bgregs
Nov 28 at 18:36
1
It keeps about 7 copies. But it is configurable. See
/usr/local/etc/periodic/daily/411.pkg-backup.– Richard Smith
Nov 28 at 18:42