Oh, OK, got it. So, it is a "Safe Copy" artifact.
BTW, imagine that I have a "Mirror Right" profile without versioning, which left an 'SBSE__.*' file on the Destination side during the previous run (due to some intermittent glitch). Next time the same profile runs, it will discover that abandoned 'SBSE__.*' file on the Destination side. The file does not exist on the Source side, which means that it has to be deleted in accordance with "Mirror Right" decision set. I assume that SB will indeed delete that file, meaning that "Mirror Right" profiles have the self-cleaning properties with regard to leftover temporary files. Is my understanding correct?
Now, what will happen if a "Mirror Right" profile with versioning encounters an abandoned 'SBSE__.*' file on the Destination side? I assume that SB will move the orphaned 'SBSE__.*' file to '$SBV$' folder, meaning that the file will actually persist for much longer period of time (i.e. until the versioning time limit expires). Is this correct?
Both of the above assumes that SB treats orphaned 'SBSE__.*' files on Destination side as ordinary files. Or, perhaps, SB will recognize 'SBSE__.*' files as its own and treat them differently?
BTW, imagine that I have a "Mirror Right" profile without versioning, which left an 'SBSE__.*' file on the Destination side during the previous run (due to some intermittent glitch). Next time the same profile runs, it will discover that abandoned 'SBSE__.*' file on the Destination side. The file does not exist on the Source side, which means that it has to be deleted in accordance with "Mirror Right" decision set. I assume that SB will indeed delete that file, meaning that "Mirror Right" profiles have the self-cleaning properties with regard to leftover temporary files. Is my understanding correct?
Now, what will happen if a "Mirror Right" profile with versioning encounters an abandoned 'SBSE__.*' file on the Destination side? I assume that SB will move the orphaned 'SBSE__.*' file to '$SBV$' folder, meaning that the file will actually persist for much longer period of time (i.e. until the versioning time limit expires). Is this correct?
Both of the above assumes that SB treats orphaned 'SBSE__.*' files on Destination side as ordinary files. Or, perhaps, SB will recognize 'SBSE__.*' files as its own and treat them differently?