<filename>.#_# and <filename>.#0

User discussion and information resource forum for Image products.

<filename>.#_# and <filename>.#0

Postby bbearren » Mon Jul 02, 2018 6:36 am

I have IFW setup in Task Scheduler to create images for 3 partitions on a weekly basis. For the last few weeks, for each partition, there is a small file with the specified name with a suffix of .#_# and a much larger file, same name, with the suffix .#0, and the .TBI file that I always expect, of the size I typically get.

What is it with those other two files? Are they needed for any reason? IFW is run by Task Scheduler at 3:00AM, so there is no user activity on the drives/partitions, and no user logged in.

This is a sample script:
"U:\Program Files\TeraByte Drive Image\imagew64.exe" /wait /b /d:w1@0x1 /priority:4 /md /f:"K:\DH87RL10A\$~YYYY$-$~MM$-$~DD$\Win10ProA\$~MM$-$~DD$-$~YYYY$-Win10ProA" /vb

The only variation between the scripts are the partition and the filename.
bbearren
 
Posts: 28
Joined: Sun Jun 17, 2012 7:02 am

Re: <filename>.#_# and <filename>.#0

Postby TeraByte Support » Mon Jul 02, 2018 9:29 am

version 3.18 enables hash files by default add /hash:0 if you don't want
them up update. If you do changes only backup, the hash files will speed up
the operation.


"bbearren" wrote in message news:15186@public.image...

I have IFW setup in Task Scheduler to create images for 3 partitions on a
weekly basis. For the last few weeks, for each partition, there is a small
file with the specified name with a suffix of .#_# and a much larger file,
same name, with the suffix .#0, and the .TBI file that I always expect, of
the size I typically get.

What is it with those other two files? Are they needed for any reason? IFW
is run by Task Scheduler at 3:00AM, so there is no user activity on the
drives/partitions, and no user logged in.

This is a sample script:
"U:\Program Files\TeraByte Drive Image\imagew64.exe" /wait /b /d:w1@0x1
/priority:4 /md
/f:"K:\DH87RL10A\$~YYYY$-$~MM$-$~DD$\Win10ProA\$~MM$-$~DD$-$~YYYY$-Win10ProA"
/vb

The only variation between the scripts are the partition and the filename.

TeraByte Support
 
Posts: 2562
Joined: Thu May 05, 2011 3:37 pm

Re: <filename>.#_# and <filename>.#0

Postby TeraByte Support » Mon Jul 02, 2018 9:30 am

I should also add that using the hash file, you can remove the .tbi file and
still do changes only backup. So if you wanted to move it off to the could,
you could. However, restoring, all the required files are needed. Also,
you'd still want to combine at times (say on the remote server the files are
on).



"TeraByte Support" wrote in message news:15191@public.image...

version 3.18 enables hash files by default add /hash:0 if you don't want
them up update. If you do changes only backup, the hash files will speed up
the operation.

TeraByte Support
 
Posts: 2562
Joined: Thu May 05, 2011 3:37 pm

Re: <filename>.#_# and <filename>.#0

Postby bbearren » Mon Jul 02, 2018 10:38 am

Thanks for the explanation. I don't do changes only backups, I have a Task Scheduler task that uses Robocopy to copy my data files daily to a separate hard drive in my PC, to my DIY NAS PC, and OneDrive also gets involved with a copy in the cloud.

I have edited my scripts and tested them, and it's all good now. Thanks again.
bbearren
 
Posts: 28
Joined: Sun Jun 17, 2012 7:02 am

Re: <filename>.#_# and <filename>.#0

Postby Bob Coleman » Mon Jul 02, 2018 5:37 pm

bbearren wrote:
> Thanks for the explanation. I don't do changes only backups, I have a Task
> Scheduler task that uses Robocopy to copy my data files daily to a separate
> hard drive in my PC, to my DIY NAS PC, and OneDrive also gets involved with
> a copy in the cloud.
>
> I have edited my scripts and tested them, and it's all good now. Thanks
> again.

Probably no need to change anything, but note that as of version 3.19 the default has gone back to not creating the hash files.
Bob Coleman
 
Posts: 504
Joined: Fri Aug 12, 2011 10:58 am


Return to Image for DOS/Linux/Windows