offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?
-
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
2. Safeguard at On-site backup itself : As off-site backup with Replication is not useful only at the time of data infected or corrupted on on-site backup and then replicated, but still useful in case of Original Data and On-site backup fails (building fired, power fluctuation etc.). So keep the on-site backup safe by taking safety measures.
Correct. And because of the async nature we often only take offsite replication once a day or it is very slow. If the original backup becomes corrupted, you often have a bit of time to break replication to protect the off site data, unlike RAID which does so instantly.
Great point, may be I will run replication twice or thrice in a week
You might be able to make replication not touch old data but only send new, as well. So if old data gets corrupted it does not get touched at the remote site.
-
The amount of storage you need in your backup appliance is totally based upon the backup methods and change rate of your data.
Assume you're doing incremental backups and that your daily changes are 10 GB, your original data is 6TGB, and your NAS is 12 TB, you'll be able to fit approximately 600 days of changes on there.
-
What are you using to perform your backups?
While Scott did touch on this
@scottalanmiller said in [offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method
So yes, one device will replicate exactly to the other, that's generally what you want in a situation like this. The first device should be the real backup with separation from the original environment so that an infection in the production environment does not threaten the backup device. The original backup device would carry the grandfather - father - son copies of the data. The replication to the second NAS would copy everything, all of the grandfather - father - sons.
I feel it's important that you understand that you want to separate access to the NAS storage from normal users on the systems it's backing up.
-
@Dashrender said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
The amount of storage you need in your backup appliance is totally based upon the backup methods and change rate of your data.
Assume you're doing incremental backups and that your daily changes are 10 GB, your original data is 6TGB, and your NAS is 12 TB, you'll be able to fit approximately 600 days of changes on there.
BUt there might be dedupe components, as well.
-
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@Dashrender said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
The amount of storage you need in your backup appliance is totally based upon the backup methods and change rate of your data.
Assume you're doing incremental backups and that your daily changes are 10 GB, your original data is 6TGB, and your NAS is 12 TB, you'll be able to fit approximately 600 days of changes on there.
BUt there might be dedupe components, as well.
Very true, just one more thing to know about.
-
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
2. Safeguard at On-site backup itself : As off-site backup with Replication is not useful only at the time of data infected or corrupted on on-site backup and then replicated, but still useful in case of Original Data and On-site backup fails (building fired, power fluctuation etc.). So keep the on-site backup safe by taking safety measures.
Correct. And because of the async nature we often only take offsite replication once a day or it is very slow. If the original backup becomes corrupted, you often have a bit of time to break replication to protect the off site data, unlike RAID which does so instantly.
Great point, may be I will run replication twice or thrice in a week
You might be able to make replication not touch old data but only send new, as well. So if old data gets corrupted it does not get touched at the remote site.
I am not clear here, is that option I need to set with QNAP Remote Replication to do this ?
-
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
2. Safeguard at On-site backup itself : As off-site backup with Replication is not useful only at the time of data infected or corrupted on on-site backup and then replicated, but still useful in case of Original Data and On-site backup fails (building fired, power fluctuation etc.). So keep the on-site backup safe by taking safety measures.
Correct. And because of the async nature we often only take offsite replication once a day or it is very slow. If the original backup becomes corrupted, you often have a bit of time to break replication to protect the off site data, unlike RAID which does so instantly.
Great point, may be I will run replication twice or thrice in a week
You might be able to make replication not touch old data but only send new, as well. So if old data gets corrupted it does not get touched at the remote site.
I am not clear here, is that option I need to set with QNAP Remote Replication to do this ?
I don't use QNAP, I don't know which options they offer and/or expose.
-
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@openit said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
2. Safeguard at On-site backup itself : As off-site backup with Replication is not useful only at the time of data infected or corrupted on on-site backup and then replicated, but still useful in case of Original Data and On-site backup fails (building fired, power fluctuation etc.). So keep the on-site backup safe by taking safety measures.
Correct. And because of the async nature we often only take offsite replication once a day or it is very slow. If the original backup becomes corrupted, you often have a bit of time to break replication to protect the off site data, unlike RAID which does so instantly.
Great point, may be I will run replication twice or thrice in a week
You might be able to make replication not touch old data but only send new, as well. So if old data gets corrupted it does not get touched at the remote site.
I am not clear here, is that option I need to set with QNAP Remote Replication to do this ?
I don't use QNAP, I don't know which options they offer and/or expose.
I see. I may need to dig more on google or QNAP forum to know better.... -
Yes, RSync can do pretty much anything. The question is if QNAP made an interface for that or not.
-
@Dashrender said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
The amount of storage you need in your backup appliance is totally based upon the backup methods and change rate of your data.
Assume you're doing incremental backups and that your daily changes are 10 GB, your original data is 6TGB, and your NAS is 12 TB, you'll be able to fit approximately 600 days of changes on there.
The total amount of space occupied by backup data will be around 6TB, while daily increasing amount will be around 6GB. Because I set for 2months retention period, it will stay always around 6TB. I am using EaseUS Todo Server backup.
-
@Dashrender said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
What are you using to perform your backups?
While Scott did touch on this
@scottalanmiller said in [offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method
So yes, one device will replicate exactly to the other, that's generally what you want in a situation like this. The first device should be the real backup with separation from the original environment so that an infection in the production environment does not threaten the backup device. The original backup device would carry the grandfather - father - son copies of the data. The replication to the second NAS would copy everything, all of the grandfather - father - sons.
I feel it's important that you understand that you want to separate access to the NAS storage from normal users on the systems it's backing up.
I understand this, for server backup, only backup software on Server is having access to NAS Shared folder. And for Server, only me have the access.
No point of users intervention here with Server and Server Backup things.
-
@scottalanmiller said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
@Dashrender said in offsite backup. NAS to NAS Remote Replication on QNAP NASes or other method ?:
The amount of storage you need in your backup appliance is totally based upon the backup methods and change rate of your data.
Assume you're doing incremental backups and that your daily changes are 10 GB, your original data is 6TGB, and your NAS is 12 TB, you'll be able to fit approximately 600 days of changes on there.
BUt there might be dedupe components, as well.
No idea about Dedupe components, I don't think I do have in my environment.
