hi,
we are preparing a upgrade from 7.1 to 8.4.
it is a small setup with one controller and one dedicated Windows proxy. there are 17 organizations and 21 S3 repositories with 27TB. restore portal is activated.
how can i calculate the needed HDD space for the controller and proxy?
how much time should i plan for the repository upgrades? is it a „offline“ process?
should i set the required firewall ports for psql and NATS before the upgrade?
are there any todos for the restore portal after the upgrade?
tia
Karsten
-
karsten123
- Service Provider
- Posts: 747
- Liked: 193 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
-
Polina
- Veeam Software
- Posts: 3981
- Liked: 1016 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Upgrade 7.1 to 8.4
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
-
karsten123
- Service Provider
- Posts: 747
- Liked: 193 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Upgrade 7.1 to 8.4
thank you very much Polina.
it is all about guessing the required disk space for the VB365/ postgresql server, which is going to be the same.
regards
Karsten
it is all about guessing the required disk space for the VB365/ postgresql server, which is going to be the same.
regards
Karsten
-
Polina
- Veeam Software
- Posts: 3981
- Liked: 1016 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Upgrade 7.1 to 8.4
Indexing is what takes quite a lot of space in PGSQL. Estimating the size is a bit complicated - I'll send you formula in DM.
Who is online
Users browsing this forum: dali@iae.nl and 17 guests