Recently I had the opportunity to deploy Veeam B&R utilising Cloud Connect Replication for a customer to replace their existing DR solution. We were running into an issue with a couple replication jobs that were sitting at 99% for longer than I would expect, in some cases for several hours.
I wasn’t sure what it was doing as there was no network traffic, CPU or even disk usage on the on the source that could be detected. The Veeam job showed no tasks currently underway and I didn’t want to speak to the Service Provider to check their end until I had verified everything was working as expected at the source so I kept digging.
Rick Vanover has posted on the official Veeam blog regarding the opening of the Veeam Vanguard nominations for 2018. This will be the third year of the Vanguard program for which the recipients receive a variety of awesome benefits, one of which is a trip to VeeamON.
Some Vanguards are bloggers, some are active on the Veeam Forums, some are active on Spiceworks sharing a lot of Veeam-specific information or even on the Veeam subreddit, the list goes on for all of the ways Vanguards have engaged with the Veeam community.
If you know anyone that you’d like to nominate, perhaps yourself even, I strongly recommend giving it a go.
Nominations will be accepted until Friday, Dec. 29. You can go through the nomination process here.
Phase 1 – Create the Backblaze B2 Bucket
Phase 2 – Install and Configure Synology CloudSync
Phase 3 – Configure Veeam Backup Repository
Phase 4 – Create the Veeam Backup Job
Phase 5 – Testing and Tuning
B2 Cloud Storage is an object storage service offered by Backblaze that enables users and organisations to upload files to their heart’s content billed on a per monthly basis using a pay for what you consume model. Backblaze has evolved this object storage service ‘B2’ out of the already successful $5 a month unlimited backup plan which was built from the ground up using Storage Pods. Storage pods are designed in-house by Backblaze, leveraging consumer grade hardware and hard drives in a purpose-built chassis designed to minimise costs, reduce footprint and yield the best dollar per GB possible. For example, using 4TB drives, they can achieve a cost per GB as low as $0.036.
These Backblaze pods, which are now up to revision 6, are literally filled to the brim with hard drives, over 60 of them in fact in a 4U chassis. I recommend that you go and check out more on these awesome units here.
So, Backblaze takes these Storage Pods a step further for B2, by grouping 20 at a time into a Backblaze Vault it enables them to optimise reliability and durability of the entire system.
The inaugural ANZ Veeam User Group meeting has been scheduled for 6:00 PM on Friday the 22nd of September in BrisVegas. The location of the meeting will be at the Saxons Office, Level 11 300 Adelaide St Brisbane City.
We are planning for 3 speakers covering a range of Veeam topics and we expect the event to run for 1.5 hours.
The Veeam ANZ User Group has a strong focus on community and networking with other Veeam users so come join us for a wonderful night learning and discussing all things Veeam.
To register, please go to this Eventbrite link.
So you may have noticed that when you’re configuring a backup job in Veeam Backup & Replication there is an option to ‘Enable guest file system indexing’. The menu tells us it will “create catalog of guest files to enable browsing, searching and 1-click restore of individual files” which sounds quite important but then it also says that “indexing is optional and not required to restore instant file level recoveries”. So you may be thinking whats the point of it then or whats the advantage here and should I enable it?
What is it? Allows you to perform searches within guest OS files stored inside the backups without having to mount the backup files first.
How does it work? It’s worth pointing out that Veeam is agentless so this indexing happens without agents, nor does it need to scan the whole file system, instead when a backup job runs, during the guest OS freeze process, Veeam creates a catalog (or index) of the VM guest OS files by directly reading from the NTFS Master File Table (MFT). For a typical VM, the required data is captured and parsed nearly instantly, which Veeam calls Instant Indexing. After the index has been created, this information is stored on the Veeam Backup & Replication server.
Are you experiencing poor performance for your Veeam File to Tape jobs? It is likely caused by your SQL Express database that the Veeam B&R server is running from. It may be time to upgrade to a licensed version of SQL Server just as this customer has done below, a job that took 25 hours has now reduced down to 5 hours.
click to open a larger version
The new SQL Standard 2016 instance was installed on the same Veeam B&R server where SQL Express 2012 was running.
A few days ago VMware announced the second half of 2017 list for vExperts recipients. A vExpert is someone that has demonstrated significant contributions to the VMware community, as well as the desire and willingness to share expertise with others. Contributing is not always blogging or Twitter as there are many public speakers, book authors, script writers, VMUG leaders, VMTN community moderators and internal champions among this group.
I am stoked to share that I was awarded the vExpert title under the Evangelist path for 2017.
Congratulations to all the other VMware evangelists, partners, and employees that have made the list for this year.
The announcement page can be found here.
What do they do? VBM files are an XML dump of relevant backup metadata pertaining to the relevant backup job from the Veeam DB. A VBM file will be created for each backup and backup copy job.
Why do we create VBMs? Before VBM files, Veeam would read metadata information from the backup files themselves. As Veeam was deployed into larger and larger environments it soon became apparent that this method of reading metadata information was too I/O intensive and needed to be improved, so the VBM file was born.
A quick post regarding max concurrent tasks in Veeam B&R which are tunable options in both proxies and repositories. The default max concurrent task for proxies is set to 2, for backup repositories the default is set to 4. An important thing to note is that we are limiting different things when configuring this max concurrent task between proxies and repositories.
When configuring proxies, the max concurrent tasks are based on a single virtual disk. So for example, if we had a single virtual machine with 4 virtual disks or a 4 virtual machines with a single virtual disk each, the units of resource scheduling required is the same, the units of resource scheduling required being 4 virtual disks that need to be processed.
Did you know that Veeam ONE has a tool called deployment projects that has the ability to simulate how a task such as adding or evicting hosts and VMs impacts your virtual infrastructure? These simulations help us to review predicted resource capacities against future resource demand, provide practical recommendations and help identify potential resource shortages. It’s a quick and easy way to check your resources before making small or large changes. Think of it as a way to perform due diligence and gain insight before making any changes to your virtual environment.
Deployment Projects can be found under Veeam ONE Reporter, to access Veeam ONE Reporter we browse to the URL of the Veeam ONE Reporter website. This website runs on the machine where the Veeam ONE Web UI component is installed. Assuming you have are using the default port it would look similar to https://veeamoneip:1239