The first run of a Fast Backup is a Full run (same as Rescan). As you have some errors, I suggest delete the backup copies you have now, makes the changes, click Force Rescan on Fast Backup page (to reset it to run-1 state), then start again.
Individual aspects are
0) as per the example in the Help, change the different folder for Full (first/rescan) backups to
h:\datafolder\1\
(or, h:\datafolder\FULL\ if you prefer). At the moment you are pointing it to a level higher than your 'fast' (incremental) folders, so that the latter would be 'nested' inside the 'full' location. This means a Restore from the 'full' location would also include all the incremental changes as well! They must be segregated. You can use a different location altogether (even a different drive) but you should never 'nest' them. (Another aspect is that if you changed to a Mirror - see point-4 - then on a 'full' run, the profile would delete all those 'incremental' folders, because they don't exist on the Source. This would mean after each Full run, you would have no recent Incrementals left - for example, 'no yesterday')
1) Which folder? Full or incrementals? The rule of thumb is that if you specify a separate path for Full backups, it should be a static path (no Variable - as above). The other (main) Destination string (for 'incremental' days) should have the Variable.
2) I can't follow your description 100% (for example, which is the "different" folder? Do you mean the 'full' location?). If so and this was the first run, then see above - this is normal (if we didn't back up everything to start with, you won't have a copy of any files that don't subsequently change). But because you have it currently set to permit 'nested' backups, you need to start again. The files it has copied so far are almost certainly in the wrong place at the moment.
3) Then change it![:)]( "Smile")
Its best to start actually running the profile on the day you want full backups (Rescans) to happen in future (it helps to visualize what is happening as it progresses). You might want to take advantage of the possibility to set your full/rescan folder to ....\full\, so it uses that one whatever day you start. Or, set it to ....\5\ if you want to start on Fridays (and do so). Don't forget to change the Force Rescan When setting to match
4) You can simply change that Fast Backup to a Mirror profile via Decisions-Files settings page. Remember that the 'incremental' folders are going to get flushed anyway (c/o the setting on Fast Backup page to that effect) so you only need worry about deleting files in the 'full' folder.
Note that the Type in main UI will still show Fast Backup (not Mirror). You need to set Decisions-Files to what you want, and remember that (or, add a note to the Name of the profile to remind you, e.g. "Name Of Profile (Mirror)"
5) yes
6) normally this might be an issue (if just using Versioning alone) - if a file changes every day, you will get max last-4 Versions of it. But because Versioning will only happen in the 'full' folder (bear in mind the 'incremental' folders are flushed before scanning, so there will never be old copies of files there to Version), this will work to your advantage, in that it will keep several Versions of the file as it was on each Friday (assuming it changes: if a file doesn't change at all during the cycle, there will be no Versions at all either - but neither will you need any. If it only changes twice, there will only be two Versions - and so on)
7) yes (subject to you starting the cycle on Friday). That 'full' location will be addressed (thus, Versions 'housekept') every 1/8/15/22 (and so on) days, but remember the Version age-limit is independent of any calendar-based day numbers, so it's up to you to set things up so the two actually coincide
8 ) Not possible/supported.
Remember that the Versions will only be of files that changed (where that change was 'captured'). A file that is unchanged throughout the 4-week cycle will not be Versioned at all, and the only copy you will have will be the single copy (checked once a week but not refreshed, because no need) in the 'full' folder. But as it is unchanged, one copy (of that unchanged state) is all you need. No point having four copies of the same state of the same file...
Don't forget to Force Rescan (or, start from scratch & make a new profile altogether). At the moment that profile is in mid-cycle state based on the original playing field, but you're planning to move the goalposts...
Individual aspects are
0) as per the example in the Help, change the different folder for Full (first/rescan) backups to
h:\datafolder\1\
(or, h:\datafolder\FULL\ if you prefer). At the moment you are pointing it to a level higher than your 'fast' (incremental) folders, so that the latter would be 'nested' inside the 'full' location. This means a Restore from the 'full' location would also include all the incremental changes as well! They must be segregated. You can use a different location altogether (even a different drive) but you should never 'nest' them. (Another aspect is that if you changed to a Mirror - see point-4 - then on a 'full' run, the profile would delete all those 'incremental' folders, because they don't exist on the Source. This would mean after each Full run, you would have no recent Incrementals left - for example, 'no yesterday')
1) Which folder? Full or incrementals? The rule of thumb is that if you specify a separate path for Full backups, it should be a static path (no Variable - as above). The other (main) Destination string (for 'incremental' days) should have the Variable.
2) I can't follow your description 100% (for example, which is the "different" folder? Do you mean the 'full' location?). If so and this was the first run, then see above - this is normal (if we didn't back up everything to start with, you won't have a copy of any files that don't subsequently change). But because you have it currently set to permit 'nested' backups, you need to start again. The files it has copied so far are almost certainly in the wrong place at the moment.
3) Then change it
Its best to start actually running the profile on the day you want full backups (Rescans) to happen in future (it helps to visualize what is happening as it progresses). You might want to take advantage of the possibility to set your full/rescan folder to ....\full\, so it uses that one whatever day you start. Or, set it to ....\5\ if you want to start on Fridays (and do so). Don't forget to change the Force Rescan When setting to match4) You can simply change that Fast Backup to a Mirror profile via Decisions-Files settings page. Remember that the 'incremental' folders are going to get flushed anyway (c/o the setting on Fast Backup page to that effect) so you only need worry about deleting files in the 'full' folder.
Note that the Type in main UI will still show Fast Backup (not Mirror). You need to set Decisions-Files to what you want, and remember that (or, add a note to the Name of the profile to remind you, e.g. "Name Of Profile (Mirror)"
5) yes
6) normally this might be an issue (if just using Versioning alone) - if a file changes every day, you will get max last-4 Versions of it. But because Versioning will only happen in the 'full' folder (bear in mind the 'incremental' folders are flushed before scanning, so there will never be old copies of files there to Version), this will work to your advantage, in that it will keep several Versions of the file as it was on each Friday (assuming it changes: if a file doesn't change at all during the cycle, there will be no Versions at all either - but neither will you need any. If it only changes twice, there will only be two Versions - and so on)
7) yes (subject to you starting the cycle on Friday). That 'full' location will be addressed (thus, Versions 'housekept') every 1/8/15/22 (and so on) days, but remember the Version age-limit is independent of any calendar-based day numbers, so it's up to you to set things up so the two actually coincide
8 ) Not possible/supported.
Remember that the Versions will only be of files that changed (where that change was 'captured'). A file that is unchanged throughout the 4-week cycle will not be Versioned at all, and the only copy you will have will be the single copy (checked once a week but not refreshed, because no need) in the 'full' folder. But as it is unchanged, one copy (of that unchanged state) is all you need. No point having four copies of the same state of the same file...
Don't forget to Force Rescan (or, start from scratch & make a new profile altogether). At the moment that profile is in mid-cycle state based on the original playing field, but you're planning to move the goalposts...