VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Block Sizes As can be seen from the field, optimal value for the stripe size is often between 128 KB and 256 KB. However, it is highly recommended to test this prior to deployment whenever possible.During the backup process data blocks are processed in chunks and stored inside backup files in the backup repository. You can customize the block size during the Job Configuration using the Storage Optimization setting of the backup job.By default Veeam’s block size is set to Local Target, which is 1 MB before compression. Since compression ratio is very often around 2x, with this block size Veeam will write around 512 KB or less to the repository per Veeam block.This value can be used to better configure storage arrays; especially low-end storage systems can greatly benefit from an optimized stripe size.There are three layers where the block size can be configured: Veeam block size for the backup files, the filesystem, and the storage volumes.Let’s use a quick example: The Veeam block size
I like to show all the utilities that Veeam offers us ... to perform administration tasks in the backup infrastructures Did you ever use??Extract Utility Veeam Backup & Replication comes with an extract utility that can be used to recover machines from backup files. The extract utility does not require any interaction with Veeam Backup & Replication and can be used as an independent tool on Linux and Microsoft Windows machines.The extract utility can be helpful, for example, if it is written to the tape next to machine backup files. In this case, you get a possibility to recover machines from backups at any moment of time even if backups are removed from Veeam Backup & Replication or Veeam Backup & Replication is uninstalled at all. IMPORTANT! The extract utility does not work with backups that are stored in scale-out backup repositories. The extract utility can be used in two interfaces:Graphic user interface (GUI) Command-line interface working in the in
Applicability and efficiency of each transport mode primarily depends on the type of datastore used by the source host — local or shared, and on the backup proxy type — physical or virtual. The table below shows recommendations for installing the backup proxy, depending on the storage type and desired transport mode.which one do you use?
Best Practices In my opinion it is very important to keep this best practice in mind If the integration API is unavailable due to licensing restrictions, or if any other deduplication appliance is used, the appliance should be considered non-integrated.In order to optimize throughput for deduplication appliances, please use the following configuration guidelines: Job configurationThe following settings are configured in the backup job “Edit” wizard under Storage > Advanced. Options not defined in this table are optional and not related to backup repositories using deduplication storage.Setting Value Tab: Backup Backup mode Incremental Create synthetic full backups periodically Enabled - if integrated Transform previous backup chains into rollbacks Disabled Create active full backups periodically Enabled - if non-integrated Tab: Maintenance Perform backup file health check Disabled Defragment and compact full backup file Disabled Tab: Storage Ena
The Veeam Ready database provides a list of all partner solutions that have successfully passed Veeam’s testing criteria. Solutions are grouped by company name, Veeam Ready classification, and more. So, you can select by Alliance Partner - Model Family - Category Example: I chose by category I think it is something very useful when it comes to having any questions about compatibility and Veeam Product Release Support . https://www.veeam.com/ready.html?x-clickref=1011lbSfagY2
In another Topic, I wrote about designing a Proxy In This Topic will see about the repository design.We need to consider The key recommendation is to follow the 3-2-1 rule. Calculate 1 core and 4GB RAM per repository task slot. The recommended minimum for a repository is 2 cores and 8GB RAM.Sizing The recommended amount of CPU for a repository is 1 core per concurrent configured task slot on a repository server. Configure at minimum a 2 core and 8GB RAM repository server to allow the operating system to be more responsive. When sizing task slots on a repository you have to understand when and how many task slots are consumed. Any write process will consume a task slot. So backing up 10 VMs in one job using per-job backup chains will only write one file (VBK/VIB) in the end - so it consumes one task slot. Running the same backup job with per-VM backup files will create one file per VM and thus can leverage up to 10 tasks slots (when available). Backup Copy Jobs, Agent Backups and
I hope that this two consideration will usefull to you I await your likes and comments
Throughout these years, I have been to many talks and events of Veeam, I have given many VMCE courses, and a lot has happened to me on this side in South America, the customers did not use Surebackup or Surereplica, they have told me that they did not know that they could use it, among other answers. And I think it is one of the most important features that Veeam has . Has it happened to you? I would like to read them …
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.