What should I backup before upgrade?
up vote
2
down vote
favorite
I realise that there are many similar questions like this but I have not found one that answers my explicit query.
I am still using Linux Fedora 20, and it is well past the time when I should upgrade to the latest version. I have started using Deja Dup for backup of my /home directory on to an external one terabyte hard drive; my question is, please, what other directories should I backup as well before I start the installation?
backup upgrade
add a comment |
up vote
2
down vote
favorite
I realise that there are many similar questions like this but I have not found one that answers my explicit query.
I am still using Linux Fedora 20, and it is well past the time when I should upgrade to the latest version. I have started using Deja Dup for backup of my /home directory on to an external one terabyte hard drive; my question is, please, what other directories should I backup as well before I start the installation?
backup upgrade
Why do a backup specifically before upgrading? Your backup process should be happening regularly and automatically. You do have backups right ?
– Criggie
Dec 26 '16 at 22:16
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I realise that there are many similar questions like this but I have not found one that answers my explicit query.
I am still using Linux Fedora 20, and it is well past the time when I should upgrade to the latest version. I have started using Deja Dup for backup of my /home directory on to an external one terabyte hard drive; my question is, please, what other directories should I backup as well before I start the installation?
backup upgrade
I realise that there are many similar questions like this but I have not found one that answers my explicit query.
I am still using Linux Fedora 20, and it is well past the time when I should upgrade to the latest version. I have started using Deja Dup for backup of my /home directory on to an external one terabyte hard drive; my question is, please, what other directories should I backup as well before I start the installation?
backup upgrade
backup upgrade
edited Dec 26 '16 at 21:48
Gilles
525k12710491578
525k12710491578
asked Dec 25 '16 at 11:57
Harry Weston
67411429
67411429
Why do a backup specifically before upgrading? Your backup process should be happening regularly and automatically. You do have backups right ?
– Criggie
Dec 26 '16 at 22:16
add a comment |
Why do a backup specifically before upgrading? Your backup process should be happening regularly and automatically. You do have backups right ?
– Criggie
Dec 26 '16 at 22:16
Why do a backup specifically before upgrading? Your backup process should be happening regularly and automatically. You do have backups right ?
– Criggie
Dec 26 '16 at 22:16
Why do a backup specifically before upgrading? Your backup process should be happening regularly and automatically. You do have backups right ?
– Criggie
Dec 26 '16 at 22:16
add a comment |
3 Answers
3
active
oldest
votes
up vote
2
down vote
accepted
For /etc, use etckeeper. It stores /etc under version control, taking care of preserving permissions and ownership. Before an upgrade, make sure that you've committed the latest changes, and set a tag (e.g. git tag fedora20-before-upgrade).
Also make a list of all the packages you currently have installed (rpm -ql >/var/tmp/fedora20-package-list.txt). That could be useful if the upgrade ends up removing some package to make dependencies work.
Other than that, there isn't anything that's especially at risk during upgrades. Home directories and local installations (e.g. under /usr/local) should not be touched, and the rest of the system should be managed by the upgrade. Of course, like any other time, you should have up-to-date backups in case something unexpected happens.
add a comment |
up vote
3
down vote
I do use Debian, so I can't give you any distribution specific hints. Anyway, before upgrading my system, I usually backup:
- /home
- /etc
- /usr/local (unless I have it on a dedicated partition)
- the list of all installed packages (which I can generate with
dpkgandapt, so I am expecting you can do the same withyumorrpm)
I would also suggest to read the relase notes for your distribution; it should outline all the steps you need to perform before starting the upgrade (backup included).
2
Just a note: you can backup/etcfor using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.
– Marcelo
Dec 25 '16 at 12:56
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up/mnt//sharedbut would not get/mnt/junk
– Criggie
Dec 26 '16 at 22:18
add a comment |
up vote
0
down vote
I would also include /var.
certainly, wholesale replacement of /var directly in new install would not be advised, but a lot of important user/admin files you will be stored there:
mysql
html
crontab
samba
to name a few.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f332678%2fwhat-should-i-backup-before-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
For /etc, use etckeeper. It stores /etc under version control, taking care of preserving permissions and ownership. Before an upgrade, make sure that you've committed the latest changes, and set a tag (e.g. git tag fedora20-before-upgrade).
Also make a list of all the packages you currently have installed (rpm -ql >/var/tmp/fedora20-package-list.txt). That could be useful if the upgrade ends up removing some package to make dependencies work.
Other than that, there isn't anything that's especially at risk during upgrades. Home directories and local installations (e.g. under /usr/local) should not be touched, and the rest of the system should be managed by the upgrade. Of course, like any other time, you should have up-to-date backups in case something unexpected happens.
add a comment |
up vote
2
down vote
accepted
For /etc, use etckeeper. It stores /etc under version control, taking care of preserving permissions and ownership. Before an upgrade, make sure that you've committed the latest changes, and set a tag (e.g. git tag fedora20-before-upgrade).
Also make a list of all the packages you currently have installed (rpm -ql >/var/tmp/fedora20-package-list.txt). That could be useful if the upgrade ends up removing some package to make dependencies work.
Other than that, there isn't anything that's especially at risk during upgrades. Home directories and local installations (e.g. under /usr/local) should not be touched, and the rest of the system should be managed by the upgrade. Of course, like any other time, you should have up-to-date backups in case something unexpected happens.
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
For /etc, use etckeeper. It stores /etc under version control, taking care of preserving permissions and ownership. Before an upgrade, make sure that you've committed the latest changes, and set a tag (e.g. git tag fedora20-before-upgrade).
Also make a list of all the packages you currently have installed (rpm -ql >/var/tmp/fedora20-package-list.txt). That could be useful if the upgrade ends up removing some package to make dependencies work.
Other than that, there isn't anything that's especially at risk during upgrades. Home directories and local installations (e.g. under /usr/local) should not be touched, and the rest of the system should be managed by the upgrade. Of course, like any other time, you should have up-to-date backups in case something unexpected happens.
For /etc, use etckeeper. It stores /etc under version control, taking care of preserving permissions and ownership. Before an upgrade, make sure that you've committed the latest changes, and set a tag (e.g. git tag fedora20-before-upgrade).
Also make a list of all the packages you currently have installed (rpm -ql >/var/tmp/fedora20-package-list.txt). That could be useful if the upgrade ends up removing some package to make dependencies work.
Other than that, there isn't anything that's especially at risk during upgrades. Home directories and local installations (e.g. under /usr/local) should not be touched, and the rest of the system should be managed by the upgrade. Of course, like any other time, you should have up-to-date backups in case something unexpected happens.
answered Dec 26 '16 at 23:11
Gilles
525k12710491578
525k12710491578
add a comment |
add a comment |
up vote
3
down vote
I do use Debian, so I can't give you any distribution specific hints. Anyway, before upgrading my system, I usually backup:
- /home
- /etc
- /usr/local (unless I have it on a dedicated partition)
- the list of all installed packages (which I can generate with
dpkgandapt, so I am expecting you can do the same withyumorrpm)
I would also suggest to read the relase notes for your distribution; it should outline all the steps you need to perform before starting the upgrade (backup included).
2
Just a note: you can backup/etcfor using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.
– Marcelo
Dec 25 '16 at 12:56
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up/mnt//sharedbut would not get/mnt/junk
– Criggie
Dec 26 '16 at 22:18
add a comment |
up vote
3
down vote
I do use Debian, so I can't give you any distribution specific hints. Anyway, before upgrading my system, I usually backup:
- /home
- /etc
- /usr/local (unless I have it on a dedicated partition)
- the list of all installed packages (which I can generate with
dpkgandapt, so I am expecting you can do the same withyumorrpm)
I would also suggest to read the relase notes for your distribution; it should outline all the steps you need to perform before starting the upgrade (backup included).
2
Just a note: you can backup/etcfor using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.
– Marcelo
Dec 25 '16 at 12:56
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up/mnt//sharedbut would not get/mnt/junk
– Criggie
Dec 26 '16 at 22:18
add a comment |
up vote
3
down vote
up vote
3
down vote
I do use Debian, so I can't give you any distribution specific hints. Anyway, before upgrading my system, I usually backup:
- /home
- /etc
- /usr/local (unless I have it on a dedicated partition)
- the list of all installed packages (which I can generate with
dpkgandapt, so I am expecting you can do the same withyumorrpm)
I would also suggest to read the relase notes for your distribution; it should outline all the steps you need to perform before starting the upgrade (backup included).
I do use Debian, so I can't give you any distribution specific hints. Anyway, before upgrading my system, I usually backup:
- /home
- /etc
- /usr/local (unless I have it on a dedicated partition)
- the list of all installed packages (which I can generate with
dpkgandapt, so I am expecting you can do the same withyumorrpm)
I would also suggest to read the relase notes for your distribution; it should outline all the steps you need to perform before starting the upgrade (backup included).
answered Dec 25 '16 at 12:48
Alessandro Dotti Contra
23527
23527
2
Just a note: you can backup/etcfor using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.
– Marcelo
Dec 25 '16 at 12:56
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up/mnt//sharedbut would not get/mnt/junk
– Criggie
Dec 26 '16 at 22:18
add a comment |
2
Just a note: you can backup/etcfor using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.
– Marcelo
Dec 25 '16 at 12:56
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up/mnt//sharedbut would not get/mnt/junk
– Criggie
Dec 26 '16 at 22:18
2
2
Just a note: you can backup
/etc for using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.– Marcelo
Dec 25 '16 at 12:56
Just a note: you can backup
/etc for using as a reference in the new installationm but never restore these backed up files in this folder blindly after an upgrade. Many things change from version to version, including versions and formats of many config files (with new options, deprecation of others, etc, so you will probably in trouble if you do so.– Marcelo
Dec 25 '16 at 12:56
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up
/mnt//shared but would not get /mnt/junk– Criggie
Dec 26 '16 at 22:18
Excellent list. I also backup /root as a matter of course, and anything that didn't come from a distro-supplied package. So I back up
/mnt//shared but would not get /mnt/junk– Criggie
Dec 26 '16 at 22:18
add a comment |
up vote
0
down vote
I would also include /var.
certainly, wholesale replacement of /var directly in new install would not be advised, but a lot of important user/admin files you will be stored there:
mysql
html
crontab
samba
to name a few.
add a comment |
up vote
0
down vote
I would also include /var.
certainly, wholesale replacement of /var directly in new install would not be advised, but a lot of important user/admin files you will be stored there:
mysql
html
crontab
samba
to name a few.
add a comment |
up vote
0
down vote
up vote
0
down vote
I would also include /var.
certainly, wholesale replacement of /var directly in new install would not be advised, but a lot of important user/admin files you will be stored there:
mysql
html
crontab
samba
to name a few.
I would also include /var.
certainly, wholesale replacement of /var directly in new install would not be advised, but a lot of important user/admin files you will be stored there:
mysql
html
crontab
samba
to name a few.
answered 2 days ago
codechimp
1134
1134
add a comment |
add a comment |
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.
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%2f332678%2fwhat-should-i-backup-before-upgrade%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
Why do a backup specifically before upgrading? Your backup process should be happening regularly and automatically. You do have backups right ?
– Criggie
Dec 26 '16 at 22:16