SBSE____.TIB files

For technical support visit http://support.2brightsparks.com/
jgt
Enthusiastic
Enthusiastic
Posts: 14
Joined: Thu Jun 30, 2005 1:57 am

SBSE____.TIB files

Postby jgt » Sun Dec 03, 2017 8:16 am

I see several SBSE____.TIB files in my SB target folders. Are these SyncBackPro files? If yes why do they have the file extension of TIB. TIB files should be Acronis True Image files. With the 2018 release of True Image these files are creating a True Image issue for me. The only place I see the files are in the target folders for SyncbackPro.

User avatar
michael.kenward
Knowledgeable
Knowledgeable
Posts: 27
Joined: Mon Jun 20, 2005 9:26 am

Re: SBSE____.TIB files

Postby michael.kenward » Sun Dec 03, 2017 11:30 am

TIB files should be Acronis True Image files.


Why? No one has a monopoly on file extensions.

SyncBack usually cleans up after itself and you won't see its housekeeping files.

jgt
Enthusiastic
Enthusiastic
Posts: 14
Joined: Thu Jun 30, 2005 1:57 am

Re: SBSE____.TIB files

Postby jgt » Sun Dec 03, 2017 6:13 pm

I agree that there is no monopoly on file extensions however, it is common practice not to use an extension that another company is using for their application. Possibly we are in a chicken/egg situation here with the tib extension but Acronis True Image has been using the TIB extension since it was released and when I view any of the online databases regarding the TIB extension they all clearly identify them as Acronis True Image files.

When Acronis released the TI 2018 version as a layer of security protection they implemented Active Protection. When Acitve Protection is turned on any attempt to modify/delete/move a TIB file outside of TI this action is blocked. Yes, it is possible to turn off the Active Protection but then you have no protection for the TIB files created by TI.

cliffhanger
Expert
Expert
Posts: 752
Joined: Tue May 31, 2011 5:59 pm

Re: SBSE____.TIB files

Postby cliffhanger » Mon Dec 04, 2017 10:39 am


jgt
Enthusiastic
Enthusiastic
Posts: 14
Joined: Thu Jun 30, 2005 1:57 am

Re: SBSE____.TIB files

Postby jgt » Mon Dec 04, 2017 11:59 pm

cliffhanger, this looks like it will resolve my issue. I just implemented it and when SBP makes the nightly runs as well as TI I will know. I might have to wait a couple of days to ensure I created the file correctly. This is a very simple file but I have been known to make a mistake. :oops:
I'll follow-up with my results.

jgt
Enthusiastic
Enthusiastic
Posts: 14
Joined: Thu Jun 30, 2005 1:57 am

Re: SBSE____.TIB files

Postby jgt » Wed Dec 06, 2017 5:25 am

cliffhanger, either I did something wrong or the procedure identified at http://support.2brightsparks.com/knowle ... 1512288406 no longer works.

After I implemented I checked and ensured that there were no SBSE____.TIB files on my PC. I used the search tool Everything to search my system. I just checked my system and I see one SBSE____.TIB file that was created at 2353 hours on 1205, it is currently 0025 hours 1206 thus the file was created less than 30 minutes ago.

cliffhanger
Expert
Expert
Posts: 752
Joined: Tue May 31, 2011 5:59 pm

Re: SBSE____.TIB files

Postby cliffhanger » Wed Dec 06, 2017 10:51 am

Hi, did you restart SBPro after adding the blockext.txt file? (Yes, i know it doesn't mention that in the KB, but it might be necessary to ensure the file is parsed/loaded on program startup). Having said that, if the nightly run is Scheduled, it should not make any difference because Scheduled runs open/use/close a separate instance of SB to run Scheduled profiles anyway (so the separate instance should have loaded blockext.txt as it fires up anyway). Note that this does not apply to Periodical backups, which would need Pro closed/re-opened once to make sure the blocker file loads as Pro starts up. If in doubt, simply reboot/re-test, which means any instance of Pro that runs after the reboot should have loaded the blocker file (assuming it is located where Pro expects to find one, if any)

If blockext.txt should have been loaded by the time the profile/s are run by whichever SBPro instance does so, I guess either the file is misconfigured/mis-located or the process itself is faulty. Unfortunately you cannot attach *.txt files here for checking (against forum rules, I guess) but you could Zip it and attach the Zip? Unfortunately by its very nature it would be hard to test if the exclusion is working because AFAIK there is no way of ensuring/forcing the 'random' part of the temp-file naming process (i.e. which random extension it decides to try and use in the first place) to 'propose' a .TIB extension to be trapped/denied (or, not). AFAICS, the only way is to record the workings of the run/s and capture them if any such files are spotted. So...

I would suggest you set Output Debug Info (see article following) and keep checking for SBSE____.TIB files immediately after each run (or, first thing next morning, provided the same profiles will not run again in the meantime). If you find any more SBSE____.TIB files, generate a Support Zip(s) immediately for the profile (or profiles) you suspect of creating the SBSE.TIB files and forward it/them to 2BS Support (details in article) and also forward (i.e. attach) a copy of your blockext.txt file and an Explorer screenshot of which folder it is installed in. Suggest you also include a reference or link to this forum topic for continuity. If 2BS need anything else I'm sure they will get back to you (on the ticket)

Note well the warning in the KB article about running the same profile(s) again before you generate Support Zip(s) - if you do, you will wipe/replace the debug info of the run you are trying to capture (with info about the new run), and your next run may not pick the same extensions again

Do not post Support Zips or copy profiles on this open forum!

In conclusion, I must add that a process that generates a random extension .??? and tests it against an internal list of do-not-use strings (making sure things like SBSE____.EXE, SBSE___.BAT etc. do not happen) and optionally against a user defined list (blockext.txt) seems to have an unusual predilection for choosing .TIB in the first place (given the tens of thousands of other filename-legal random combinations it could decide on). I cannot help getting the feeling there is something else going on...


Return to “SyncBackPro (commercial)”



Who is online

Users browsing this forum: No registered users and 8 guests