System Requirements Page: Quick Survey

[anton.maryasov]

Hi everyone!
We’re expanding the Veeam Backup & Replication User Guide to include all supported workloads. As part of this, the System Requirements section will grow significantly, and we’d like your feedback on the most convenient way to deal with it.

Please take a moment to have a look and vote here.
The survey will take about 5 minutes.

Thanks! Your input will directly influence how we structure the updated guide.

[Markusd]

Happy to give my 2 cents

Survey completed

[Eric_Cartman]

Happy to help - survey completed

[MoritzG-Seidemann]

Taken and appreciated

[dabrigo]

Took the survey, only a suggestion for question 3: as i use the search options indipendently if i need to look at a specific topic or if i search for something in the contents, can you add a "Both" option?

[tinto1970]

thank you. my opinion is that veeam's doc has become very huge and needs a bit of re-organization

[m.novelli]

I think no sysadmin ever looked at a software hardware system requirements

Marco

[e.rottier]

Took the survey, only a suggestion for question 3: as i use the search options indipendently if i need to look at a specific topic or if i search for something in the contents, can you add a "Both" option?

I am of the same opinion. Both would be best.

You can have two versions of both:
1) Completely separate
2) When clicking on the article, then go to the correct section in the general\large article.

I would personally go for Option C, version 2.

[andrepulia]

Done! Happy to help

[jasonede]

Done. Although searching I tend to use a variety of methods. I start with table of contents and if can't find simply in that I go to the search function.

[anton.maryasov]

Hi everyone,

Just wanted to say a big thank you to everyone who took part in the survey and shared feedback. We received 300+ responses, and the result was very clear — over 85% of you preferred the fragmented system requirements format.

Based on that feedback, we went ahead and updated the System Requirements section, and the new version is already live in production.

The discussion also brought up a lot of useful insights and suggestions beyond the original question, and we’ve captured those internally. You’ll likely see some of these improvements appearing in the documentation over time.

Really appreciate everyone who took the time to vote and comment — this kind of feedback genuinely helps us make the docs better.

Thanks again!

BTW, if you're exploring the docs, give Veeam Intelligence on the Help Center a try