Veeam

560

Solutions

548

Contributors

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

I'm on esxi 5.5, vSphere 6.5. Something happened where a VM got stuck removing snapshot after a Veeam backup and been running for over 72 hours. We saw no file size changes on files in the VM folder on the host so we restarted management agent on the host.
After the host rebooted, this VM became invalid/inaccessible (it alternates between those two states continuously).
I removed it from Inventory and am not sure how to add it back. When I browse to the datastore and try to right-click the vmx file, the only options I see are Download, delete, copy, move, rename...
0
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

 

 
1
2
3
4
0
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 …
1
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.
VsphereError.PNG
0
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 …
0
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
0
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?
Veam_Problem.png
0
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.
0
I had this question after viewing VM - Virtual machine disks consolidation needed.

Hey everyone (ok mostly Andrew, haha).  I've recently come onboard at my current company as their IT Manager and have never once seen Disk Consolidation is needed in my 12+ years as an IT Professional...until now.  

Due to some very poor decisions by the previous IT Manager, we have a VM that has been locking up during Veeam 12-hour backups as the utility attempts to delete the snapshot it created for the backup.  I've been on the phone with VMware a total of 7-8 hours trying to figure out the issue and they finally isolated it to a couple of rogue snapshot vmdk files that were never removed (dating back to October of last year).  

Below are the details, with some modifications to file names and such to protect our identity.  :)
VMware thinks the main issue is the "713.4G Oct 18 20:44 ProblemVM-000001-sesparse.vmdk" on the first datastore listed below.  They said it appears someone manually diverted the delta file so it could not be written to the base disk.

VMware ESXi 6.5.0 build-4564106
VMware ESXi 6.5.0 GA

VM : ProblemVM.domain.com

[CML Datastore 02] ProblemVM.domain.com/ProblemVM.domain.com.vmdk   - 558GB
[Host VMData] ProblemVM.domain.com_1-000001.vmdk                - 3.2TB
[CML Datastore 07_ProblemVM] ProblemVM/ProblemVM-000008.vmdk           - 3.8TB…
0
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.
0
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)
ESXI01.  10.10.40.10
ESXI02 .  10.10.40.11
ESXI03 .  10.10.40.12
 
VEEAM 1  10.10.40.13
VEEAM 2 10.10.40.14
 
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: [10.10.40.11];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?
0
I have veeam standard running in one location wich produces monthly backups. Instead of transporting the backup device backwards & forwards I want to be able to use Veeam backup copy.
I have installed a trial of VEEAM enterprise on a server in my office
setup WAN accelerators for local &the remote office (running standard)
I can import backups from the remote repository into the enterprise version
But I cannot get a backup copy job to run...
if I select the virtual machine from the infrastructure - all I get is no restore points. I have left it running continuously  & with the monthly backup finishing it still said no restore points
Enterprise does not pickup the VM from the imported backups
There is no local backup job to import it from as the backups are run on the standard version in the remote office.

All I want to do is copy the monthly backup from one office to another using the WAN accelerators as we have very constrained bandwidth in one location
0

Veeam

560

Solutions

548

Contributors

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.