Direkt zum Inhalt

Job Name & File Name

Thread needs solution

I have two backup jobs with the exact same criteria except for the name and scheduled time. One is/was running at 11am and the other at 11pm.

Does the job name dictate what the file name will be? One job is named Susan and creates backup files with the name Susan*.tibx. The other is named Susan_full_b2_s1_v1.tibx and creates similarly named backup files.

If I delete the job named Susan and rename the other one as Susan, will the files going forward be names Susan? Or will it continue with the chain and version number as previous?

Thanks.

0 Users found this helpful

Does the job name dictate what the file name will be? One job is named Susan and creates backup files with the name Susan*.tibx. The other is named Susan_full_b2_s1_v1.tibx and creates similarly named backup files.

Yes.  The name you give to the backup task (job) is the name that will be used for the files being created by that task.

If I delete the job named Susan and rename the other one as Susan, will the files going forward be names Susan? Or will it continue with the chain and version number as previous?

Sorry it doesn't work that way.  ATI 2020 does not allow you to rename an existing backup job at this time - a fix is awaited for this issue.

If you delete the Susan task, then all references to that task are removed.  If you just rename the second Susan_full... task, then you will end up with a mixture of file names - all existing files will have the old name, and any new files created would have the new name.  As such, it is probably better to delete both jobs and then create a new one using the name you want both the job and files to have.

Thank you Steve.

I think what I'll do is delete Susan and its related files and leave Susan_full... as is. It's got the file naming structure that I much prefer. And I don't need two backups a day.

phred wrote:

I think what I'll do is delete Susan and its related files and leave Susan_full... as is. It's got the file naming structure that I much prefer. And I don't need two backups a day.

 I don't know what you are expecting with the name Susan_full_b2_s1_v1.tibx, but you should not expect it to follow the naming conventions of the .tib files. When the next file is created, it should have the name Susan_full_b2_s1_v1-0001.tibx.

BrunoC wrote:

 I don't know what you are expecting with the name Susan_full_b2_s1_v1.tibx, but you should not expect it to follow the naming conventions of the .tib files. When the next file is created, it should have the name Susan_full_b2_s1_v1-0001.tibx.

I would have expected the same as what you suggest, but I'm finding that it does indeed follow the old .tib naming convention. And I don't want to do anything that will change it.

Anhang Größe
515958-173408.jpg 75.64 KB

I can only comment that I cannot reproduce the same effect that you are seeing here Fred.

Out of interest, if you double click on one of your Susan_full_b2 .tibx files in Explorer, what does it show you for the content?

Phred, can you also show us the script file for this job. Did you apply Steve's script patch to create a .tib file but with a .tibx extension? What will happen on the next Full?

Steve Smith wrote:

I can only comment that I cannot reproduce the same effect that you are seeing here Fred.

Out of interest, if you double click on one of your Susan_full_b2 .tibx files in Explorer, what does it show you for the content?

 Here are two screenshots Steve. One is what it looks like when I double-clicked on Susan_full... and the other is when I drilled down and double-clicked on what was shown in the first one. And if I double-clicked on any of the drive letters it shows the files on that drive that have been backed up.

Anhang Größe
515969-173411.jpg 24.79 KB
515969-173414.jpg 42.55 KB
BrunoC wrote:

Phred, can you also show us the script file for this job. Did you apply Steve's script patch to create a .tib file but with a .tibx extension? What will happen on the next Full?

No, I haven't done Steve's tibx to tib modification. There are two script files - this is the one with the latest date, and I'm pretty sure it's for the Susan_full... job.

Anhang Größe
515972-173416.txt 5.83 KB

The script shows that this is a .tib format; it must have been a backup task carried over from the previous version of ATI. So how did the file type get changed to .tibx?

BrunoC wrote:

The script shows that this is a .tib format; it must have been a backup task carried over from the previous version of ATI. So how did the file type get changed to .tibx?

I sure hope that question is rhetorical, Bruno, because I have no idea. All I know is the file naming is that way I had hope it would be. Whether the extension is .tib or .tibx doesn't matter that much to me as long as the backup is valid and I can use it to restore if/when necessary.

In case it helps, I've attached the other script. It looks like this one has the job name of Susan, while the first one I posted had Susan_full_...

I can hardly wait to see what filename gets used with tonight's backup.

Anhang Größe
515979-173418.txt 3.57 KB

Fred, the script .tib.tis contents are from your other task just named Susan and producing the Susan.tibx file output.  If you open these files in Notepad, you will see the task / job name at the top of the file as <display>Susan..... </display>

 

Steve Smith wrote:

Fred, the script .tib.tis contents are from your other task just named Susan and producing the Susan.tibx file output.  If you open these files in Notepad, you will see the task / job name at the top of the file as <display>Susan..... </display>

 

Yes, I saw that too. But Bruno asked for the scripts and I posted them. Yesterday I turned off the job Susan and today the script for the job Susan_full_b2_s1_v1 showed today's file date.  So that's the script that's running the job with the same name. And giving me incremented file names like the old .tib format. Even though the extension is .tibx and Bruno says the script is a .tib format.

At this point I'm quite happy to leave things as they are. Two more backups and a new chain should start. I'll report back with what the filename and extension is at that point.