Hi Patrick,
1. We have one backup per standalone job, so we only need one system name
2. The ID is automatically generated based on various source server parameters that remain constant at the operating system level and serve as unique identifiers (such as BIOS UUID)
3. Regarding backup copy, the limitation for the maximum number of symbols is needed to prevent potential issues with file systems that do not support long file paths
There is no documentation or best practices regarding modifying this naming convention: users are not supposed to modify it in any way. However, could you please provide more context about the problem you are trying to solve and why you are interested in knowing all of this?
Thanks!
1. We have one backup per standalone job, so we only need one system name
2. The ID is automatically generated based on various source server parameters that remain constant at the operating system level and serve as unique identifiers (such as BIOS UUID)
3. Regarding backup copy, the limitation for the maximum number of symbols is needed to prevent potential issues with file systems that do not support long file paths
There is no documentation or best practices regarding modifying this naming convention: users are not supposed to modify it in any way. However, could you please provide more context about the problem you are trying to solve and why you are interested in knowing all of this?
Thanks!
Statistics: Posted by PetrM — Nov 04, 2024 5:24 pm
