Discussions specific to the VMware vSphere hypervisor
Post Reply
Cia91
Lurker
Posts: 1
Liked: never
Joined: Mar 29, 2017 8:38 am
Contact:

New destination LUN maintaining name.

Post by Cia91 » Mar 29, 2017 8:51 am

Hi all,

we lost a storage during the weekend (Argon blast) and fortunately it was the storage used as destination for the Veeam Replication job.

We are now recreating the lost LUN and presenting them to the vsphere infrastructure. Of course we are recreating them with the same name as the old one, but i think Veeam will not recognize them as a Destination lun in the Replication job right?

How Veeam identify the LUN? By some sort of ID? I suppose i will have to manually modify every job and point it's destination to the new lun.

We are talking of about 150 job so a faster method will be appreciated if someone have ideas. :(

foggy
Veeam Software
Posts: 16932
Liked: 1377 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: New destination LUN maintaining name.

Post by foggy » Mar 29, 2017 1:21 pm

The LUN itself will be recognized, but since it does not contain replicas, after presenting the new LUN to vSphere, you would need to remove replicas from configuration in Veeam B&R for it to be able to continue jobs. The first jobs cycle after that will be perform full run.

Post Reply

Who is online

Users browsing this forum: No registered users and 31 guests