What filesystem and backup strategy for a small-scale home server?











up vote
2
down vote

favorite












I am rebuilding a home server after my previous one failed (My Odroid C1 with 1GB RAM running Ubuntu 14.04 was just struggling with RAM and other things that made it hang; my mdadm-lvm RAID1 storage system failed entirely, both disks ended up with tons of bad blocks, maybe partly because of the initial system being in a bad state, and I've had a bad experience trying to recover any of the data ...).



I now have a UDOO x86 with 4GB RAM and Ubuntu 18.04 taking care of:




  • a web server (nginx + mysql)

  • a mail server (dovecot + postfix)

  • Nextcloud and its different apps (file storage/sharing, cardDAV, calDAV, IMAP client)


This is to say that it's for simple "family" use, I am not expecting tons of traffic unless I suddenly become famous. Everything works like a charm, except that my eMMC is limited to 32GB and I need storage space. My wishes are:




  • Backup


    1. Data must be stored in places I physically control

    2. Simple to setup from multiple local sources (eMMC + storage of my server, but also ability to backup my laptop) to the same target(s)

    3. Easy to restore file from a backup (if my storage system completely fails/burns/is stolen).



  • Storage


    1. 2TB storage space, to store dovecot mail folders, nextcloud storage files, other ad-hoc storage (e.g. pictures), and some website files

    2. If possible: ability to minimise the risk of backing up errors, and minimise the need to restore from backup when things go wrong

    3. Low maintenance and flexibility to the extent possible



  • Over consideration over my data: I don’t hold strategic data, maybe pictures and documents that I would to keep for the long term as optimally as possible. I would be pissed if I need to restore from the latest monthly, but as long as it’s easy I wouldn’t be totally devastated to have to rewrite my latest article or lost the pictures from my last trip. Of course if this can be easily avoided I’d be more than happy to consider that option. However backed up data need to be errorless.


Reading around dozens of blog or forum posts, I understood that backup is the most important thing. Ideally backup should be done to another machine (to avoid cascading risks being linked to the system we want to backup), at another physical address (to cope with risk of fire, theft, ...), and ideally at multiple locations. I will take the risk to store things just on another drive, and it sounded good to me using restic scheduled with systemd. Please raise a red flag if you think there's much better, otherwise we can move on.



For the storage part, I have to admit I was quite confused by the range of forum and blog posts I've read, which covered a wide range:




  • Some argue that the most important is backup, and you can just have your system designed to fail. (needs 1 drive with ext4)

  • Others encourage merging multiple drives but with non real-time snapshots: JBOD (MergerFS) + snapRAID (needs at least 2 drives)

  • The rest seem to agree that the best filesystem is ZFS, although it uses a lot of RAM, is rigid (same disk volume) and it’s expensive to expand (needs: Mirror >= 2 drives RAIDZ >= 3 drives RAIDZ2 >= 4 drives)

  • Is it still worth considering Linux software RAID with mdadm + lvm? I've had a bad experience with RAID1...


Given all the above, what would be your recommendation?










share|improve this question







New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • I'm always amazed how monolithic everyone regards backups. It is well worth sorting your data into at least 3 categories: vital, useful, and junk, and putting a lot of effort into reducing the size of the first category, and to backing it up in many different ways and places. Of course, there is no need to backup the last (and inevitably largest) category. Yes, triage requires effort, but why backup your spam mail with as much diligence as the doc or program you spent 3 months writing. And the family will appreciate only having to look through 10 photos instead of 100, mostly the same...
    – meuh
    Nov 13 at 17:55










  • Where did you read I would backup everything?
    – Thomas
    Nov 13 at 21:21















up vote
2
down vote

favorite












I am rebuilding a home server after my previous one failed (My Odroid C1 with 1GB RAM running Ubuntu 14.04 was just struggling with RAM and other things that made it hang; my mdadm-lvm RAID1 storage system failed entirely, both disks ended up with tons of bad blocks, maybe partly because of the initial system being in a bad state, and I've had a bad experience trying to recover any of the data ...).



I now have a UDOO x86 with 4GB RAM and Ubuntu 18.04 taking care of:




  • a web server (nginx + mysql)

  • a mail server (dovecot + postfix)

  • Nextcloud and its different apps (file storage/sharing, cardDAV, calDAV, IMAP client)


This is to say that it's for simple "family" use, I am not expecting tons of traffic unless I suddenly become famous. Everything works like a charm, except that my eMMC is limited to 32GB and I need storage space. My wishes are:




  • Backup


    1. Data must be stored in places I physically control

    2. Simple to setup from multiple local sources (eMMC + storage of my server, but also ability to backup my laptop) to the same target(s)

    3. Easy to restore file from a backup (if my storage system completely fails/burns/is stolen).



  • Storage


    1. 2TB storage space, to store dovecot mail folders, nextcloud storage files, other ad-hoc storage (e.g. pictures), and some website files

    2. If possible: ability to minimise the risk of backing up errors, and minimise the need to restore from backup when things go wrong

    3. Low maintenance and flexibility to the extent possible



  • Over consideration over my data: I don’t hold strategic data, maybe pictures and documents that I would to keep for the long term as optimally as possible. I would be pissed if I need to restore from the latest monthly, but as long as it’s easy I wouldn’t be totally devastated to have to rewrite my latest article or lost the pictures from my last trip. Of course if this can be easily avoided I’d be more than happy to consider that option. However backed up data need to be errorless.


Reading around dozens of blog or forum posts, I understood that backup is the most important thing. Ideally backup should be done to another machine (to avoid cascading risks being linked to the system we want to backup), at another physical address (to cope with risk of fire, theft, ...), and ideally at multiple locations. I will take the risk to store things just on another drive, and it sounded good to me using restic scheduled with systemd. Please raise a red flag if you think there's much better, otherwise we can move on.



For the storage part, I have to admit I was quite confused by the range of forum and blog posts I've read, which covered a wide range:




  • Some argue that the most important is backup, and you can just have your system designed to fail. (needs 1 drive with ext4)

  • Others encourage merging multiple drives but with non real-time snapshots: JBOD (MergerFS) + snapRAID (needs at least 2 drives)

  • The rest seem to agree that the best filesystem is ZFS, although it uses a lot of RAM, is rigid (same disk volume) and it’s expensive to expand (needs: Mirror >= 2 drives RAIDZ >= 3 drives RAIDZ2 >= 4 drives)

  • Is it still worth considering Linux software RAID with mdadm + lvm? I've had a bad experience with RAID1...


Given all the above, what would be your recommendation?










share|improve this question







New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • I'm always amazed how monolithic everyone regards backups. It is well worth sorting your data into at least 3 categories: vital, useful, and junk, and putting a lot of effort into reducing the size of the first category, and to backing it up in many different ways and places. Of course, there is no need to backup the last (and inevitably largest) category. Yes, triage requires effort, but why backup your spam mail with as much diligence as the doc or program you spent 3 months writing. And the family will appreciate only having to look through 10 photos instead of 100, mostly the same...
    – meuh
    Nov 13 at 17:55










  • Where did you read I would backup everything?
    – Thomas
    Nov 13 at 21:21













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I am rebuilding a home server after my previous one failed (My Odroid C1 with 1GB RAM running Ubuntu 14.04 was just struggling with RAM and other things that made it hang; my mdadm-lvm RAID1 storage system failed entirely, both disks ended up with tons of bad blocks, maybe partly because of the initial system being in a bad state, and I've had a bad experience trying to recover any of the data ...).



I now have a UDOO x86 with 4GB RAM and Ubuntu 18.04 taking care of:




  • a web server (nginx + mysql)

  • a mail server (dovecot + postfix)

  • Nextcloud and its different apps (file storage/sharing, cardDAV, calDAV, IMAP client)


This is to say that it's for simple "family" use, I am not expecting tons of traffic unless I suddenly become famous. Everything works like a charm, except that my eMMC is limited to 32GB and I need storage space. My wishes are:




  • Backup


    1. Data must be stored in places I physically control

    2. Simple to setup from multiple local sources (eMMC + storage of my server, but also ability to backup my laptop) to the same target(s)

    3. Easy to restore file from a backup (if my storage system completely fails/burns/is stolen).



  • Storage


    1. 2TB storage space, to store dovecot mail folders, nextcloud storage files, other ad-hoc storage (e.g. pictures), and some website files

    2. If possible: ability to minimise the risk of backing up errors, and minimise the need to restore from backup when things go wrong

    3. Low maintenance and flexibility to the extent possible



  • Over consideration over my data: I don’t hold strategic data, maybe pictures and documents that I would to keep for the long term as optimally as possible. I would be pissed if I need to restore from the latest monthly, but as long as it’s easy I wouldn’t be totally devastated to have to rewrite my latest article or lost the pictures from my last trip. Of course if this can be easily avoided I’d be more than happy to consider that option. However backed up data need to be errorless.


Reading around dozens of blog or forum posts, I understood that backup is the most important thing. Ideally backup should be done to another machine (to avoid cascading risks being linked to the system we want to backup), at another physical address (to cope with risk of fire, theft, ...), and ideally at multiple locations. I will take the risk to store things just on another drive, and it sounded good to me using restic scheduled with systemd. Please raise a red flag if you think there's much better, otherwise we can move on.



For the storage part, I have to admit I was quite confused by the range of forum and blog posts I've read, which covered a wide range:




  • Some argue that the most important is backup, and you can just have your system designed to fail. (needs 1 drive with ext4)

  • Others encourage merging multiple drives but with non real-time snapshots: JBOD (MergerFS) + snapRAID (needs at least 2 drives)

  • The rest seem to agree that the best filesystem is ZFS, although it uses a lot of RAM, is rigid (same disk volume) and it’s expensive to expand (needs: Mirror >= 2 drives RAIDZ >= 3 drives RAIDZ2 >= 4 drives)

  • Is it still worth considering Linux software RAID with mdadm + lvm? I've had a bad experience with RAID1...


Given all the above, what would be your recommendation?










share|improve this question







New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I am rebuilding a home server after my previous one failed (My Odroid C1 with 1GB RAM running Ubuntu 14.04 was just struggling with RAM and other things that made it hang; my mdadm-lvm RAID1 storage system failed entirely, both disks ended up with tons of bad blocks, maybe partly because of the initial system being in a bad state, and I've had a bad experience trying to recover any of the data ...).



I now have a UDOO x86 with 4GB RAM and Ubuntu 18.04 taking care of:




  • a web server (nginx + mysql)

  • a mail server (dovecot + postfix)

  • Nextcloud and its different apps (file storage/sharing, cardDAV, calDAV, IMAP client)


This is to say that it's for simple "family" use, I am not expecting tons of traffic unless I suddenly become famous. Everything works like a charm, except that my eMMC is limited to 32GB and I need storage space. My wishes are:




  • Backup


    1. Data must be stored in places I physically control

    2. Simple to setup from multiple local sources (eMMC + storage of my server, but also ability to backup my laptop) to the same target(s)

    3. Easy to restore file from a backup (if my storage system completely fails/burns/is stolen).



  • Storage


    1. 2TB storage space, to store dovecot mail folders, nextcloud storage files, other ad-hoc storage (e.g. pictures), and some website files

    2. If possible: ability to minimise the risk of backing up errors, and minimise the need to restore from backup when things go wrong

    3. Low maintenance and flexibility to the extent possible



  • Over consideration over my data: I don’t hold strategic data, maybe pictures and documents that I would to keep for the long term as optimally as possible. I would be pissed if I need to restore from the latest monthly, but as long as it’s easy I wouldn’t be totally devastated to have to rewrite my latest article or lost the pictures from my last trip. Of course if this can be easily avoided I’d be more than happy to consider that option. However backed up data need to be errorless.


Reading around dozens of blog or forum posts, I understood that backup is the most important thing. Ideally backup should be done to another machine (to avoid cascading risks being linked to the system we want to backup), at another physical address (to cope with risk of fire, theft, ...), and ideally at multiple locations. I will take the risk to store things just on another drive, and it sounded good to me using restic scheduled with systemd. Please raise a red flag if you think there's much better, otherwise we can move on.



For the storage part, I have to admit I was quite confused by the range of forum and blog posts I've read, which covered a wide range:




  • Some argue that the most important is backup, and you can just have your system designed to fail. (needs 1 drive with ext4)

  • Others encourage merging multiple drives but with non real-time snapshots: JBOD (MergerFS) + snapRAID (needs at least 2 drives)

  • The rest seem to agree that the best filesystem is ZFS, although it uses a lot of RAM, is rigid (same disk volume) and it’s expensive to expand (needs: Mirror >= 2 drives RAIDZ >= 3 drives RAIDZ2 >= 4 drives)

  • Is it still worth considering Linux software RAID with mdadm + lvm? I've had a bad experience with RAID1...


Given all the above, what would be your recommendation?







ubuntu backup filesystems storage






share|improve this question







New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Nov 13 at 15:23









Thomas

111




111




New contributor




Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • I'm always amazed how monolithic everyone regards backups. It is well worth sorting your data into at least 3 categories: vital, useful, and junk, and putting a lot of effort into reducing the size of the first category, and to backing it up in many different ways and places. Of course, there is no need to backup the last (and inevitably largest) category. Yes, triage requires effort, but why backup your spam mail with as much diligence as the doc or program you spent 3 months writing. And the family will appreciate only having to look through 10 photos instead of 100, mostly the same...
    – meuh
    Nov 13 at 17:55










  • Where did you read I would backup everything?
    – Thomas
    Nov 13 at 21:21


















  • I'm always amazed how monolithic everyone regards backups. It is well worth sorting your data into at least 3 categories: vital, useful, and junk, and putting a lot of effort into reducing the size of the first category, and to backing it up in many different ways and places. Of course, there is no need to backup the last (and inevitably largest) category. Yes, triage requires effort, but why backup your spam mail with as much diligence as the doc or program you spent 3 months writing. And the family will appreciate only having to look through 10 photos instead of 100, mostly the same...
    – meuh
    Nov 13 at 17:55










  • Where did you read I would backup everything?
    – Thomas
    Nov 13 at 21:21
















I'm always amazed how monolithic everyone regards backups. It is well worth sorting your data into at least 3 categories: vital, useful, and junk, and putting a lot of effort into reducing the size of the first category, and to backing it up in many different ways and places. Of course, there is no need to backup the last (and inevitably largest) category. Yes, triage requires effort, but why backup your spam mail with as much diligence as the doc or program you spent 3 months writing. And the family will appreciate only having to look through 10 photos instead of 100, mostly the same...
– meuh
Nov 13 at 17:55




I'm always amazed how monolithic everyone regards backups. It is well worth sorting your data into at least 3 categories: vital, useful, and junk, and putting a lot of effort into reducing the size of the first category, and to backing it up in many different ways and places. Of course, there is no need to backup the last (and inevitably largest) category. Yes, triage requires effort, but why backup your spam mail with as much diligence as the doc or program you spent 3 months writing. And the family will appreciate only having to look through 10 photos instead of 100, mostly the same...
– meuh
Nov 13 at 17:55












Where did you read I would backup everything?
– Thomas
Nov 13 at 21:21




Where did you read I would backup everything?
– Thomas
Nov 13 at 21:21










1 Answer
1






active

oldest

votes

















up vote
0
down vote













K.I.S.S. No need to complicate things if there is not a good reason to do so.




  1. RAID is not a backup system, it doesn't protect you against accidental deletion/alteration.


  2. A problem with "snapshots" is that they aren't selective and it is not always easy to recover just a handful of files from them.


  3. If you have a low update rate, a cloud backup could be OK. Usually writing is cheap, reading is expensive, so this is a good solution if you think you'll only have to occasionally restore a couple of files but restoring the whole 2TB is going to be expensive (and slow).


  4. A local disk is a good first step, but if there is a fire/burglar you can lose everything. What you can do is have two backup disks, and swap them regularly, keeping the second disk elsewhere (office/parent/sibling/friend).


  5. A hybrid solution with a monthly backup to local disk (kept outside the house) and frequent backups to the cloud make restoring the system faster, and less expensive, since you can restore most of it from the monthly backup.



PS: I'm not sure the eMMC is designed to support the update rate of a live Linux system.






share|improve this answer





















  • Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
    – Thomas
    Nov 13 at 21:27













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});






Thomas is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375059%2fwhat-filesystem-and-backup-strategy-for-a-small-scale-home-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













K.I.S.S. No need to complicate things if there is not a good reason to do so.




  1. RAID is not a backup system, it doesn't protect you against accidental deletion/alteration.


  2. A problem with "snapshots" is that they aren't selective and it is not always easy to recover just a handful of files from them.


  3. If you have a low update rate, a cloud backup could be OK. Usually writing is cheap, reading is expensive, so this is a good solution if you think you'll only have to occasionally restore a couple of files but restoring the whole 2TB is going to be expensive (and slow).


  4. A local disk is a good first step, but if there is a fire/burglar you can lose everything. What you can do is have two backup disks, and swap them regularly, keeping the second disk elsewhere (office/parent/sibling/friend).


  5. A hybrid solution with a monthly backup to local disk (kept outside the house) and frequent backups to the cloud make restoring the system faster, and less expensive, since you can restore most of it from the monthly backup.



PS: I'm not sure the eMMC is designed to support the update rate of a live Linux system.






share|improve this answer





















  • Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
    – Thomas
    Nov 13 at 21:27

















up vote
0
down vote













K.I.S.S. No need to complicate things if there is not a good reason to do so.




  1. RAID is not a backup system, it doesn't protect you against accidental deletion/alteration.


  2. A problem with "snapshots" is that they aren't selective and it is not always easy to recover just a handful of files from them.


  3. If you have a low update rate, a cloud backup could be OK. Usually writing is cheap, reading is expensive, so this is a good solution if you think you'll only have to occasionally restore a couple of files but restoring the whole 2TB is going to be expensive (and slow).


  4. A local disk is a good first step, but if there is a fire/burglar you can lose everything. What you can do is have two backup disks, and swap them regularly, keeping the second disk elsewhere (office/parent/sibling/friend).


  5. A hybrid solution with a monthly backup to local disk (kept outside the house) and frequent backups to the cloud make restoring the system faster, and less expensive, since you can restore most of it from the monthly backup.



PS: I'm not sure the eMMC is designed to support the update rate of a live Linux system.






share|improve this answer





















  • Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
    – Thomas
    Nov 13 at 21:27















up vote
0
down vote










up vote
0
down vote









K.I.S.S. No need to complicate things if there is not a good reason to do so.




  1. RAID is not a backup system, it doesn't protect you against accidental deletion/alteration.


  2. A problem with "snapshots" is that they aren't selective and it is not always easy to recover just a handful of files from them.


  3. If you have a low update rate, a cloud backup could be OK. Usually writing is cheap, reading is expensive, so this is a good solution if you think you'll only have to occasionally restore a couple of files but restoring the whole 2TB is going to be expensive (and slow).


  4. A local disk is a good first step, but if there is a fire/burglar you can lose everything. What you can do is have two backup disks, and swap them regularly, keeping the second disk elsewhere (office/parent/sibling/friend).


  5. A hybrid solution with a monthly backup to local disk (kept outside the house) and frequent backups to the cloud make restoring the system faster, and less expensive, since you can restore most of it from the monthly backup.



PS: I'm not sure the eMMC is designed to support the update rate of a live Linux system.






share|improve this answer












K.I.S.S. No need to complicate things if there is not a good reason to do so.




  1. RAID is not a backup system, it doesn't protect you against accidental deletion/alteration.


  2. A problem with "snapshots" is that they aren't selective and it is not always easy to recover just a handful of files from them.


  3. If you have a low update rate, a cloud backup could be OK. Usually writing is cheap, reading is expensive, so this is a good solution if you think you'll only have to occasionally restore a couple of files but restoring the whole 2TB is going to be expensive (and slow).


  4. A local disk is a good first step, but if there is a fire/burglar you can lose everything. What you can do is have two backup disks, and swap them regularly, keeping the second disk elsewhere (office/parent/sibling/friend).


  5. A hybrid solution with a monthly backup to local disk (kept outside the house) and frequent backups to the cloud make restoring the system faster, and less expensive, since you can restore most of it from the monthly backup.



PS: I'm not sure the eMMC is designed to support the update rate of a live Linux system.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 13 at 16:51









xenoid

3,4033618




3,4033618












  • Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
    – Thomas
    Nov 13 at 21:27




















  • Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
    – Thomas
    Nov 13 at 21:27


















Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
– Thomas
Nov 13 at 21:27






Thanks a lot @xenoid for your answer. #1 is well understood, but there is still a point in having redundancy, as explained in several others posts (such as question 605364) to ensure continuity of service when a disk fails or minimise downtime. That makes sense as I am running cloud, mail and web services. Which is why I’d like to understand what it would cost while K.I.S.S. #2 is noted, but it seems some backup system allow you to mount a snapshot. #3 and #5 using the cloud are incompatible with my criteria number 1. Thanks a lot for #4, I’ll consider that
– Thomas
Nov 13 at 21:27












Thomas is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















Thomas is a new contributor. Be nice, and check out our Code of Conduct.













Thomas is a new contributor. Be nice, and check out our Code of Conduct.












Thomas is a new contributor. Be nice, and check out our Code of Conduct.















 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375059%2fwhat-filesystem-and-backup-strategy-for-a-small-scale-home-server%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How do I know what Microsoft account the skydrive app is syncing to?

When does type information flow backwards in C++?

Grease: Live!