TeraByte Unlimited

Existing Backup Structure: note: (I) file names are incremental file backups

2015-06-01 02:33 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.1
2015-06-01 02:37 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.2
2015-06-01 02:41 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.3
2015-06-01 02:44 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.4
2015-06-01 02:47 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.5
2015-06-01 02:50 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.6
2015-06-01 02:51 AM 749,490,176 2015-06-01-0223-Win7(SSD32)-.7
2015-06-01 02:51 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.TBI
2015-06-02 12:15 AM 438,580,752 2015-06-02-0007-Win7(SSD32)-(I)-.#0
2015-06-02 12:15 AM 306,262,016 2015-06-02-0007-Win7(SSD32)-(I)-.TBI
2015-06-03 12:16 AM 439,119,064 2015-06-03-0009-Win7(SSD32)-(I)-.#0
2015-06-03 12:16 AM 396,955,648 2015-06-03-0009-Win7(SSD32)-(I)-.TBI
2015-06-04 12:20 AM 438,302,240 2015-06-04-0016-Win7(SSD32)-(I)-.#0
2015-06-04 12:20 AM 1,478,914,048 2015-06-04-0016-Win7(SSD32)-(I)-.TBI
2015-06-05 12:10 AM 444,990,640 2015-06-05-0004-Win7(SSD32)-(I)-.#0
2015-06-05 12:10 AM 534,622,208 2015-06-05-0004-Win7(SSD32)-(I)-.TBI
2015-06-06 01:49 AM 447,261,872 2015-06-06-0145-Win7(SSD32)-(I)-.#0
2015-06-06 01:49 AM 331,292,672 2015-06-06-0145-Win7(SSD32)-(I)-.TBI
2015-06-07 12:15 AM 423,336,016 2015-06-07-0007-Win7(SSD32)-(I)-.#0
2015-06-07 12:15 AM 145,457,152 2015-06-07-0007-Win7(SSD32)-(I)-.TBI
2015-06-08 04:33 PM 432,422,280 2015-06-08-1628-Win7(SSD32)-(I)-.#0
2015-06-08 04:33 PM 533,626,880 2015-06-08-1628-Win7(SSD32)-(I)-.TBI
2015-06-09 12:15 AM 432,663,528 2015-06-09-0010-Win7(SSD32)-(I)-.#0
2015-06-09 12:15 AM 187,547,648 2015-06-09-0010-Win7(SSD32)-(I)-.TBI
2015-06-12 12:09 AM 442,882,968 2015-06-12-0004-Win7(SSD32)-(I)-.#0
2015-06-12 12:09 AM 1,236,652,032 2015-06-12-0004-Win7(SSD32)-(I)-.TBI
2015-06-13 01:31 AM 444,703,368 2015-06-13-0127-Win7(SSD32)-(I)-.#0
2015-06-13 01:31 AM 317,087,744 2015-06-13-0127-Win7(SSD32)-(I)-.TBI
2015-06-14 12:33 AM 426,553,992 2015-06-14-0021-Win7(SSD32)-(I)-.#0
2015-06-14 12:33 AM 216,981,504 2015-06-14-0021-Win7(SSD32)-(I)-.TBI
2015-06-15 12:14 AM 428,184,656 2015-06-15-0009-Win7(SSD32)-(I)-.#0
2015-06-15 12:14 AM 218,767,360 2015-06-15-0009-Win7(SSD32)-(I)-.TBI
2015-06-16 12:13 AM 430,358,408 2015-06-16-0008-Win7(SSD32)-(I)-.#0
2015-06-16 12:13 AM 273,776,640 2015-06-16-0008-Win7(SSD32)-(I)-.TBI
2015-06-17 12:26 AM 433,239,016 2015-06-17-0022-Win7(SSD32)-(I)-.#0
2015-06-17 12:26 AM 297,259,008 2015-06-17-0022-Win7(SSD32)-(I)-.TBI
2015-06-18 12:16 AM 440,101,144 2015-06-18-0010-Win7(SSD32)-(I)-.#0
2015-06-18 12:16 AM 594,563,072 2015-06-18-0010-Win7(SSD32)-(I)-.TBI
2015-06-20 01:41 AM 426,252,208 2015-06-20-0137-Win7(SSD32)-(I)-.#0
2015-06-20 01:41 AM 303,636,480 2015-06-20-0137-Win7(SSD32)-(I)-.TBI
2015-06-20 01:58 AM 426,252,328 2015-06-20-0155-Win7(SSD32)-(I)-.#0
2015-06-20 01:58 AM 1,978,368 2015-06-20-0155-Win7(SSD32)-(I)-.TBI
2015-06-21 12:16 AM 429,615,088 2015-06-21-0011-Win7(SSD32)-(I)-.#0
2015-06-21 12:16 AM 280,317,952 2015-06-21-0011-Win7(SSD32)-(I)-.TBI
2015-06-22 12:13 AM 433,582,912 2015-06-22-0009-Win7(SSD32)-(I)-.#0
2015-06-22 12:13 AM 316,411,904 2015-06-22-0009-Win7(SSD32)-(I)-.TBI
2015-06-22 01:37 AM 433,596,696 2015-06-22-0133-Win7(SSD32)-(I)-.#0
2015-06-22 01:37 AM 87,609,344 2015-06-22-0133-Win7(SSD32)-(I)-.TBI
2015-06-23 12:16 AM 433,530,792 2015-06-23-0009-Win7(SSD32)-(I)-.#0
2015-06-23 12:16 AM 204,492,800 2015-06-23-0009-Win7(SSD32)-(I)-.TBI
2015-06-24 12:23 AM 435,286,056 2015-06-24-0017-Win7(SSD32)-(I)-.#0
2015-06-24 12:23 AM 247,013,376 2015-06-24-0017-Win7(SSD32)-(I)-.TBI
2015-06-25 12:23 AM 429,310,472 2015-06-25-0018-Win7(SSD32)-(I)-.#0
2015-06-25 12:23 AM 467,898,368 2015-06-25-0018-Win7(SSD32)-(I)-.TBI

Under windows or winre environment:
Restoring or validating from the (last) 2015-06-25 12:23 AM 467,898,368 2015-06-25-0018-Win7(SSD32)-(I)-.TBI entry WORKS FINE.

Under BIBM/Image or DOS/Image for dos:
Restoring or validating from the (last) 2015-06-25 12:23 AM 467,898,368 2015-06-25-0018-Win7(SSD32)-(I)-.TBI entry
immediately asks for the NEXT BACKUP FILE to be selected. Selecting any file generates a "the file is locked" error. There is no way to continue.

Restoring from the 2015-06-22 01:37 AM 87,609,344 2015-06-22-0133-Win7(SSD32)-(I)-.TBI entry works with no problem.
Any file after this date will ask for the next file to be selected.

QUESTION: Have I reached an internal limit to the number of files that can be in an incremental chain? Again, there is no problem running under Windows.

The OS would have an open file handle limit. also, each file is going to
take a few MB of ram each. You should start combing after a while or create
a new full.


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

Existing Backup Structure: note: (I) file names are incremental file
backups

2015-06-01 02:33 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.1
2015-06-01 02:37 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.2
2015-06-01 02:41 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.3
2015-06-01 02:44 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.4
2015-06-01 02:47 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.5
2015-06-01 02:50 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.6
2015-06-01 02:51 AM 749,490,176 2015-06-01-0223-Win7(SSD32)-.7
2015-06-01 02:51 AM 4,294,963,200 2015-06-01-0223-Win7(SSD32)-.TBI
2015-06-02 12:15 AM 438,580,752 2015-06-02-0007-Win7(SSD32)-(I)-.#0
2015-06-02 12:15 AM 306,262,016 2015-06-02-0007-Win7(SSD32)-(I)-.TBI
2015-06-03 12:16 AM 439,119,064 2015-06-03-0009-Win7(SSD32)-(I)-.#0
2015-06-03 12:16 AM 396,955,648 2015-06-03-0009-Win7(SSD32)-(I)-.TBI
2015-06-04 12:20 AM 438,302,240 2015-06-04-0016-Win7(SSD32)-(I)-.#0
2015-06-04 12:20 AM 1,478,914,048 2015-06-04-0016-Win7(SSD32)-(I)-.TBI
2015-06-05 12:10 AM 444,990,640 2015-06-05-0004-Win7(SSD32)-(I)-.#0
2015-06-05 12:10 AM 534,622,208 2015-06-05-0004-Win7(SSD32)-(I)-.TBI
2015-06-06 01:49 AM 447,261,872 2015-06-06-0145-Win7(SSD32)-(I)-.#0
2015-06-06 01:49 AM 331,292,672 2015-06-06-0145-Win7(SSD32)-(I)-.TBI
2015-06-07 12:15 AM 423,336,016 2015-06-07-0007-Win7(SSD32)-(I)-.#0
2015-06-07 12:15 AM 145,457,152 2015-06-07-0007-Win7(SSD32)-(I)-.TBI
2015-06-08 04:33 PM 432,422,280 2015-06-08-1628-Win7(SSD32)-(I)-.#0
2015-06-08 04:33 PM 533,626,880 2015-06-08-1628-Win7(SSD32)-(I)-.TBI
2015-06-09 12:15 AM 432,663,528 2015-06-09-0010-Win7(SSD32)-(I)-.#0
2015-06-09 12:15 AM 187,547,648 2015-06-09-0010-Win7(SSD32)-(I)-.TBI
2015-06-12 12:09 AM 442,882,968 2015-06-12-0004-Win7(SSD32)-(I)-.#0
2015-06-12 12:09 AM 1,236,652,032 2015-06-12-0004-Win7(SSD32)-(I)-.TBI
2015-06-13 01:31 AM 444,703,368 2015-06-13-0127-Win7(SSD32)-(I)-.#0
2015-06-13 01:31 AM 317,087,744 2015-06-13-0127-Win7(SSD32)-(I)-.TBI
2015-06-14 12:33 AM 426,553,992 2015-06-14-0021-Win7(SSD32)-(I)-.#0
2015-06-14 12:33 AM 216,981,504 2015-06-14-0021-Win7(SSD32)-(I)-.TBI
2015-06-15 12:14 AM 428,184,656 2015-06-15-0009-Win7(SSD32)-(I)-.#0
2015-06-15 12:14 AM 218,767,360 2015-06-15-0009-Win7(SSD32)-(I)-.TBI
2015-06-16 12:13 AM 430,358,408 2015-06-16-0008-Win7(SSD32)-(I)-.#0
2015-06-16 12:13 AM 273,776,640 2015-06-16-0008-Win7(SSD32)-(I)-.TBI
2015-06-17 12:26 AM 433,239,016 2015-06-17-0022-Win7(SSD32)-(I)-.#0
2015-06-17 12:26 AM 297,259,008 2015-06-17-0022-Win7(SSD32)-(I)-.TBI
2015-06-18 12:16 AM 440,101,144 2015-06-18-0010-Win7(SSD32)-(I)-.#0
2015-06-18 12:16 AM 594,563,072 2015-06-18-0010-Win7(SSD32)-(I)-.TBI
2015-06-20 01:41 AM 426,252,208 2015-06-20-0137-Win7(SSD32)-(I)-.#0
2015-06-20 01:41 AM 303,636,480 2015-06-20-0137-Win7(SSD32)-(I)-.TBI
2015-06-20 01:58 AM 426,252,328 2015-06-20-0155-Win7(SSD32)-(I)-.#0
2015-06-20 01:58 AM 1,978,368 2015-06-20-0155-Win7(SSD32)-(I)-.TBI
2015-06-21 12:16 AM 429,615,088 2015-06-21-0011-Win7(SSD32)-(I)-.#0
2015-06-21 12:16 AM 280,317,952 2015-06-21-0011-Win7(SSD32)-(I)-.TBI
2015-06-22 12:13 AM 433,582,912 2015-06-22-0009-Win7(SSD32)-(I)-.#0
2015-06-22 12:13 AM 316,411,904 2015-06-22-0009-Win7(SSD32)-(I)-.TBI
2015-06-22 01:37 AM 433,596,696 2015-06-22-0133-Win7(SSD32)-(I)-.#0
2015-06-22 01:37 AM 87,609,344 2015-06-22-0133-Win7(SSD32)-(I)-.TBI
2015-06-23 12:16 AM 433,530,792 2015-06-23-0009-Win7(SSD32)-(I)-.#0
2015-06-23 12:16 AM 204,492,800 2015-06-23-0009-Win7(SSD32)-(I)-.TBI
2015-06-24 12:23 AM 435,286,056 2015-06-24-0017-Win7(SSD32)-(I)-.#0
2015-06-24 12:23 AM 247,013,376 2015-06-24-0017-Win7(SSD32)-(I)-.TBI
2015-06-25 12:23 AM 429,310,472 2015-06-25-0018-Win7(SSD32)-(I)-.#0
2015-06-25 12:23 AM 467,898,368 2015-06-25-0018-Win7(SSD32)-(I)-.TBI

Under windows or winre environment:
Restoring or validating from the (last) 2015-06-25 12:23 AM
467,898,368 2015-06-25-0018-Win7(SSD32)-(I)-.TBI entry WORKS FINE.

Under BIBM/Image or DOS/Image for dos:
Restoring or validating from the (last) 2015-06-25 12:23 AM
467,898,368 2015-06-25-0018-Win7(SSD32)-(I)-.TBI entry
immediately asks for the NEXT BACKUP FILE to be selected. Selecting any
file generates a "the file is locked" error. There is no way to continue.

Restoring from the 2015-06-22 01:37 AM 87,609,344
2015-06-22-0133-Win7(SSD32)-(I)-.TBI entry works with no problem.
Any file after this date will ask for the next file to be selected.

QUESTION: Have I reached an internal limit to the number of files that can
be in an incremental chain? Again, there is no problem running under
Windows.

It appears from the data "tas3086" has posted, there is a limit in IFD of a
maximum of 20 incremental files for restore.

What are the limits for IFW and IFL?


"TeraByte Support" wrote:
> The OS would have an open file handle limit. also, each file is going to
> take a few MB of ram each. You should start combing after a while or create
> a new full.
>
>
> "tas3086" wrote in message news:[email protected]...
> Snip

Under PC/MS DOS it's controlled file files=, in TBOS it's fixed.

Under linux you can use ulimit -n to see or set

Under Windows there is no real limit. The default if C library was used is
512, but it doesn't use that so that limit doesn't apply. Would be a lot,
here's a sample of number of handles that were allowed to be opened:
http://blogs.technet.com/b/markrussinovich/archive/2009/09/29/3283844.aspx

"Tom Cole" wrote in message news:[email protected]...

It appears from the data "tas3086" has posted, there is a limit in IFD of a
maximum of 20 incremental files for restore.

What are the limits for IFW and IFL?


"TeraByte Support"

wrote:
> The OS would have an open file handle limit. also, each file is going to
> take a few MB of ram each. You should start combing after a while or
> create
> a new full.
>
>
> "tas3086" wrote in message news:[email protected]...
> Snip

I've increased (MS) PC/DOS FILES, BUFFERS, FCBS, and STACKS to their maximum limit in Config.sys, and they had no effect on the ability to process the chain.

Terabyte: For other users in the future, Is there any chance that you can create an error message that more descriptively states the error in image.exe? Can this be detected at backup time as a restore warning of some kind? i.e. "will restore under windows ONLY"

I will try IFL to see if I can use it, but am happy that TBWINRE works without error. I'd like another alternative available though, just in case I reach some other unknown/undefined limit !

**UPDATE NOTE: I did try IFL and used ulimit to increase openfiles to 2048. It had no effect, was not able to read the chain.
Anyone have some other suggestions for PC/DOS or Linux?

wrote:
> Anyone have some other suggestions for PC/DOS or Linux?

Does specifying 'multiple passes' enable you to restore with more than 20
incrementals?
(You'll need to select 'manual restore'.)

For DOS FILE= to work, you have to use "file (os)"

For Linux (the default is 1024 files) so you again would need to use "file
(os)".

I think I know what you're running in to when using "Files (direct)". That
can be increased.


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

I've increased (MS) PC/DOS FILES, BUFFERS, FCBS, and STACKS to their maximum
limit in Config.sys, and they had no effect on the ability to process the
chain.

Terabyte: For other users in the future, Is there any chance that you can
create an error message that more descriptively states the error in
image.exe? Can this be detected at backup time as a restore warning of some
kind? i.e. "will restore under windows ONLY"

I will try IFL to see if I can use it, but am happy that TBWINRE works
without error. I'd like another alternative available though, just in case
I reach some other unknown/undefined limit !

**UPDATE NOTE: I did try IFL and used ulimit to increase openfiles to 2048.
It had no effect, was not able to read the chain.
Anyone have some other suggestions for PC/DOS or
Linux?

Yeah, for File (direct) it was using the debug value of 20 instead of 200,
but changed to 512 for the next update.


"TeraByte Support" wrote in message news:[email protected]...

For DOS FILE= to work, you have to use "file (os)"

For Linux (the default is 1024 files) so you again would need to use "file
(os)".

I think I know what you're running in to when using "Files (direct)". That
can be increased.


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

I've increased (MS) PC/DOS FILES, BUFFERS, FCBS, and STACKS to their maximum
limit in Config.sys, and they had no effect on the ability to process the
chain.

Terabyte: For other users in the future, Is there any chance that you can
create an error message that more descriptively states the error in
image.exe? Can this be detected at backup time as a restore warning of some
kind? i.e. "will restore under windows ONLY"

I will try IFL to see if I can use it, but am happy that TBWINRE works
without error. I'd like another alternative available though, just in case
I reach some other unknown/undefined limit !

**UPDATE NOTE: I did try IFL and used ulimit to increase openfiles to 2048.
It had no effect, was not able to read the chain.
Anyone have some other suggestions for PC/DOS or
Linux?

Your fix will be great. I will be patiently waiting until its release. Will it help the TBOS and DOS implementations?

DOS File (os) will not work for me as all of my disks are not FAT. (I have a pen drive that boots dos and has a full IFD system installed on it.) So I require FILES DIRECT method.

Thank you for quickly finding a hopefully helpful solution.

SUBNOTE: Your product is one of the best and most thorough product set that I have ever used. It is better than Acronis, Norton Ghost, and other brand names, yet you do not seem to get the recognition that your product deserves. Is there anything that we can do to get your name in lights?

(Although, the last product that was fantastic: Powerquest Drive Image, was bought by Norton, solely I think, to put them out of business. So maybe it is best that we keep you a secret !!!)