License administration
Viewing licenses
Types of licenses you see in GitProtect console may vary a bit from its business models— licenses used in GitProtect are assigned to agents that are doing backup (endpoint, server, feature worker, cloud worker, local worker) or to backed-up objects (as a Microsoft 365 user or a Git repository).
To see all of your available licenses in GitProtect Management Service go to Settings > License > See details.
To increase the number of available licenses please contact [email protected].
Refreshing licenses
GitProtect must periodically synchronize with the licensing server to verify the validity of your subscription and to adjust to any changes, such as added storage capacity or new licenses.
How it works:
Automatic Refresh — by default, GitProtect Management Service automatically refreshes your licenses once every 24 hours.
Offline grace period — to ensure continuity in on-premises environments, GitProtect allows the system to continue all backup and restore operations for up to 3 days without a successful license verification.
If the verification fails and your license package is not verified within three days, the Management Service may stop working.
You can manually trigger a refresh if you have recently modified your license (e.g., upgraded your plan) and want the changes to take effect immediately without waiting for the automatic daily refresh cycle.
To refresh your licenses go to Settings > License and hit the Refresh button under your available license package.
On-premises licenses
The on-premises deployment model requires your Management Service to connect with the GitProtect license server once every three days.
This process is performed automatically. If the device with GitProtect installed has no internet connectivity, you can configure the specified rules to allow the device to connect to the component listed in the below table.
one.xopero.com
443 (HTTPS)
213.222.221.126
Last updated
Was this helpful?