Dear Experts, in case of disaster, such as viruses, ransomware,... if we only have NAS device remaining and it only includes the Veeam backup files (.vbm, vbk, .vib files) of Exchange server; can we recover it?

If we cannot recover the VM, how can we rebuild it from those backup files. Can you please suggest a plan? Many thanks.

Veeam 9.5; Exchange 2016, Server 2012R2

Hi

How to use Veeam Backup and Recovery 9.5 for archieving files?

We have one host and apx. 10 VMs (Linux and Windows Servers) and use successfully Veeam for backing up them to OnSite NAS (CIFS) and using copy job to the remote Site over Internet. The vCenter is used too here.

I was wondering how accidently deleted files and files which are seldom used but need to be archieved can be addressed using Veeam? Need to have them at the backup and potentially restore a accidently (or purpoced) deleted file from there after severl years. Even if the repositary is full we don't want that Veem discards/deletes those files.

Any basic steps/thoughts are highly appreciated.

Lastly, we have also Veem One license but won't necessarily use it. Maybe we don't really need it.

Thanks in advantage.

HUGE problem!  

We are in an ESX 6 environment.  I recently used Veeam to migrate a VM from one host to another.  I selected the option to delete the original VM upon successful migration.

So, once the migrated VM started, we noticed that there were some spanned drives in there and they are corrupt.  

I need to recover (undelete) the original VM on the data store from which it was migrated.

Questions is:  HOW do I run recovery software on the original datastore on the original ESX host to see if I can undelete the VMDK files that lived there?

Where do I install the recovery software?  How do I mount the datastore need some step-by-step help here.

Thanks

Cliff

Greetings,

Should I use Veeam for replicating an exchange server? They only have one and looks like they won't approve another for me to set up a DAG. We already use Veeam for backups. I have about 4 TB on one host in local disks since we just migrated the VMs off of it to their new SAN so I can replicate to those local disks. Just wasn't sure about replicating exchange and how to go about connecting clients to it, if they won't connect automatically after restarting outlook, should we need to failover to the replica.

Thanks

We are using ESXi 6.0 and we are running Windows VMs.  I used Veeam to migrate a VM over to a new host and it came up hosed.  The dynamic disks won't come back online.

On the problem VM, my disk shows as dynamic and my spanned volumes show failed.  Reactivating them isn't working.  I can't reactivate the disk or the volume.

Can anyone point me in the direction of how to fix this?

Before you ask, no, we don't have backups.  We lost the NAS for backups about three weeks ago and we have no replacement NAS yet.  So, I was going to split my VMs between two of my three hosts and replicate the VMs to the third host.  It's during the migration that the file server got hosed.

Anyone have a good fix for recovering the spanned disks?

Thanks

Cliff

PS:  My disks show as spanned, dynamic, failed.

Dear All


               How do i eject tape from Veeam ? i was trying to eject, but i can not select the "eject" button, any idea ?



Keith

Hi experts,

I am using Microsoft Azure, which comes with my Partner subscription. I am only using it to set up simple storage under the $100 monthly limit to use with Veeam. The problem is when I set up a simple storage, Veeam does not recognize it during its wizard. If I set up Azure to run the storage as a VM network, it does work with Veeam, but it is too costly, and it is complicated.

Basically, what I am saying is that I am rather clueless when it comes to working with Azure. I am not sure if I am able to contact Microsoft for support; that is doubtful. If someone understands my question, then possibly it can be done here. If not, I may need help one on one remotely to set Azure up properly.

Thanks.

OK Guys, a question about a topic i have no to none experience in...

i bought a second hand HP Storageworks MSL6000

this has 2 LTO 3 drives inside.

the vendor told me he connected the MSL6000 over IP to a windows system.

i see on the back a Fiber Connection and a Network Connection.

any idea how to get this working? i have a windows server 2016 running with Veeam BR installed and working.

i need to connect the MSL 6000 into windows so that Veeam van use this.

how to start?

Hi All, I want move a Hyper V VM Domain Controller(with all FSMO Roles) from one host to another host.

This is not a clustered environment, the VM DC is being backed up with Veeam, can I just restore the VM hdd to the new Host and fire it up or should I perform a Export/Import process?

I have read lots of articles that suggest this would be fine, but some say there may be replication problems, Unique ID issues etc.

I would appreciate any advice on this process

Thanks

Since upgrading to Veeam 9.5 Ive noticed I now have snapshots on two of my 4 servers which sit on the vCentre. Im down to 350gb on the main storage datastore and dont have any more space presently available. I never noticed these snapshots before on Veeam 8 but I may of not noticed but since upgrading to 9.5 a lot of space has disappeared from my datastore.

Is there a way the snapshots can be consolidated into the main vm files or do I have to provide more space?

Re: Imaging computers for bare metal backups.  I don't want to miss a bet regarding best practices.
So, I'm asking for comments on my beliefs and practices.
I'm trying to be as pedantic as possible in order to generate comments.  So some assertions are really, to me, DUH!  (You don't have to say "well, SURE!"     :-)
I'm currently targeting VEEAM Windows Free Agent as the tool.
There are no virtual machines.
There are no "families" of identical target hardware.

1) If it's going to be bare metal then that implies the OS drive could be empty and one has to provide a boot mechanism.

2) One has to have a boot mechanism, an image, and the image source has to be reachable by the booted recovery environment.

3) Remote access is out of the question.

4) If the computer is headless then this can complicate matters to provide HID access for the recovery environment.

5) The VEEAM backup process can keep up with changes.  So, if the objective is to back out from an OS upgrade, some selection in the recovery will be necessary.  (Assumes that using a Restore Point from within Windows isn't feasible).

6) Using VEEAM, it's necessary to have a unique boot drive.  How to avoid the uniqueness?

7) The unique boot drives have to be available or easily burned from backups.  (Which?)

8) If the unique boot drive isn't tested (including that the image file reachable) then you don't know what you have.

Some thoughts and questions:
The more computers handled by imaging, …

I'm trying to make good use of the VEEAM free imaging tool for bare metal backups.
I can get the image files OK but have a few questions about restore operations.

Assuming that I need to apply this to a number of computers (not too large a number) and that others may have to do the restorations, I'd like to save the files on a network share rather than, say, an external USB drive that can be made "local" when the time for restoration comes.
Clearly, one is going to want to test the restoration process and I'm willing to deal with variations in computers regarding "can this one boot from a USB or DVD?".

But, in the first test using a network drive, I couldn't get the VEEAM restore system to see any network shares.
This is in a workgroup environment with a number of file shares on the network.
I've already determined that the NIC driver seems to be present and have configured its settings after / during boot to match the workgroup subnet.
But that's as far as I can get.
Also, I'm not expecting name service so use file-sharing computer IP addresses such as:
\\10.10.10.33\[sharename]

I don't want to find a solution for a one-off computer.  I want to be able to do this over a range of different computers.

Suggestions?  I'd rather not give up on a network share as the image source.  But, if that's the conventional wisdom then I guess I'll have to more seriously consider just that.