Using the old Cobian still - but I just discovered the new kid on the block is Reflector.
I don’t think you could do this in the original version 11, but I want to filter all content in a particular named folder, but there are multiple subfolders that this should apply to on different paths. It needs to be inclusion and exclusion based. My "Use Case" is for Unreal development. And now we are at UE5 and there is of course version control solutions such as Perforce, but they are only really useful for Games Development houses, for many the cost is prohibitive.
So back to the backup scenario, we might have
c:\unrealproject\Content\Megascans\*.*
c:\new_unrealproject\Content\Megascans\*.*
c:\previous_version_unrealproject\Content\Megascans\*.*
With this example Megascans folders can be huge, and full of redundant files, that is a master copy exists elsewhere on the disk.
I would preferably have one incremental backup job for the master directory
and any jobs with projects in the target directory (..\Documents\projects for instance) would have the Megascans subfolders excluded.
Unreal Dev is not the only time, I have had this type of "use case" come up many times over the years and constantly toyed with making my own backup solution. But I don’t have the time to reinvent the wheel. But you seem quite pro-active at least on the forum. So, I am hopeful that you and your users will see the advantages in this form of filter.
Anyway, thanks for your time, and good luck with Reflector.
I don’t think you could do this in the original version 11, but I want to filter all content in a particular named folder, but there are multiple subfolders that this should apply to on different paths. It needs to be inclusion and exclusion based. My "Use Case" is for Unreal development. And now we are at UE5 and there is of course version control solutions such as Perforce, but they are only really useful for Games Development houses, for many the cost is prohibitive.
So back to the backup scenario, we might have
c:\unrealproject\Content\Megascans\*.*
c:\new_unrealproject\Content\Megascans\*.*
c:\previous_version_unrealproject\Content\Megascans\*.*
With this example Megascans folders can be huge, and full of redundant files, that is a master copy exists elsewhere on the disk.
I would preferably have one incremental backup job for the master directory
and any jobs with projects in the target directory (..\Documents\projects for instance) would have the Megascans subfolders excluded.
Unreal Dev is not the only time, I have had this type of "use case" come up many times over the years and constantly toyed with making my own backup solution. But I don’t have the time to reinvent the wheel. But you seem quite pro-active at least on the forum. So, I am hopeful that you and your users will see the advantages in this form of filter.
Anyway, thanks for your time, and good luck with Reflector.
Statistics: Posted by andyseabrook — 30 Jun 2022, 15:06 — Replies 1 — Views 5