Gostev wrote:Some still have issues, which are suspected to be caused by lack of RAM on the backup repository server. You can read the detailed feedback on the last few pages of this thread.
CPU: x86 processor (x86-64 recommended).
Memory: 4 GB RAM, plus up to 2 GB RAM (32-bit OS) or up to 4 GB RAM (64-bit OS) for each concurrent job depending on backup chain’s length and backup files sizes. For more information, see Limitation of Concurrent Tasks.
Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.
JaySt wrote:Gostev, all good news, but i still don't get why there's no Veeam KB describing the current status. Some kind of advise on the minimum requirement of KB4088787 and , as you mentioned, things like "use 64K for now" is good stuff to get out there if you ask me.
Gostev wrote:No, classic incremental backup does not benefit from ReFS block cloning, so you can use any file system at all.
As for stability, I just answered this question to someone else (see the first post on this very page). Thanks!
Giacomo_N wrote:And forever incremental?
Gostev wrote:Thank you for your kind words, guys
Yes, every backup mode updates an existing full backup file, or creates new synthetic full backup files does benefits from fast cloning.
CloudMSP wrote:Everything is working, but will Veeam automatically see that it ReFS and fast clone capable now?
Gostev wrote:Yes. You will start seeing benefits after the next active or synthetic full backup.
Users browsing this forum: Bing [Bot] and 19 guests