Veeam® has pioneered a new market of Availability for the Always-On Enterprise™ by helping organizations meet recovery time and point objectives (RTPO™) of less than 15 minutes for all applications and data. Veeam develops backup, disaster recovery and virtualization management software for VMware and Hyper-V virtual environments. The company focuses on products that help with virtualized workloads, reduce downtime, and ensure the system Availability required by service-level agreements.

Share tech news, updates, or what's on your mind.

Sign up to Post


we use veeam for our backup solution in the datacenter. We backup our Hyper-v hosts to a veeam backup and replication server. This server is located in the same datacenter. After this backup we use cloud connect to send the data to another location.

Last week someone told me that the cloud connect solution is not so good as if the original backup i take is corrupt then the cloud connect copy is also corrupt.

He told me that we need to setup a second backup and replication server and then take a second backup with that server.

when i told veeam about this they told me to use the sure backup option. we have the enterprise license and this is included they told.

what are your ideas over this? What to do to make sure we take correct backups.

as a reasonably inexperienced person with VMware, I have an issue with a VM. It is an SBS2011 server in production and the last few days there is an error in the event logs about the hard disk having a bad block. Since then our Veeam backups have failed with a CRC error. CHKDSK with no parameters (i.e. no attempt to fix anything) shows 8k in bad blocks.

I know chkdsk can be destructive to data, my worry is if I run it there is a very small possibility the VM will not boot afterwards - unlikely but that would be just me luck. To minimise downtime I was wondering if I could protect against this by taking a snapshot beforehand. If the VM gets broken by the chkdsk I could just revert to snapshot, would that be correct?

Thanks a lot.

Alasdair Barclay

I use to backup my Windows 2016 HyperV HV Server (2 VMs) with Veeam Backup and Replication on a Synology NAS repository

COnfig 1:
Windows Server 2016 HV:
- VM1:
- VM2:
NAS Synology

COnfig 2:
Windows Server 2016 HV: NIC1:, NIC2:
- VM1:
- VM2:
NAS SYnology:

COnfig 3:
Windows Server 2016 HV:
- VM1:
- VM2:
NAS Synology:

My concern is about security of data on the NAS which stores my backups (in the event of a CryptoLocker attack in particular)

- Which configuration is recommended for best practice?
- Is Config1 really unsecure and not recommended?
- Should config 3 works OK? The HV will have Internet access ? How?

Thank you for your comments and recommendations

The veam software is installed and configured to a vm. This vm backup the rest vm of the server.
I am planing (for test purpose at the moment)  to try to backup a desktop (for pc on the domain)
Firstly i would like to ask if is possible to use a trial for desktop(the VMare backuped with a paid version ) ?
Also how to configure the desktop (with out damage the existing configurations)
Hi Experts,

I have a question on achieving server recovery at DR site(to-be-propose) for a few Physical Server which includes Active Directory and on-Prem Exchange. If I plan to use Veeam Backup and Replication v9.5, would it be able to achieve the goal by doing critical recovery assuming the site failures on HQ? by doing Instant VM recovery. understand for active directory server will be good to deploy as additional DC at DR site but can Physical Exchange server be recovered as Instant VM recovery at DR site?
I am in the process of setting up my Veeam Backup & Replication backup job for my VMware environment.  I was thinking that it would be best to backup the entire cluster so that all VMs, including those created at a future date, would be backed up.  The issue that I have is that my vCenter Server Appliance (VCSA) is also within that cluster.  

According to Veeam knowledge base article kb2328, I should enable VMware Tools Quiescence and that the Application-Aware Processing and Guest File System Indexing setting is either disabled or excluded for the VCSA VM.  After reading some further information of the Veeam site, it seems that if I enale both VM Quiescence and Application-Aware processing at the job level then Veeam will first attempt to use application-aware processing.  If Veem is able to quesce all the VMs int eh job with application-aware processing then it will not use VMware Tools quiescence.  However, if some VMs cannot be quiesced with application-aware processing, or application-aware processing is disabled for some VMs in the job, the Veeam will use VMware Tools quiescence to prepare the VMs for backup.  

Due to the fact that I have a bunch of Windows VMs, including SQL Server and Exchange Server, I want to use the Application-Aware feature.  It's my interpretation that Veeam will use either Applicaton-Aware for all of the VMs or VMware Tools Quiescence for all of the VMs in the backup job.  If my interpretation is correct, I will need to setup two backup …
Hi Everyone

What is the best DR plan using 2 Readynas in a VMware/Veeam environment?

I have a VMware 6.5 box running 2 VM's.  I use veeam replication to replicate to a iSCSI datastore which in on a LUN on the Nas1 box.   On the Veeam Box I run a backup job to iSCSI connection to another LUN on the same nas1.  Also running on the Veeam box is Veeam Office365 which backs up to another LUN on the same nas1.

On the main nas1 I have 3 ReadyDR jobs which run to a second readynas of the same type.  I was looking at trying to replicate the LUN's from Nas1 to Nas2 but couldn't get the, to see each other.  I was initially using ReadyReplicate however this is not supported anymore by Netgear and I cant see the LUN's in ReadyReplicate any how.

My question is what is the best config?  What is the best DR plan if you have the following:

1 VMware box running 2 VM's with a iSCSI connection to a LUN on a Nas box
1 Workstation running Veeam Backup Up and Replication and Veeam Office365
2 x readynas 8TB


Dear Sir,

We had a Veeam Backup and Replication 8 and using MS SQL Server 10.50.2500 (Microsoft SQL Server Express Edition (64-bit) which is not compliance to company's policy. I had installed MS SQL Server 2014 with SP2 (12.0.5571) on another server.

Anyone have experienced how to migrate the VEEAM configure database from MS SQL Express to MS SQL Standard edition? How the VEEAM pointing to the new database server?Please help.

With regards,
I am re-building my Veeam serveur moving for 4.x to 9.5 and want to be sure and safe I'm doing the right thing,

A consultant put in place a few jobs but didn't seems that sure of the configs to put.
I want a full backup set out every friday and full on-site every nights (one to a NAS and one to a local USB drive)

My main job goes to a NAS.
As 20 restore points
"Configure secondary destinations for this job" is not check
It's a Incremental
"Enable application-aware processing" is checked
"Enable guest file indexing" is checked
runs daily

got a Weekly on F: drive
1 restore point
"Configure secondary destinations for this job" is not check
"Active full backup - Create active full backups periodically on Thursday"
This job I remove every Fridays and bring home and I rotate it using 8 hd
"Enable application-aware processing" is checked
"Enable guest file indexing" is not checked
Runs everyday at 8pm

And got a BackupCopy job called "backup on external drive"
Target is E: removable HD
31 restore points
Runs continuous

1- Is all configs efficient?
2- And is there anyway on the job "backup on external drive" I could bitlocker that drive when it is not in use.
I activated bitlocker but coudn't create a batch job that would decrypt before backup and re-crypt afterwards.

I have a laptop that is dead but I do have a Veeam full computer backup and I wanted to restore the volume from the old laptop to the new laptop (different hardware - one is a Latitude 5580 and the new is a 5590).  I did see this article and followed it, but it's a physical laptop, not a VM:

I used the recovery media from the new laptop and restored the C:\ volume from the backup - no errors in this process but when I boot the new laptop, Windows wants to try and do a repair (Preparing Automatic Repair) but can't.  I did have to use there "manual restore" option and map the C:\ since the volume info on the old laptop is most likely different from the volume info on the new.  Any ideas?  My guess is there's something wrong with the partition so it can't boot off of it.
Is there any free tool for backing up Exchange Online ?

For Veeam Backup for Microsoft Office 365, does it count for number of users on Exchange online ?

At present, we have 300mailbox with total size of 1TB. Which solution is suggested ? Will backup to premise is not possible in our case due to huge amount of data move through the network.

For Veeam Backup, can it backup by incremental ?


We have moved from BackupExec to Veeam and currently backup 10 x VM's and 5 physical servers.

Our backup repositories includes local disk, remote NAS and a robotic tape library.

I have been trying to work out the best practices for the requirement which is a follows.

Backups are Monday to Friday from 10pm.
Monday to Thursday are incremental, Friday are full backups.

We would like to store the backups on the local disk each night, copy incrementals to the NAS and over the weekend copy all of them to tape which is removed offsite and rotated each month.

If anyone has a suggestion on how to do this that would be great.
We presently have two UCS and EMC data domain systems.  One of them is in our colo and the other is our site.  We wanted to verify the pros/cons with going with either Avamar or Veeam or possibly another solution to replicate data and especially our virtual machines.  Our EMC data domain houses about 1 TB of data although our capacity is between 25 or 30 TB.  

Can someone offer some suggestions as well as alternatives to Avamar and Veeam?  Price will be a big concern as well.
Hello Board

We currently have an issue that i don't get resolved since 3 Weeks.

Physical Server
HPE DL380 Gen10 with 1x 2-port 10Gbe-HPE562SFP+ and 1x 2-port 10Gbe-HPE562FLRSFP+ attached via compatible HPE DAC Cable to a switch
OS: Windows Server 2016 Std
Software: Veeam Backup and Replication 9.5
Network Configuration: 1x LACP Windows-Team (1 Member of each networkcard-port) with management network, 1x LACP x LACP Windows-Team (1 Member of each networkcard-port) with storage network. All interfaces have jumboframes configured

Storage Array:
HPE Nimble Storage
Network Configuration: 2x 10Gbe Port with storage network configured

During backup the nimble array creates a storage snapshot of the volumes that have to be backuped. Veeam then copies the storage-snapshot-data to the local repository. During backup-copy from a particular storage-snapshot we do have a ton of the following windows events:
  • Target sent an iSCSI PDU with an invalid opcode. Dump data contains the entire iSCSI header. - Error - EventID 24
  • The initiator could not send an iSCSI PDU. Error status is given in the dump data. - Error - EventID 7
  • The initiator could not send an iSCSI PDU. Error status is given in the dump data. -Warning - Event ID 153 --> i assume this happens because of the iscsi lost

What have been done so far:

Checked Jumbo Frames
Ping …
Dear All

              i have a issue when trying to restore from tape from veeam, when i choose a restore point from backup tape, i received below "there is not enough space for backup files", any help would be appreciated, thanks


I have been tasked to go back through a large number of our backups over the last year and pull all the files into one large searchable repository. We are a  Windows shop and we use Veeam for our backup solution.

My current plan is to do a "File Level Recovery" in Veeam. The great side effect of doing a file level recover in Veeam is you have a GUI to pull out individual files if you need to but it also mounts all the backed up VM's drives to the local server you are performing the recover on so you are then able to use whatever tool you want that works directly with a Windows folder structure.

Given I can mount the backup copy drives to another server and search through them using standard file explorer tools I am interested to know if anyone has recommendations on a pro-grade tool that can scan the backup drives and the file repository I am building and then copy anything over from the backup that is not already in the repository. That would also include copying over the same file that is already in the repository but maybe a newer version of the file but also keeping a copy of the older version.

That is the main part I am struggling with is how to handle dealing with multiple copies of the same file but that has been modified. I need a way to either keep the modified copy in a similar folder structure but in root folder structure and just label the root with the date it was restored from or just put it in the same folder structure/directory and just automatically …
About two weeks ago three of our Veeam back up jobs began failing (they've run for a few years prior to this). We get a (503 Server Not Available) error. I am able to RDP to the computer. It has a working internet connection. When i go to the web browser address, though, i get the same 503 error (i'll attach screen grab). I've rebooted the computer and the host. That did not help. Nothing has changed in our DNS/Networking and we've been using the same firewirewall for years but these servers are located on the same network.

Vmware ESXi is version 6.0.0 for the host.

Not sure what other information i should provide.

Any suggestions would be great. Thank you.
Veeam backup fails to create a snapshot due to error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{e8796d4d-5afe-446a-9648-f0fb208162c1}]. Writer's state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f2].

Writers are all stable and have no errors
Server has been rebooted and dlls have been re-registered

Disk shadow verify command shows this result:

-> set verbose on
-> set context volatile
-> add volume C:
-> add volume \\?\Volume{53357368-6671-426e-9410-8289db3d0c8f}\
-> writer verify {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
-> writer verify {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
-> writer verify {0bada1de-01a9-4625-8278-69e735f39dd2}
-> writer verify {e8132975-6f93-4464-a53e-1050253ae220}
-> writer verify {be000cbe-11fe-4426-9c58-531aa6355fc4}
-> writer verify {8d5194e1-e455-434a-b2e5-51296cce67df}
-> writer verify {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
-> writer verify {6f5b15b5-da24-4d88-b737-63063e3a1f86}
-> writer verify {2707761b-2324-473d-88eb-eb007a359533}
-> writer verify {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
-> writer verify {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
-> writer verify {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
-> writer verify {afbab4a2-367d-4d15-a586-71dbb18f8485}
-> writer verify {542da469-d3e1-473c-9f4f-7847f01fc64f}
-> writer verify …
Veeam not connect to Vcenter - connection is being actively refused - portqry says 443 is not listening on Vcenter but netstat shows that 443 is listening
I am using esxi 6.7 and i created 3 vm. On one of these vm i installed veeam for bakup the other vm.
when i tried to connect the other vm (for backup) to veeam i get the error which i attached.

How to solve this problem?
Can any update me on server backup solution:

Which backup is solution is best to go with:
Veritas backup exec, Veeam Availability Suite and Rubrik.

We have VM server + physical server also.
I have a 2 VMS on Esxi using Veeam to backup on local NAS.
I would like to have replication onto 3 USB Drives for offsite purposes.
how would i accomplish the Backup Copy job using the rotated media, please advise.
Dear all,
its my first post on the forum and hopefully i am posting on the right place.

On our Productions we have 3 ESXI 6.5.0 Update 1 (Build 6765664)
ESXI02 .
ESXI03 .
VEEAM1 server on ESXI02
VEEAM 2 Server on ESXI 03
We backup VMS are on ESXI01 on VEEAM ESXI02.
restore to ESXI01 from VEEAM1 works fine
Restore to ESXI03 from VEEAM1 is working fine
Restore to ESXI01 from from VEEAM 2 works fine,
Now we want to restore to ESXI02 using the VEEAM1 which is hosted on the ESXI02 its keeps erroring out.
11/1/2017 12:28:41 AM Error    Restore job failed Error: Failed to open VDDK disk [[SSD] PC001/PC01_0.vmdk] ( is read-only mode - [false] )
                               Logon attempt with parameters [VC/ESX: [];Port: 902;Login: [root];VMX Spec: [moref=4];Snapshot mor: [4-snapshot-2];Transports: [nbd];Read Only: [false]] failed because of the following errors:
                               Failed to open disk for write.
                               Failed to download disk.
                               Agent failed to process method {DataTransfer.SyncDisk}.
We have Contact VEEAM about this error but the issue appear to be a host configuration issue.
Can someone please point me to the right directions to get this fixed?






Veeam® has pioneered a new market of Availability for the Always-On Enterprise™ by helping organizations meet recovery time and point objectives (RTPO™) of less than 15 minutes for all applications and data. Veeam develops backup, disaster recovery and virtualization management software for VMware and Hyper-V virtual environments. The company focuses on products that help with virtualized workloads, reduce downtime, and ensure the system Availability required by service-level agreements.