TeraByte Unlimited

Hi.I have a question regarding Backup:
My Drive C is Bitlocker Enabled and I want to create image from C (Win 10 Installed) when windows is running.I want to restore in case of emergency persisting the Bitlocker Encryption(I don't want to Enable Bitlocker again).
Also I don't want to backup entire drive (Unused Sectors) due to backup time and image size.
My question is which Options must be Enabled or Disabled in Backup Options and Global Settings?
There is an option : Read From Volume.Should I enable this Option??
Any experience with successful restore in similar scenario??

See this KB article: https://www.terabyteunlimited.com/kb/article.php?id=616

And this...

viewtopic.php?f=4&t=1731

Thanks.The topics you suggest was helpful.
According this section:
When restoring a Type A backup image to an unlocked BitLocker partition (to restore in the encrypted state), using Validate Byte-for-Byte is not supported and will fail.
Can I use [Validate Byte-for-Byte] when creating image using VSS on Windows???

Should I enable [Read From Volume] when using VSS on Windows??
and
How to force to create Incremental backup (NOT Differential) when creating Changes-Only backup??

You can use Validate Byte-for-Byte when creating the backup.

You don't normally need to enable the Read From Volume option since VSS handles it automatically. However, outside of Windows (like in TBWinRE) you would need to use Read From Volume.

In the case of the first Changes Only Backup, you would select the full image as the base (this is the same whether creating an incremental chain or differential chain). To create an incremental chain you specify the last incremental as the base for the new backup.

OK Thank.
So in case of creating Batch File for Incremental Backup, How to determine last Backup as Base ? Because the Incremental Backups Filenames are different and variable??
Another Question:
I've read in program Manual that the Number of Incrementals should not be a lot and it's better to get a Full Backup again after a while.Considering the time taken for Full Backup , It's ok to intervally delete only Incrementals and keep first Full Backup and create Incrementals based on first Full Backup again??
and
It's not clear for me that which file should be selected to restore to recenet state: Last Incremental Backup File or Full Backup??

On Sat, 6 Oct 2018 17:22:57 EDT, Backupper wrote:

>OK Thank.
>So in case of creating Batch File for Incremental Backup, How to determine last Backup as Base ? Because the Incremental Backups Filenames are different and variable??

You would need to record the file name of the last base backup file.

My IFW_Backup batch file suite does this automatically. See
http://bit.ly/2xTuLyw for more information.

>Another Question:
>I've read in program Manual that the Number of Incrementals should not be a lot and it's better to get a Full Backup again after a while.

I personally keep up to 30 incremental backups before taking another
full backup. Other than the possibility of backup files becoming
unreadable, there is no technical reason why you can't have a long
chain of incrementals. (If your backup medium is unreliable then ANY
backup files may potentially become corrupt.)

>Considering the time taken for Full Backup , It's ok to intervally delete only Incrementals and keep first Full Backup and create Incrementals based on first Full Backup again??

This is called a differential backup.

However, if you delete the older differential backups when you create
a new one, you loose the ability to recover files that may have been
inadvertently deleted or corrupted in the meantime. (The time machine
effect.)

>and
>It's not clear for me that which file should be selected to restore to recenet state: Last Incremental Backup File or Full Backup??

You would select the latest incremental backup to restore your system
to what it was on that date. Each backup file contains a link back to
the base used when it was created,so the chain of incrementals is
followed right back to the Full backup, when restoring.

use the option to save it. Cover in the manual, search "savename"


"Backupper" wrote in message news:[email protected]...

OK Thank.
So in case of creating Batch File for Incremental Backup, How to determine
last Backup as Base ? Because the Incremental Backups Filenames are
different and variable??
Another Question:
I've read in program Manual that the Number of Incrementals should not be a
lot and it's better to get a Full Backup again after a while.Considering the
time taken for Full Backup , It's ok to intervally delete only Incrementals
and keep first Full Backup and create Incrementals based on first Full
Backup again??
and
It's not clear for me that which file should be selected to restore to
recenet state: Last Incremental Backup File or Full Backup??

Well,I solved the problem via a program written by vb to find last modified file and set it as Base automatically.
But my new problem is:
The first Backup based on a Full Backup takes long time to complete(I know it's Differential).For example for a 900 Gb volume it takes about 3 hours to complete (with Validating).
I don't know next Incremental backups (based on Last backup) will take same time or not??If I want to do it daily, it's awful.Is that normal or there is something I should do to make it faster??

On Thu, 11 Oct 2018 16:49:59 EDT, Backupper wrote:

>Well,I solved the problem via a program written by vb to find last modified file and set it as Base automatically.
>But my new problem is:
>The first Backup based on a Full Backup takes long time to complete(I know it's Differential).For example for a 900 Gb volume it takes about 3 hours to complete (with Validating).
>I don't know next Incremental backups (based on Last backup) will take same time or not??If I want to do it daily, it's awful.Is that normal or there is something I should do to make it faster??
>
Make sure you are using the /hash parameter on all your backups (Full
and Incrementals). This is the equivalent of the 'Create Sector Hash
Files' option in the graphical user interface.

This causes the imaging program to create 2 additional relatively
short files in addition to the image file(s), and enables subsequent
incremental backups to be much faster. (See the manual for more
details.)