Availability for the Always-On Enterprise
Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Post by Gostev » Aug 17, 2013 9:50 am


General FAQ
This topic (scroll down) covers general information about the product, and all core features which are not hypervisor-specific.

VMware vSphere FAQ
The following FAQ covers VMware vSphere specific questions:

Microsoft Hyper-V FAQ
The following FAQ covers Microsoft Hyper-V specific questions.
Hyper-V : [FAQ] FREQUENTLY ASKED QUESTIONS (pending content collection)

Tape FAQ
The following FAQ covers tape specific questions.
Tape : [FAQ] FREQUENTLY ASKED QUESTIONS (pending content collection)

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Post by Gostev » Aug 17, 2013 9:51 am

Q: How the product is licensed?
A: Per physical CPU socket of "source" hypervisor host (where protected virtual machines reside). Destination hosts for replication and migration jobs do not need to be licensed. Hosts running virtual machines which are not being processed by Veeam do not need to be licensed, even if they are a part of the same cluster.

Q: Does CPU core count matter?
A: No, the price is the same no matter of amount of CPU cores. License tiers based on CPU core count are gone with the new pricing that became effective on July 1st, 2013.

Q: Are any of the product components licensed separately? Namely Enterprise Manager, backup servers, backup proxy servers, backup repositories, WAN accelerators, tape libraries.
A: No, they are not licensed separately. You can deploy as many of those components as it makes sense for your environment.

Q: How licensed sockets for each hypervisor are tracked, is it the same pool?
A: No, each hypervisor has its own socket count in the license file.

Q: Is the socket price different depending on hypervisor?
A: No, the price is the same no matter of hypervisor.

Q: Can I change my licensed sockets from one hypervisor to another?
A: Yes, you can do it at any time by contacting your Veeam sales representative. Conversion is available free of charge. As a part of the process, you will also be provided with a temporary license key giving you the licensed amount of sockets for both hypervisors to allow coexistence of environments on the same backup server. This license key is provided at no charge, is good for 3 months, and can be extended upon request for large socket count environments. Technical support for both hypervisors is also included at no charge for the duration of the temporary license.

Q: Can I install multiple backup servers across multiple sites using the same license file?
A: You can install any number of backup servers using the same license file, as long as the actual socket usage across all backup servers does not exceed the licensed amount. To ensure compliance, we recommend that you use Veeam Backup Enterprise Manager, which provides centralized license management. Enterprise Manager reports actual socket usage across all backup servers, and can be used to push the new license file to all connected backup servers.

Q: Can I mix and match different product editions in the same environment.
A: No, the license edition has to be the same.

Q: At what specific moment do the source host sockets get counted towards the licensed sockets pool?
A: Upon first backup, replication or copy of a VM that is running on the given host.

Q: I have removed some hosts from my environment, can I get their sockets back into the license pool?
A: Yes. Open the license management dialog in the main product UI, select the host, and click Revoke.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Upgrade: Licensing

Post by Gostev » Aug 17, 2013 9:53 am

Q: I am an existing customer running version 6.x. Do I need new license file to install v7?
A: Yes, you need to obtain new license file for version 7.x. Your existing license file for any previous versions will not work.

Q: Is v7 a free upgrade from previous versions?
A: With Veeam, all upgrades are "free" for customers on maintenance. All new license purchases include 1 year of maintenance. If you bought B&R more than 1 year ago, but did not extend your maintenance after the 1st year, you need to address this with your Veeam sales representative first by purchasing maintenance, including the "blank" period coverage.

Q: I am current customer on maintenance, how do I get the license file for v7?
A: Please use License Management Portal in the product download area (under My Account) to get your new license file, or email licensing@veeam.com for assistance. If you choose to email, expect delayed response in the first few days after the product has been released.

Q: Which v7 product edition do I get upgraded to when upgrading from 6.x?
A: Same product edition as you are currently using with v6 (Standard or Enterprise). Additionally, all Enterprise edition customers who were active on maintenance as of July 1st, 2013 can claim optional free upgrade to Enterprise Plus. The free upgrade must be claimed by Nov 1st, 2013. Note that claiming the upgrade will increase your product maintenance costs starting the next maintenance cycle, as those are calculated off MSRP.

Q: What are the feature differences between the Standard, Enterprise and Enterprise Plus editions? Are there any new differences comparing to v6?
A: No existing features have been removed from any editions. Vast majority of new features enhancements are available right in the Standard edition. Some newly added v7 features are only available in the Enterprise or Enterprise Plus edition. Please refer to the Veeam Backup & Replication Editions Comparison document on the product page under Resources tab.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Upgrade: Technical

Post by Gostev » Aug 17, 2013 9:54 am

Q: Do I need to perform clean install, or can v7 upgrade my existing B&R install?
A: We support in-place upgrade from versions 6.0, 6.1 or 6.5 (any patch level). If you are running older versions, please contact our support for instructions and assistance with performing an upgrade.

Q: How do I upgrade to 7.0?
A: The upgrade process is very simple and straightforward. Make sure no jobs or restore processes are active, and run 7.0 setup program on your backup server. After the setup finishes, launch the B&R and follow the Upgrade wizard to automatically upgrade all the remaining components. For more details and step-by-step process, please refer to the Upgrade section of the Release Notes document.

Q: Will upgrade preserve my jobs and other settings?
A: Yes, all your jobs and settings will be preserved. This also means that some new features (parallel processing, new default compression level) will not be enabled by default, and must be enabled manually if desired. This is to ensure the product behavior remains the same after upgrade.

Q: What B&R version can I upgrade to version 7.0 from?
A: You must be running version 6.0, 6.1 or 6.5 (any patch level).

Q: Does 7.0 backup server support both 32-bit and 64-bit OS?
A: v7 backup server only supports 64-bit OS. If your 6.x backup server runs on 32-bit OS, you must migrate it to 64-bit OS before attempting the upgrade. You can use configuration backup functionality (available starting version 6.5) to easily migrate your 6.5 backup server to the new host prior to performing upgrade.

Q: Do 7.0 backup proxies and backup repositories still support both 32-bit and 64-bit OS?
A: Yes, meaning you can keep your backup proxies and backup repositories intact. However, we recommend using 64-bit servers for backup repositories, as this provides for supporting larger backup sizes.

Q: Can 7.0 and previous versions be installed on the same server?
A: No. You can, however, run different versions in parallel on different servers while processing the same VMs without any issues (as long as jobs do not overlap). This is the approach most of our customers choose for POC testing of new versions before upgrading their production deployment.

Q: Can Enterprise Manager 7.0 collect data from Veeam Backup & Replication 6.x servers?
A: Yes.

Q: Can I restore backup made with previous product versions using 7.0?
A: Yes. Version 7.0 can restore backups made with any version of Veeam Backup & Replication starting from version 1.0.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

System Requirements

Post by Gostev » Aug 17, 2013 10:02 am

Q: What are the system requirements and supported configurations for the product components, and for protected VMs?
A: Refer to the System Requirements section of the Release Notes document available in the download area, and on the product page under Resources tab. Refer to platform-specific FAQ topics for additional platform-specific information.

Q: Is Veeam Backup & Replication supported running in a VM?
A: Yes.

Q: Is Veeam Backup & Replication available as a Linux-based virtual appliance?
A: No.Veeam Backup & Replication must be installed on Microsoft Windows.

Q: What are the benefits of using the 64-bit operating systems for Backup & Replication components that support both 32-bit and 64-bit OS?
A: For backup repositories, 64-bit operating systems enable support for much bigger backup files. There is no benefit in having 64-bit backup proxy servers at this time, however VMware vSphere 5.5 support, once available, will require 64-bit backup proxy servers.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Job Types

Post by Gostev » Nov 07, 2013 1:11 pm

Q: What are Backup jobs designed for?
A: Backup jobs produce highly compressed and deduplicated backup files with production VMs data, which allows you to save significant amount of space required to host the backups. Full VM restore from backup normally takes significant time due to the need to extract and copy full VM image from backup to the production storage, but can also be done instantly for a limited number of VMs (see Instant VM Recovery).

Q: What are Backup Copy jobs designed for?
A: Backup Copy jobs efficiently create copies of your backups both on-site (usually for archival purposes) and off-site (to meet the off-site backup storage requirement). Maintaining multiple copies of your backups, with some of them being off-site is dictated by industry best practice known as 3-2-1 backup rule: at least 3 copies of production data (1 production and 2 backups), with backups stored on 2 different media types, and 1 of them stored off-site.

Q: What are SureBackup jobs designed for?
A:: SureBackup jobs perform actual recovery verification by powering on one or more VMs in the isolated environment, and verifying recovery by checking if VM was started, OS was booted, VM responds to ping, and VM applications are running fine. SureBackup job is also the key component of U-AIR and On-Demand sandbox functionality.

Q: What are Replication jobs designed for?
A: Replication jobs produce exact replicas of production VMs on standby hosts. These replicas can be powered on immediately when production VM goes down, without any dependencies on Veeam Backup and Replication server, and at full I/O performance. However, replicas require standby host, and more disk space than backups due to being stored in uncompressed, native format. Thus, replica are typically used for tier 1 VMs with low recovery time objectives.

Q: What are Migration jobs designed for?
A: Migration jobs can move the running VMs to the selected hosts and storage with minimum possible downtime. Depending on your migration scenario and VMware licensing level, the migration job will automatically leverage one of the following: VMware VMotion, VMware Storage VMotion, Veeam Quick Migration with SmartSwitch, or Veeam Quick Migration with cold switch. This allows you to quickly evacuate VMs from hosts requiring urgent maintenance without affecting bandwidth or performance, or perform inter- and intra- datacenter migrations. Migration jobs are only supported for VMware VMs.

Q: What are VM Copy jobs designed for?
A: VM Copy jobs produce exact copies of selected VMs on the selected storage, and can be used for scenarios such as datacenter migrations, creating test labs, and ad-hoc backups. VM Copy jobs support processing of running VMs. Unlike backup job however, VM Copy does not support "incremental" runs. VM copy jobs are only supported for VMware VMs.

Q: What are File Copy jobs designed for?
A: File Copy jobs copy regular files between any servers managed by Veeam (Windows or Linux servers, or hypervisor hosts), and can be used for various administrative tasks. File Copy jobs do not support processing of virtual disk files belonging to running VMs.

Q: What are Backup to Tape jobs designed for?
A: Backup to Tape copy Veeam backup files to tape with full tracking of the content of copied backup files in the tape catalog. This allows for streamlined restores, with restore process being able to pick the required tapes automatically.

Q: What are File to Tape jobs designed for?
A: File to Tape jobs copy regular files from any servers managed by Veeam (Windows or Linux servers, or hypervisor hosts) to tape. Copied files are tracked in the tape catalog, however Veeam backup files are treated as regular files.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Post by Gostev » Nov 07, 2013 1:25 pm


Q: What is the data flow in case of backup?
A: Disk > Backup proxy > Network > Backup repository > Disk

Backup Proxies

Q: What is the backup proxy server?
A: Backup proxy fetches the VM data (configuration files and virtual disks) from the production storage, processes the data to reduce it size by applying deduplication and compression, and sends it off to the backup repository (in case of backup) or another backup proxy server (in case of replication). Backup proxy is also used to write the VM data (configuration files and virtual disks) back to the production storage which is used for VM restores, and to create and update replica VMs for replication.

Q: Why is it best to install the proxy server on a physical machine?
A: Because on-the-fly processing (deduplication and compression) of heavy data streams (hunreds of MB per second) requires significant CPU, Memory and I/O resources, physical proxy server suits best for 24/7 virtual environments with high consolidation ratio. Otherwise, you may find backup process affecting your production.

Q: What OS can I install the proxy server on?
A: Microsoft Windows XP or later. This can be new or existing server.

Q: Do I have to setup a proxy server to start using a product?
A: No, as default proxy server is deployed by the setup automatically. However, we recommend that you add additional ones for redundancy and load-balancing. For recommendations on where it is best to deploy additional proxies, please refer to the hypervisor-specific FAQ.

Q: Can the proxy server backup itself?
A: Yes, the proxy server can backup itself and any other Veeam Backup & Replication component.

Synthetic Backup

Q: What are the benefits of synthetic full backup that you provide?
A: A few times less stress on the production environment, a few times faster full backup performance, a few time less backup storage space due to no need to keep multiple fulls (available in certain backup modes only).

Q: I am using deduplicating storage device. Is synthetic full backup good for me?
A: Depending on how your storage implements deduplication (inline vs. post-process), you may get a better performance by using active (real) full backup instead of synthetic.

Q: We have a policy in place that requires me to do real full backups. Am I forced to use synthetic fulls with Veeam?
A: No, you can configure the job to perform active (real) full backups instead. Also, you can schedule active full backup, for example, once a month (or once a quarter), while doing synthetic full backup for the rest of the time. v7 provides great flexibility around scheduling active full backups.

Q: How exactly does reversed incremental backup mode work?
A: Refer to the following post: Veeam Synthetic Backup Explained

Q: How the transform option for incremental backup is different from what reversed incremental backup mode?
A: The end result of transformation is the same - single full backup containing the most recent VM state, with earlier restore points (VRB files) "going back" from that state. The difference is that with reversed incremental backup mode, this happens every time you run the backup. With incremental backup mode, this happens on synthetic full backup day only. This speeds up backup on incremental days, but slows it down on full backup day.

Backup Repositories

Q: What is the backup repository?
A: Backup repository is the place where your backups are stored. Each backup repository has local agent that enables for efficient local processing of incremental data in cases when backup proxy and backup repository communicate over LAN or WAN.

Q: What do you support as a backup repository?
A: The following repositories are supported:
• Any storage directly attached to a Microsoft Windows server (Windows XP or later, both x86 and x64 supported). The storage can be local disks, directly attached disk based storage (such as USB hard drive), or a iSCSI/FC SAN LUN in case the server is connected into the SAN fabric.
• Any storage directly attached to, or mounted on a Linux server (x86 and x64 of all major distributions are supported, must have SSH and Perl installed). The storage can be local disks, directly attached disk based storage (such as USB hard drive), NFS share, or iSCSI/FC SAN LUN in case the server is connected into the SAN fabric.
• CIFS (SMB) share. Password authentication is supported. Data can be written to CIFS share directly from the backup proxy server, or through secondary backup proxy server (useful in cases when CIFS share is located in the remote site).

Q: Can I use a virtual machine as my backup repository?
A: Yes, however be sure to think you recover plan in case of disaster carefully. While actual VM does not need to be running in order for you to be able to restore (as you can always import your backups directly from storage), remember that disaster may affect your ability to retrieve the backup files if you store them in the VM disks located on your production storage. Additional recommendations and considerations are provided in the hypervisor-specific FAQ.

Q: What RAID level do you recommend for the underlying backup storage?
A: We recommend at least RAID5 for minimal redundancy. However, our customers are recommending RAID10 whenever possible, because this helps with performance of I/O intensive backup operations (such as synthetic fulls).

Tape & Offsite

Q: Does Veeam support writing its backups to tape?
A: Yes, starting with version 7.0 Veeam offers native tape support. See Tape Support FAQ for more information [to be created]

Q: What is the best way to copy my backups offsite?
A: Backup Copy job to an offsite backup repository. Considering using built-in WAN acceleration for slow links.

Backup Modes

Q: What backup mode should I choose among available?
A: This depends on your requirements. Please review the attached document for pros and cons of each backup mode (considerations did not change since version 5.0)
v7 Choosing Backup Mode.xlsx
Choosing the backup mode that fits your needs
(10.87 KiB) Downloaded 4304 times

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Backup Copy

Post by Gostev » Nov 07, 2013 1:46 pm

Q: What is the data flow in case of backup copy?
A: Data flow depends on the transport mode selected in the job.
Direct mode: Disk > Source backup repository > Network > Target backup repository > Disk
WAN accelerated: Disk > Source backup repository > Source WAN accelerator > Network > Target WAN accelerator > Target backup repository > Disk

Q: Does Backup Copy job literally copy backup files?
A: No. Backup Copy job creates new backup files containing VMs it is selected to process.

Q: What is the difference between selecting VMs from infrastructure, from backup and by adding primary backup jobs?
A: There is no difference, this is just a matter of convenience. In all cases, Backup Copy job will obtain VM data from backup files.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Post by Gostev » Nov 07, 2013 1:47 pm

Q: What is the data flow in case of replication?
A: Disk > Source proxy > Network > Target proxy > Disk

Q: Can I use the same source and target proxy for replication?
A: Yes, but only when replicating locally (on-site replication). In this case, B&R scheduler will attempt to use the same backup proxy whenever possible.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Post by Gostev » Nov 11, 2013 3:05 pm

Q: Can you please go over of the whole concept and what it is all about?
A: See the following high-level video (for desciption of concept and architecture), and more technical demo (contains pre-release UI).

Q: What is SureBackup job?
A: SureBackup jobs perform actual recovery verification by powering on one or more VMs from backup or replica in the isolated environment, and verifying recovery by checking if VM was started, OS was booted, VM responds to ping, and VM applications are running fine. Additionally, to be able to detect the storage corruption issue (aka bit rot), SureBackup job can optionally verify the complete VM image by reading all virtual disk blocks and comparing the contents against CRC included in the block.

Q: What exactly is verified by the SureBackup job? VM availability, OS boot up or also applications?
A: All of this. There are 4 steps or level of recovery verification:
1. Check for successful VM startup (API call results). For example, if virtual disk is missing from backup file, or if disk descriptor file is corrupted, VM will not start and vCenter will tell SureBackup the issue.
2. Check for successful OS boot up by checking VM heartbeat. If OS does not boot, then guest tools will never start and heartbeat will never appear.
3. Check for network connectivity by pinging VM. If VM never appears on the network, this also indicates in some recovery issue.
4. Check VM applications by running test scripts against them. If application does not respond to test script with expected results, this indicates recovery issue.

Q: Are all of the above tests mandatory?
A: No. You can define which tests you want to use granularly for each VM, container, or linked backup job.

Q: Which VMs will be verified by SureBackup job?
A: All VMs from the selected application group (these run for the duration of the job providing required infrastructure services), and all VMs from linked backup jobs (these are simply started, verified and stopped one by one).

Q: I can see that it is possible setup SureBackup job without specifying application group to use. How so?
A: If you do not care to verify application recoverability, and just want to make sure VM can boot up, then you do not need to worry about some applications possibly not starting because of missing dependencies, and thus you do not need an application group to start and run those dependencies first. Just stuff your SureBackup job with linked backup jobs, and make sure application test scripts are disabled to avoid getting verification error reports.

Q: If I have not virtualized my Domain Controllers, how do you bring instances of those inside the virtual fenced lab?
A: You have to have at least one virtualized domain controller.

Q: I received report that verification had failed for one of the VMs. How can I quickly see what is going on?
Q: Open the corresponding SureBackup job session, locate the VM in question, right-click it and choose to restart it. Click the hyperlink under VM name to open its console (or use vSphere client), and troubleshoot the recovery issue manually.

Q: Verification procedure for some application we have is a manual process that cannot be scripted. What is our best option?
A: Create dedicated application groups for these applications. Create SureBackup job with this application group, select the Keep VM running checkbox, and schedule the job with the required period (say, once a week after full backup). VMs will sit there and wait for staff responsible for manual recovery verification to come in the morning and perform the required tests by connecting to VM with vSphere Client.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Post by Gostev » Nov 11, 2013 3:40 pm

Q: What kind of deduplication do you perform?
A: We perform agentless, block-level, inline (on-the-fly) deduplication. Deduplication happens both at source (before data is sent to backup storage, which significantly improves incremental backup performance), as well as target (to achieve additional reduction for jobs with multiple VMs).

Q: What are the typical data reduction ratios?
A: Compression and deduplication ratios up to 10x and more of the original size can be achieved, but this depends on too many factors, such as amount of VMs in the job, similarity of those VMs, content of virtual disks, etc.

Q: 10x is nice from software, but other software and hardware dedupe vendors claim to have 100x and more deduplication ratio?
A: Ask them to provide the formula they are using to calculate dedupe ratio. With Veeam, 10x is pure deduplication ratio within a single full backup file (bytes in divided by bytes out). Other vendors often inflate ratios to achieve impressive numbers for marketing purposes. This is typically done by assuming each backup is full. If you apply this approach to Veeam, then with most typical 30 days retention policy with daily backups, you will get up to 300x "marketing" dedupe ratio. This is because Veeam synthethic backup allows you to keep only one full backup on disk at any time (no matter of how long your retention policy is).

Q: To what level the deduplication is done?
A: We do block level dedupe with constant block size (configurable 1024 KB, 512 KB or 256 KB blocks), on the job level (not between jobs).

Q: I've been told that Veeam deduplication is inefficient because it uses large block sizes.
A: Veeam deduplication is designed to work alongside with compression, so you should be looking at the overall data reduction ratio instead. Large block size allows for both higher processing performance, and much better compression ratio for individual blocks. This allows Veeam to achieve the same data reduction factors with much smaller processing overhead. As you can see from this research by EMC, when deduplication is coupled with compression, overall data reduction ration remains about the same as the block size increases. This is because compression algorithms benefit from having more data in the block to work with.

Q: How can I achieve the best deduplication ratio?
A: Group similar VMs (such as VMs with the same operating system, or VMs made from the same template) in the same job. Have fewer jobs with more VMs in each, rather more jobs with fewer VMs in each.

Q: My VMs are not made from the same template. Will dedupe work between them?
A: Yes. Because deduplication is done on block level, it does not matter if VMs were made from the same template, or provisioned manually. Any similar blocks between VMs will be deduped, even if these VMs have different operating systems.

Q: Does deduplication work for replication, or for backup only?
A: No, because replicas are created in native format (uncompressed), deduplication is not applicable to them.

Q: Since Veeam has its own deduplication, does it make any sense to write Veeam backup files to storage device with hardware deduplication?
A: Yes, this way you will get global deduplication (between backup files produced by different backup jobs). Generally speaking, deduplicating storage devices are best choice for long-term archival of backup files produced by Veeam. However, not every deduplicating storage device is good as primary backup target, because unlike raw disks, these devices are not designed to provide good IOPS, and may become primary bottleneck for your backup performance, thus affecting your backup window. Likewise, poor random read I/O performance certain deduplicating storage devices are exhibiting may affect restore performance.

Q: Have you done integration testing with other vendor's deduplicating technology such as EMC DataDomain, HP StoreOnce, ExaGrid, etc?
A: Yes, we have partnerships with most deduplicating storage vendors. Moreover, v7 delivers noticeable integration improvements based on the tests we have conducted.

Q: Should I disable built-in deduplication it I am backing up to a deduplicating appliance?
A: No, we recommend that you keep it enabled for better results! You will get faster backups, and more portable backup files. However, consider disabling compression, because compression may affect deduplicating ratio significantly on these type of storage devices.

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Built-in WAN Acceleration

Post by Gostev » Nov 11, 2013 3:41 pm


Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Application-Aware Image Processing

Post by Gostev » Nov 11, 2013 3:41 pm

Q: What exactly do you mean by application-aware image processing?
A: Application-aware image processing is unique Veeam technology that allows creating image-level backups in application-aware manner. It is a multi-step process that consists of detecting applications running inside of the processed VM; using Microsoft VSS to perform application-level quiescence to ensure that each application state is transactionally consistent; applying application-specific settings to prepare each application to perform VSS-aware restore on the next VM startup; and finally performing transaction logs pruning for certain applications if backup was successful. The whole process is fully automated.

Q: Why application aware image processing functionality in Veeam is important? How is it better than VMware Tools VSS integration?
A: Microsoft VSS was not designed with image-level backup and restores in mind, but rather for file-level backup and restore process. For some applications, on top of basic VSS quiescence, additional steps need to be taken when backing up and restoring the VM image as a whole.

Q: Do I need to deploy persistent agent in every VM that I am backing up in order to be able to use application-aware image processing?
A: No, Veeam does not use persistent agents inside VMs. Instead, Veeam automatically deploys small runtime coordination process to each VM when backup starts, and removes it immediately after backup finishes. This frees you up from agents micromanagement (deployment, configuration, updates, monitoring, troubleshooting). Besides, actual VM runs without any 3rd party agents present most of the time.

Q: Does Veeam install its own VSS provider on each guest?
A: No, we leverage default VSS provider from Microsoft that is already available on each Windows guest.

Q: What is Microsoft VSS and how it can provide transaction consistency with image-level backups?
A: Please read the following beginners guide to Microsoft VSS: What is Windows VSS & why you should care

Q: What applications do you support for transaction-consistent backups?
A: Any VSS-aware application running on Windows XP/2003 or later. All modern server applications from Microsoft are VSS-aware, plus many 3rd party vendors ship their server application with VSS writers as well.

Q: How do I know if my application is VSS-aware?
A: It should implement VSS writer and have it installed and registered in Microsoft VSS framework. Open command prompt on backed up VM, and run vssadmin list writers for complete list of VSS-aware applications on specific system.

Q: Do you know if Oracle has VSS writer?
A: Yes, Oracle 11g has a component named "Oracle VSS Writer" that installs when selecting Windows OCI Components on the Oracle 11g database install wizard. It does support Oracle 10g starting from patchset

Veeam Software
Posts: 23199
Liked: 2963 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

File Level Recovery

Post by Gostev » Nov 11, 2013 3:44 pm


Q: Does file level recovery (FLR) require that backup file content is extracted and staged on disk or in RAM before recovery can take place?
A: No, file-level recovery happens directly from backup file, withour prior extraction.

Q: Do you have to backup VMs with guest file system indexing enabled to be able to do file level recovery?
A: No. Unlike with other solutions, with Veeam indexing is completely optional and is not a requirement for file level recovery. However, indexing enables you to additionally perform 1-Click File Restore through web UI (see below).

Q: How does native Windows file level recovery work?
A: Native Windows file level recovery mounts the content of backup file directly to backup server as folders. You can even point any applications to files located in these folders, and use them normally (backup file remains read-only no matter what you do).

Q: Can you restore files with correct permissions?
A: Yes, this option is now available.

Q: What file systems are supported for instant file-level recovery?
A: FAT, NTFS and ReFS.

Q: Are GPT disks supported?
A: Yes, starting version 6.1

Q: Are Windows dynamic disks supported?
A: Yes, starting version 6.5

Other OS

Q: How does multi-OS file level recovery work?
A: Because Windows cannot read other file systems natively, we invented a patent-pending approach that uses special FLR helper appliance that runs stripped down Linux (takes 10 sec to boot) yet smart enough to be able to read the data from as many as 17 file systems. Virtual disk files of VM you are restoring from are mounted to FLR helper appliance directly from backup file (without prior extraction).

Q: Can you restore files with correct permissions?
A: Yes, this option is now available in the multi-OS file-level restore wizard when restoring directly to a Linux host.

Q: What operating systems are supported for instant file-level recovery?
A: 17 most commonly used file systems from Windows, Linux, Solaris, BSD, Unix, Novell and Mac operating systems.

Q: Do you support instant file level recovery from NSS volumes on Novell?
A: Yes.

1-Click File Restore (web UI)

Q: I have 1-Click File Restore buttons (Restore and Download) disabled? Guest system indexing is enabled on all jobs.
A: This is premium functionality that is only available in the Enterprise Edition of our product. If you have Standard Edition, use instant file level restore wizards in the B&R console instead.

Q: How does 1-Click File Restore work?
A: Enterprise Manager web UI user picks one or more guest files to restore by browsing or searching guest file system index of the backed up VMs (indexing explained below). Enterprise Manager then creates a task on Backup server, and the Backup server restores the file using native file level restore capabilities (see above).

Q: Do I need to install any agents on the guest to be able to restore files to the original location?
A: No, 1-Click File restore is agentless.

Q: Do you have to backup VMs with guest file system indexing enabled in order to enable 1-Click File Restore?
A: Yes, 1-Click file restore requires that guest file system is indexed during the backup.

Q: Does the 1-Click File Restore process preserve the original file, or simply overwrite it?
A: Yes, the original file is preserved with the _original suffix.

Q: What if the original file is locked by some process, and cannot be renamed?
A: In this case, we restore the file with the _restored suffix, and log a warning no notify the restore operator.

Q: How do I make someone the File Restore Operator?
A: Using the Configuration page of the Enterprise Manager, grant user the corresponding role. The user will then be able to logon to the Enterprise Manager web UI. File Restore Operators can only see a subset of web UI (specifically, Files tab only).

Q: Does the File Restore Operator need to have permissions on restored file, guest, VM, or host to be able to perform the in-place restore?
A: No.

Q: Can I restrict File Restore Operators to be able to restore specific files only? Disable ability to download the restore files? Restrict them to the certain virtual machines only?
A: Yes, these settings are available in the Enterprise Manager configuration.

Q: In case of in-place restore (back to original location), do you preserve files permissions and ownership?
A: Yes.

Q: What are the system requirements for 1-Click File Restore?
A: Same as for Windows file level restore (see above), since both are using the same engine.

Q: Is 1-Click File Restore supported for OS other than Windows?
A: Same as for Windows file level restore (see above), since both are using the same engine.

Guest File System Indexing and Search

Q: Do I need to deploy any agents inside of each VM to be able to index guest file system?
A: No agents are required. All you need to do is select the corresponding check box in the backup job wizard, and specify the administrator's credentials to your VMs.

Q: Will turning on indexing slow down my backups significantly?
A: No. Instead of scanning through the whole file system (like some competitive solution do), we capture index data directly from NTFS MFT, as a part of guest OS freeze process. For a typical VM, the required data is captured and parsed nearly instantly, which is we are calling this Instant Indexing.

Q: Does the indexing functionality require more CPU power on the Veeam Backup server or Veeam Enterprise Manager server?
A: No, creating the “catalog” of all files inside the backed-up image is done by Veeam Backup servers, not by the Enterprise Manager server. Enterprise Manager only displays search results, whereas actual catalog indexing and search is offloaded by Microsoft Search Server (we support both Search Server 2008 and 2010). The Microsoft Search Server Express edition is free and is sufficient for smaller deployments.

Q: Is the Instant Indexing feature only available with Veeam Enterprise Manager?
A: You do not need Enterprise Manager to create the local catalog, but you have to install Enterprise Manager server to be able to browse and search for guest files in VM backups, and maintain global catalog across multiple backup servers. Also, please see the Standard vs. Enterprise Edition comparison document on product page under Resources tab for more information about slight differences in Instant Indexing feature set depending on your Veeam Backup license level.

Q: I have more than one Backup server. Will the guest file search show results across all Backup servers?
A: Yes, as long as all your Backup servers are federated in the Enterprise Manager.

Q: Where does the index database reside?
A: Local catalog is stored directly on the Veeam Backup server, in the location specified during setup. Global catalog (across all backup servers) is located on the Enterprise Manager server. Additionally, index is also stored in the backup file itself (and so it is immediately available for all imported backups).

Q: What do I need to backup to protect index database?
A: You need to backup Enterprise Manager server, since this is what holds global catalog (across all backup servers). Backing up local catalog data on Veeam Backup servers is not required, since any new index data that appears there is automatically (and incrementally) replicated to the global catalog.

Q: It looks like guest file index is missing some files?
A: By default, we do not index Windows system and temp folders to reduce the index size.

Microsoft Search Server Integration

Q: Is Microsoft Search Server required to browse or search guest file system catalog?
A: No, Microsoft Search Server is optional. Browsing functionality does not rely on Microsoft Search Server. Searching for files is also provided natively, however for performance consideration we recommend using Microsoft Search Server in cases when you need to perform searches across more than a few hundreds of indexed VMs.

Q: My guest file system catalog is too large, and a single Microsoft Search Server no longer scales.
A: Just add additional Microsoft Search Server, and Enterprise Manager will automatically load-balance global catalog between them.

Q: Is Microsoft Search Server 2010 better than Microsoft Search Server 2008?
A: Yes, it has a few times better capacity at a cost of increased system requirements. To significantly increase capacity of any version, upgrade to licensed version of Microsoft Search Server, and use licensed Microsoft SQL server for Microsoft Search Server backend database.

Q: Would you suggest putting the Microsoft Search Server on its own server? Is catalog crawl CPU intensive operation?
A: Yes. Catalog crawl is quite resource intensive task that can consume significant chunks of server CPU, thus affecting backup performance.

Q: I have fairly large environment, but want to stick with free Microsoft Search Server Express Edition, do you have any recommendations?
A: Index only those VMs you really need to index (for example, file servers only). Index only selected folders on your VMs (for example, only user home folders on your file servers). If you are still running out of capacity, just deploy additional Microsoft Search Servers.


Who is online

Users browsing this forum: Google [Bot] and 54 guests