> For the complete documentation index, see [llms.txt](https://docs.storware.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storware.eu/backup-and-recovery-7.4/protecting-virtual-machines/virtual-machines/verge.md).
# Verge
VergeIO is the future of virtualization and the leading VMware Alternative. Unlike hyperconverged infrastructure (HCI), its ultraconverged infrastructure (UCI) collapses the traditional IT stack (computing, storage, and networking) into an integrated data center operating environment, VergeOS. Its efficiency enables greater workload density using existing hardware while improving data resiliency.
Storware Backup & Recovery supports backup for Verge:
* Full backup
* Incremental backup
## Verge Change Block tracking
Verge provides block change tracking based on the hashes. Storware Backup and Recovery is using this method to perform incremental backups.
## Supported features
| | CBT |
| ------------------------------------------------------------------- | ------ |
| Supported versions | 26.0.2 |
| The last snapshot is kept on the hypervisor for incremental backups | No |
| Access to hypervisor OS required | No |
| Proxy VM required | No |
| Full backup | Supported |
| ----------------------------------- | -------------------- |
| Incremental backup | Supported (with CBT) |
| Synthetic backups | Supported |
| File-level restore | Supported |
| VM disk exclusion | Supported |
| Quiesced snapshots | Supported |
| Snapshots management | Not supported |
| Pre/post command execution | Supported |
| Access to VM disk backup over iSCSI | Supported |
| VM name-based policy assignment | Supported |
| VM tag-based policy assignment | Supported |
| Power-on VM after restore | Supported |
## Network requirements
**Connection URL:** `https://VERGE_IP:VERGE_PORT`
| Source | Destination | Ports | Description |
| ------ | ----------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Node | Verge API | environment-specific, configured during VergeOS deployment | API access to the VergeOS API |
| Node | NAS servers | 2049/tcp | NFS v4 access for data transfer
NAS servers should be in the dedicated network
- configured in VergeOS upfront,
- also specified in the hypervisor manager settings
|
## Configuring Verge for Storware Backup and Recovery
To perform backup and restore operations for Verge, you need to create a NAS virtual machine, which will be used for data import and export operations. The machine shares NFS share that will be mounted in the node.
To create NAS service proceed with the following steps:
1. Log in to Verge admin console
2. Select NAS from the main menu and then NAS Services, select New
3. Provide the name of the virtual machine that will be created. Note the name, you will need to provide it in the Storware Backup and Recovery while adding hypervisor. \
You can adjust other options to your needs. When configuring network parameters please consider that the virtual machine must be accessible for the node.
4. Make sure that the "Allow Export" option is checked.
5. Power on the create machine
## Adding hypervisor managers
When creating the hypervisor manager, provide the following data in the General tab fields:
URL - Verge URL, e.g. `https://VERGE_IP:VERGE_PORT`
Username - Verge user
Password - password for the user
In the "Verge settings" tab provide the name of the NAS service virtual machine created in the previous step.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.storware.eu/backup-and-recovery-7.4/protecting-virtual-machines/virtual-machines/verge.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.