Backup File Server to DAS
-
@IT-ADMIN said:
i can understand that the new system image overwrite the old damaged one without deleting the damaged system image, it is like bringing the time back to the time that the new system image was taken
Um, no. Overwriting and deleting are the same thing here. It IS deleting. How could it not be? Wouldn't going "back in time" delete anything done since that time?
-
@scottalanmiller said:
@IT-ADMIN said:
i can understand that the new system image overwrite the old damaged one without deleting the damaged system image, it is like bringing the time back to the time that the new system image was taken
Um, no. Overwriting and deleting are the same thing here. It IS deleting. How could it not be? Wouldn't going "back in time" delete anything done since that time?
yes this is what i mean Dear @scottalanmiller
-
anyway i guess it is a complicated process
-
@scottalanmiller said:
@IT-ADMIN said:
i can understand that the new system image overwrite the old damaged one without deleting the damaged system image, it is like bringing the time back to the time that the new system image was taken
Um, no. Overwriting and deleting are the same thing here. It IS deleting. How could it not be? Wouldn't going "back in time" delete anything done since that time?
Heck no. Here we can't remove failed backup or the log of the failed backups everything remains untouch as it was taken, even if it's bad and wasting space. Remove it and someone (or a virus) could be overwriting something to cover it's tracks.
-
@Jason said:
@scottalanmiller said:
@IT-ADMIN said:
i can understand that the new system image overwrite the old damaged one without deleting the damaged system image, it is like bringing the time back to the time that the new system image was taken
Um, no. Overwriting and deleting are the same thing here. It IS deleting. How could it not be? Wouldn't going "back in time" delete anything done since that time?
Heck no. Here we can't remove failed backup or the log of the failed backups everything remains untouch as it was taken, even if it's bad and wasting space. Remove it and someone (or a virus) could be overwriting something to cover it's tracks.
Meaning that the rollback deletes everything and then writes over it (essentially.)
-
@IT-ADMIN said:
anyway i guess it is a complicated process
Actually no, it is rather simple. Often in IT things get confusing when they are simpler, rather than complex. SAN, for example, is super confusing because no one will accept how simplistic it is. They always read into it things that do not exist.
-
@scottalanmiller said:
@Jason said:
@scottalanmiller said:
@IT-ADMIN said:
i can understand that the new system image overwrite the old damaged one without deleting the damaged system image, it is like bringing the time back to the time that the new system image was taken
Um, no. Overwriting and deleting are the same thing here. It IS deleting. How could it not be? Wouldn't going "back in time" delete anything done since that time?
Heck no. Here we can't remove failed backup or the log of the failed backups everything remains untouch as it was taken, even if it's bad and wasting space. Remove it and someone (or a virus) could be overwriting something to cover it's tracks.
Meaning that the rollback deletes everything and then writes over it (essentially.)
we are waiting for the gentleman @jason to clarify his point, is the restore format the hard disk ??
-
@scottalanmiller said:
@IT-ADMIN said:
anyway i guess it is a complicated process
Actually no, it is rather simple. Often in IT things get confusing when they are simpler, rather than complex. SAN, for example, is super confusing because no one will accept how simplistic it is. They always read into it things that do not exist.
yes sometimes we don't accept some stuff simply because they look to us very simple
-
@IT-ADMIN said:
@scottalanmiller said:
@Jason said:
@scottalanmiller said:
@IT-ADMIN said:
i can understand that the new system image overwrite the old damaged one without deleting the damaged system image, it is like bringing the time back to the time that the new system image was taken
Um, no. Overwriting and deleting are the same thing here. It IS deleting. How could it not be? Wouldn't going "back in time" delete anything done since that time?
Heck no. Here we can't remove failed backup or the log of the failed backups everything remains untouch as it was taken, even if it's bad and wasting space. Remove it and someone (or a virus) could be overwriting something to cover it's tracks.
Meaning that the rollback deletes everything and then writes over it (essentially.)
we are waiting for the gentleman @jason to clarify his point, is the restore format the hard disk ??
Let's define what you mean by format first. Can you provide how you are using that term so that we are clear?
-
ok, i like your way of analyzing things, define the terms first, (i'm impressed :))
i mean by format: erase everything -
Okay yes. A system level restore does a full erase either by wiping the drive while applying a full image or by doing a block level rollback. In both cases it is effectively an entire erasure of the system.
-
Just an FYI: formatting would always erase things, but just erasing does not format. Formatting is a specific filesystem operation. So I would use erase in a discussion like this rather than format. Because technically it erases but does not format.
-
@scottalanmiller said:
Just an FYI: formatting would always erase things, but just erasing does not format. Formatting is a specific filesystem operation. So I would use erase in a discussion like this rather than format. Because technically it erases but does not format.
yeah, it is correct, i should use erase rather than format
-
the entire computer backup just finished, it is 58.2 GB and the original is C+D= 113 GB
-
@IT-ADMIN said:
the entire computer backup just finished, it is 58.2 GB and the original is C+D= 113 GB
It only copies the blocks in use not the empty parts of the filesystem
-
@scottalanmiller said:
@IT-ADMIN said:
the entire computer backup just finished, it is 58.2 GB and the original is C+D= 113 GB
It only copies the blocks in use not the empty parts of the filesystem
i see, great, it is very optimal procedure, veeam is really powerful
-
i really thank all IT pro in this topic, you are really helpful people,
thank you for your time, this topic would be a reference for me, it is full of precious information,
i appreciate your efforts guys -
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
the entire computer backup just finished, it is 58.2 GB and the original is C+D= 113 GB
It only copies the blocks in use not the empty parts of the filesystem
i see, great, it is very optimal procedure, veeam is really powerful
All good backup processes work this way.
-
@IT-ADMIN said:
i see, great, it is very optimal procedure, veeam is really powerful
Veeam's technology is pretty impressive. This use of it is similar to StorageCraft.
-
@IT-ADMIN said:
i really thank all IT pro in this topic, you are really helpful people,
thank you for your time, this topic would be a reference for me, it is full of precious information,
i appreciate your efforts guysGlad that it was so useful, both in finding solution and in providing education! It's been a very big thread with a lot of great conversation.
