Hi Karsten,
I'm not sure what you mean by the space for the controller and proxy, but the most space will be required for the PostgreSQL.
During an upgrade, the most critical part is transfrerring the configuration and cache databases from individual Jet DBs on v7 to a centralized PGSQL on v8, and also creating a restore points cache (i.e. performing repository indexing which is a background process after the cache upgrade). Repository caches in PGSQL typically take less space compared to Jet DB, while restore points cache may require singnificant space.
Approximately, upgrading a repository with 5 GB cache is expected within 6 minutes. Repository indexing duration per 1,000 restore points is around 3 minutes.
For the restore portal, there're no specific requirements or considerations.
Also, you can always contact your Veeam SA to get help with such upgrades.
Thanks
I'm not sure what you mean by the space for the controller and proxy, but the most space will be required for the PostgreSQL.
During an upgrade, the most critical part is transfrerring the configuration and cache databases from individual Jet DBs on v7 to a centralized PGSQL on v8, and also creating a restore points cache (i.e. performing repository indexing which is a background process after the cache upgrade). Repository caches in PGSQL typically take less space compared to Jet DB, while restore points cache may require singnificant space.
Approximately, upgrading a repository with 5 GB cache is expected within 6 minutes. Repository indexing duration per 1,000 restore points is around 3 minutes.
For the restore portal, there're no specific requirements or considerations.
Also, you can always contact your Veeam SA to get help with such upgrades.
Thanks
Statistics: Posted by Polina — May 15, 2026 3:42 pm






