Over the last weeks we received a lot of feedback and requests and so we are now at version 5 of our calculator.
After some discussions we decided to add all sizing relevant calculations into one beautiful Excel document for internal use. So my swiss colleague Stephan Herzig started creating a calculator for calculating these costs, based on numbers we received from our worldwide team (thanks Gummett). These costs are not that high, but it’s always better to know them before your your credit card bill clunks through the letter box. Those processes are also generating ingress/egress/API call operations (=extra costs). Whenever we start a backup job, the job/proxy gets data from Microsoft 365 and stores it back to an object storage Processes are reading, comparing, deleting and writing bocks to the object storage. There are also providers like wasabi (with an all-inclusive-rate.īut what does it mean in terms of VBO. These costs vary from provider to provider.
#Veeam backup for o365 download
That means you can drop your files into the cloud but if you want to download them again there are egress and API call costs. To keep it simple – Working using an Object Storage makes life easier.īut using cloud also means that sometimes it’s not that easy to predict all the prices as you wish.Įspecially when working with object storage – it’s like a doorbuster – it’s easy to get in and hard to come out. Just in short why: More flexibility, easy to grow and expand, more performance and affordable prices.
In the last past month a lot of customers were changing from on-premise storage to the cloud. Repeat the steps for each service by selecting it using the dropdown menu.īefore we start with the calculation lets talk about the object storage integration. Now select “Storage” and “180 days” to see your numbers. Then select the proper report in the top left corner: On the left side go to “Reports” and click the button “Email activity”. You can find your current usage in the O365-Adminportal: ()
Our proxy sizing in VBO is based on the amount of objects. So we do need the amount of users per service. To get some realistic numbers, we collect the informations per service, because in the background each service has its own compression capabilities and it does make some difference later in the cost calculation. ?īefore we concentrate on object storage I will give you some important information for your general VBO-Sizing. Wouldn’t it be great if we had a tool for this ? For sure ! But let us first build up some tension. Welcome back after a longer break due to holidays, personal changes and some challenges over the last weeks.Īs one of the main responsible german Systems Engineer for Veeam Backup for Microsoft Office 365 (VBO) I received a lot of questions and requests regarding the right sizing for a VBO-environment as well as for the “new” Object Storage Repository feature, which is available since version 4. Click here to download the latest Verision: Download