Skip to main content

Using Secondary Paths (User Configuration ProfileUnity ADM GPO)

Lukasz Mikosz
  • Created:
  • Updated:

 

Problem:

How does Secondary Paths work?

Symptoms:

mceclip0.png

Possible Resolution(s):

This setting allows administrators to specify both a primary path prefix and secondary path prefixes for the storage of INI Configuration files, Portability files and FlexApp packages. This allows for fail-over protection should access to the primary location fail. Mixing UNC paths with cloud paths is allowed.

  • Secondary paths separate in to three parts: Configuration | FlexApp | Portability 
  • No needed for the "|" when there is only one expression for secondary path (Ex. FlexApp fail over only)
  • Each part can have multiple fail over locations
  • Only "Server_Name" can be substituted in fail over event
  • There is no limit how many fail over paths can be added
  • The greater than symbol (>) follows the primary path and signals the shift between the primary and secondary paths.
  • A comma (,) separates secondary paths, if multiple secondary paths can be given
  • A vertical bar or pipe (|) separates rules, if multiple rules are configured (optional)
  • If FlexApp only fail over is needed "|" can be omitted all together (look below examples)
  • Secondary paths (And Primary Paths) could be mixed matched: CIFS > Cloud or Cloud > CIFS etc.
  • When "Cloud" is used its bucket/Folder not Server\Share
  • FlexApp fail over ONLY works when "Cache Mode" is enabled on the DIA Packages.
  • FlexApp not only checks for avability of the DIA package but also checks for latency to the share and uses the path which ever is faster.
  • FlexApp is also inline to the block request. - Seamless fail-over while apps are running.

Example for Configuration ini path fail over:

Primary path for INI (This is in your "INI Path" GPO setting): \\Server1\Share_a\ProfileUnity

\\Server1\Share_a > \\Server2\Share_a, \\Server3\Share_a

If the primary path (Red) becomes unavailable the secondary path is checked and so on. Than after inserting "|" (Optional) you can stack alternative FlexApp and Portability paths.

For secondary path and third fail over path the "ProfileUnity" folder was dropped as only "Server_Name" and share needs to be listed. In this case "Share_a" is the share name which is static. 

For more information how to use with S3, GS or UNC and alternate FlexApp and Portability paths, please check page 52 of Installation and Configuration Guide

More Examples:
For FlexApp fail-over only without configuration ini path or Portability path fail over:
  • FlexApps are located in \\MyServer1\Share1\FlexAppsDIA failing over to: \\MyServer2\Share1\FlexAppsDIA
  • Correct syntax:
    • \\MyServer1\Share1 > \\MyServer2\Share1
For Portability fail-over only without configuration ini path or FlexApp path fail over:
  • Portability folders are located in \\MyServer1\HomeShare1\%username%\Portability failing over to: \\MyServer2\HomeShare1\%username%\Portability
  • Correct syntax:
    • \\MyServer1\HomeShare1 > \\MyServer2\HomeShare1

       

       

      Product: ProfileUnity-FlexApp

      Product Version: 6.8.x+

       

Related articles