Two Windows 10 64-bit OS computers are unable to backup to a QNAP TS-451 NAS while these laptops are connected to the Wi-Fi while running the free version of Veeam v.2 (see the screenshot).

However, these same two laptops are able to backup just fine while their Wi-Fi is disabled and they are plugged in with Ethernet cables on the same network.

What can be done to fix this issue so that these two laptops will be able to backup to the NAS while connected to the Wi-Fi and without being plugged in with network cables?

On a Windows 10 computer where I have just installed the free Veeam backup program and have set the program to backup to a local NAS I receive the error message "Skipping scheduled backup because battery level is too low" even though the laptop is fully charged and is plugged into power.

What can be done to fix this issue so I can backup the laptop?

I did a Veeam Exchange restore and exported the three pst files to the desktop.  I then copied the files to my computer so that I could open them in Outlook 2016.  Unfortunately I get an error message saying "File access is denied. You do not have the permission required to access the file Blah Blah.pst".  

I edited the files and added full permissions for myself and even the "Everyone" group but still get the same message, any ideas please?

i have a veeam Job which backup 6 vms(jobname= job1). Sudenly this Job not working any more , after that i cloned this Job (jobname= job1.clone) and work good at the Moment.
but still exist on the NAS storage , .vbk and vbr files. they are prox :900 gb .of Course i would like to use this space for job1.clone Job.

i changed restore Point under job1 and deleted part of vbk,and vrb. But still there is data which i cant delete manually.

Please help to delete These old files.

Thanks in advance

Hi Experts
I use Veeam 8.0 Free only Tape function and MS SQL express installed on the Windows 2012 R2 Server.
today i got error, related  SQL Server max 10Gb place.

is there a way i can solve this Problem.I reduced sometape Job which are not need any more.But not help.

error:SQL server is not available.
Could not allocate a new page for database 'VeeamBackup' because of insufficient disk space in filegroup 'PRIMARY'.
 Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
The statement has been terminated.

Hi experts,

I would say my technical level as far as servers is about a 5 to 6 out of 10. The IT person setting up the server would be a 12. He makes sure I have good quality hardware and software, but he also doesn't always recommend the most expensive. For this reason, he has no issues using WSB, but I don't want something that bare bones, no matter how well it works. Plus, I am more willing to spend money. As a physician, I see myself working another seven years (which I know is bordering on too long for the server -- I guess I am misguided by the fact my Dell Edge 2900 lasted that long).

Just to give my setup, I am setting up a Dell T430 server with Windows Server Standard 2016 as the host, with two VM guests. One will run my SQL databases and the other will contains Essentials for Active Directory and will be the DC. I have only eight clients all Lenovos running Win 7 Pro. They are all identical. Modem is Arris by Spectrum with 70 down and 6 up. pfSense router (awesome, but I am glad he set it up) and a Cisco 26 port switch. I know this is more info than you need. My old server (Dell Edge 2900) will temporarily be the fax server, but it can be converted to something else -- maybe a replication machine? I can also get Azure for the cloud much cheaper than AWS.

So, now to my question. And, these are frustrating I know, because it is more about opinion. I generally end up splitting the points as there is no right or wrong answer. But, I am trying to decide among …

Hi EE,

I am running a replication job, however, the job hangs at "Processing Configuration" for around 4 minutes then I get an error message indicating the replication job is not allowed in the current state.
 
Attached is a screenshot of the actions veeam ran.

Any help is appreciated
Capture.PNG

Hi Experts,

We are running nightly onsite backups for our server (DC + File Server) using Veeam, and I want to store an offsite copy of these backups on AWS. What AWS Service should i go for? Do you have any documentation or KBs i can refer to for setting this up?

Hi
Had a nice salesman on the phone, reckons arcserve is market leader in backup and better than backup exec and veeam.
Any professional vouch for this?  we still suing BE and veeam for tape and VM backups respectively, although thinking of migrating from BE to veeam for tape also..
Thanks

Hi,

I noticed my Veeam backups stopped working after we had a power cut/ups failure. When I powered back up the VM Server and then the windows guests all seemed well.

I was able to connect via my vsphere client on my laptop to connect to the VM Host and fire up the windows guest servers. When I try logon to the same vm host from my veeam server using the same vshpere client/root username.password I get An unknown error occurred, unable to connect to remote server.

What brought me to this point was when I was checking my veeam backups after the power cut, they hadnt backed up. The error message I get from veeam software on the veeam backup server was Your connection was actively refused. Its as if my VM Host will not take connections which come from my veeam backup server IP address ?

Any ideas
SycamoreIT

Hi All,

What’s the impact when taking the backup of Exchange Server (no DAG) with Veeam (VSS aware or Application-Aware Processing enabled) when the server is currently running on Circular logging and the mailbox is being migrated from one server to another ?
More info about the application aware: https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_vss_application_vm.html?ver=95 

The reason I ask this question is that the migration of the 2TB+ mailbox database is quite slow about 5 GB per hours, which is about 17 days with no backup running on the email server.

Any help and comments would be greatly appreciated.

Hi,

I've been using Veeam for years as a back/replication package.  I started getting an error a day or so ago that is rather odd.  

The first odd thing about it is the suffix:  vmdk.vmdk for both virtual disks.   Never seen this before.  Not sure if it was named that originally as I wouldn't normally check the suffix with a VM that has been running for years (and still is).

And as a production server, I haven't made any changes to the configuration at all.  The specific message is:

Processing configuration Error: Cannot replicate disk {LSI-1] ABS64/ABS64_1.vmdk.vmdk because its capacity was reduced.

The capacity of this drive is 60 gig and has been for years.  Any suggestions on how to diagnose this?

Running vSphere 6 essentials with current updates applied, and Veeam B&R 9.0.0.1715.

Thanks!

--Ben

Hi EE,

I've been getting this error on a Veeam backup for over 2 months now.  There is not a lot of information online, so maybe you guys can help me. This is the error that I am getting:

"Failed to prepare guest for hot backup. Error: Cannot upload guest agent's files to the administrative share [\\10.80.60.17\ADMIN$]. Cannot copy file. Source file: [C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamGuestIndexer.exe]. Target file: [\\10.80.60.17\ADMIN$\VeeamVssSupport\VeeamGuestIndexer.exe]. CopyFile() failed. Win32 error:The process cannot access the file because it is being used by another process. Code: 32
Error: Cannot upload guest agent's files to the administrative share [\\10.80.60.17\ADMIN$]. Cannot copy file. Source file: [C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamGuestIndexer.exe]. Target file: [\\10.80.60.17\ADMIN$\VeeamVssSupport\VeeamGuestIndexer.exe]. CopyFile() failed. Win32 error:The process cannot access the file because it is being used by another process. Code: 32"

Any help would be appreciated.