This can make it rather confusing to figure out which backups belong to which set - which is again why it's a good idea to let Reflect just use randomly generated IDs for backup sets and apply any descriptive naming you want in the name of the parent folder rather than within the file itself. If you run ANOTHER Full and haven't changed that base name, then Reflect will try to use that same pattern again - but since a file already exists at the target with that name, it will append a 1 to that 'base' but BEFORE the 'intra-set' numbering. But if you specify a custom name, the first Full you create will use that name followed by '00-00'. If you keep the default naming scheme of a randomly generated Image ID, then backups that are all part of the same set will have the same base ID, with the only difference being the two number pairs at the end, and each new set will have a completely different randomly generated ID.

The only case where those two digit pairs would be different from each other would be if you enabled file splitting to have a single backup split across multiple smaller files, typically because you wanted to store files either on an optical disc or on a FAT32 partition that didn't support files larger than 4GB. If you were to create a Diff or Inc as a child of that Full, its name would end '01-01', and subsequent backups in the set would be incremented accordingly.

A file ending '00-00' will always be a Full backup. a Full and any child Differential or Incremental backups.

The two pairs of digits at the end increment for backups within a given set, i.e. This is one reason it's a good idea to consider keeping the default setting of allowing Reflect to name backups by Image ID rather than providing a custom name.

Macrium reflect error 9 driver number 1