How are you backing up / Imaging your system???

[_leras]

I got this thing about high quality recordings (vocals or samples) being sent over the internet. Still to this day when i do remix work i still require all parts to be sent to me via courier. Old habits dont die easy.

Screw that. Try and just get the original project zipped and sent if you can.

[Muzik4Life]

to anyone using M'Rflect X:

Have you really seen a speed difference in the backup process?

The time to backup 764GB took 2hrs 34min using X which is the same time using V8 +/- 2-3 mins.....

Did you install the CBT (convinced in V8 this was messing with DPC) block tracker? and do you compress your backups???

[Jac459]

to anyone using M'Rflect X:

Have you really seen a speed difference in the backup process?

The time to backup 764GB took 2hrs 34min using X which is the same time using V8 +/- 2-3 mins.....

Did you install the CBT (convinced in V8 this was messing with DPC) block tracker? and do you compress your backups???

In the "theory" of backups, you are normally looking at 2 KPIs, RTO and RPO.
RTO, recovery time objective (how long you take to get back to a system working after crash).
RPO, recovery point objective (how much data "freshness" you accept to lose when a crash happens --> for example if you backup every week you have a theoretical RPO of 1 week because in worst case scenario, if you crash just before the weekly backup you lose 1 full week of work).

In our music context, if you are an artist, RPO matters much much more than RTO because you can always rebuild a system (mainly everything we use are online except very specific old tools you may have for which anyway you should have a backup). But loosing 1 day of work can really suck, in particular when this day was the day where you got "this" spark of creativity you were looking for since 1 month.

In this context, to me having all your "personal" data like project, custom sounds, presets in a RAID file system does make a lot of sense because you can have an RPO of 0 with the correct RAID.

Having a full system backup should not take much of your energy because you WILL be able to rebuild your system anyway (in 4-8 hours max I would guess) and a full system backup even with daily incremental doesn't do much for RPO.

I think what I am trying to tell you here is that if you spend more energy and money on your RTO instead of your RPO... You are doing something wrong. Except of course if you own a professional studio, welcoming artist (but in this case, instead of a backup management system, you should definitely have a backup ... laptop.

Finally on top of the concept of backup, you have the concept of archiving (which is basically the long term solution when you want to keep cold data for cheap for years or decades). I am not sure that it concerns us too much except for key key projects/sounds libraries.

(PS : don't thank me for these totally unsolicited list of advises).

[Muzik4Life]

to anyone using M'Rflect X:

Have you really seen a speed difference in the backup process?

The time to backup 764GB took 2hrs 34min using X which is the same time using V8 +/- 2-3 mins.....

Did you install the CBT (convinced in V8 this was messing with DPC) block tracker? and do you compress your backups???

In the "theory" of backups, you are normally looking at 2 KPIs, RTO and RPO.
RTO, recovery time objective (how long you take to get back to a system working after crash).
RPO, recovery point objective (how much data "freshness" you accept to lose when a crash happens --> for example if you backup every week you have a theoretical RPO of 1 week because in worst case scenario, if you crash just before the weekly backup you lose 1 full week of work).

In our music context, if you are an artist, RPO matters much much more than RTO because you can always rebuild a system (mainly everything we use are online except very specific old tools you may have for which anyway you should have a backup). But loosing 1 day of work can really suck, in particular when this day was the day where you got "this" spark of creativity you were looking for since 1 month.

In this context, to me having all your "personal" data like project, custom sounds, presets in a RAID file system does make a lot of sense because you can have an RPO of 0 with the correct RAID.

Having a full system backup should not take much of your energy because you WILL be able to rebuild your system anyway (in 4-8 hours max I would guess) and a full system backup even with daily incremental doesn't do much for RPO.

I think what I am trying to tell you here is that if you spend more energy and money on your RTO instead of your RPO... You are doing something wrong. Except of course if you own a professional studio, welcoming artist (but in this case, instead of a backup management system, you should definitely have a backup ... laptop.

Finally on top of the concept of backup, you have the concept of archiving (which is basically the long term solution when you want to keep cold data for cheap for years or decades). I am not sure that it concerns us too much except for key key projects/sounds libraries.

(PS : don't thank me for these totally unsolicited list of advises).

Great Advice... I will say, i got a backup of everything and i mean everything. i even got backups of my backups. I got such a huge library of Sounds/custom presets/projects i'd be stupid not to.

I could never put a price on the work i have lost due to poor backup ethics. OTT doesn't even come to mind when i look at how my backup system is today. My work is priceless, and my backups are worth more than that.....

[Jac459]

to anyone using M'Rflect X:

Have you really seen a speed difference in the backup process?

The time to backup 764GB took 2hrs 34min using X which is the same time using V8 +/- 2-3 mins.....

Did you install the CBT (convinced in V8 this was messing with DPC) block tracker? and do you compress your backups???

In the "theory" of backups, you are normally looking at 2 KPIs, RTO and RPO.
RTO, recovery time objective (how long you take to get back to a system working after crash).
RPO, recovery point objective (how much data "freshness" you accept to lose when a crash happens --> for example if you backup every week you have a theoretical RPO of 1 week because in worst case scenario, if you crash just before the weekly backup you lose 1 full week of work).

In our music context, if you are an artist, RPO matters much much more than RTO because you can always rebuild a system (mainly everything we use are online except very specific old tools you may have for which anyway you should have a backup). But loosing 1 day of work can really suck, in particular when this day was the day where you got "this" spark of creativity you were looking for since 1 month.

In this context, to me having all your "personal" data like project, custom sounds, presets in a RAID file system does make a lot of sense because you can have an RPO of 0 with the correct RAID.

Having a full system backup should not take much of your energy because you WILL be able to rebuild your system anyway (in 4-8 hours max I would guess) and a full system backup even with daily incremental doesn't do much for RPO.

I think what I am trying to tell you here is that if you spend more energy and money on your RTO instead of your RPO... You are doing something wrong. Except of course if you own a professional studio, welcoming artist (but in this case, instead of a backup management system, you should definitely have a backup ... laptop.

Finally on top of the concept of backup, you have the concept of archiving (which is basically the long term solution when you want to keep cold data for cheap for years or decades). I am not sure that it concerns us too much except for key key projects/sounds libraries.

(PS : don't thank me for these totally unsolicited list of advises).

Great Advice... I will say, i got a backup of everything and i mean everything. i even got backups of my backups. I got such a huge library of Sounds/custom presets/projects i'd be stupid not to.

I could never put a price on the work i have lost due to poor backup ethics. OTT doesn't even come to mind when i look at how my backup system is today. My work is priceless, and my backups are worth more than that.....