VM Restore using nbd, instead of direct SAN

VMware specific discussions

VM Restore using nbd, instead of direct SAN

Veeam Logoby ferrus » Thu Dec 03, 2015 3:57 pm

Hi

We have a new Veeam 8 installation, with multiple physical proxies. Each proxy has several TBs of local storage, and each is FC attached to the SAN source repositories.

We've just tried a full VM restore, and while it worked successfully - it chose a different proxy to the one where the files are located, and dropped down to network mode.
The messages in the restore log are:

03/12/2015 15:00:06 No available proxies are running on ESX(i) management interface subnet. Using proxies from a different subnet, performance may be impacted.
03/12/2015 15:00:11 Using source proxy 'incorrectproxyserver' [nbd]


We haven't - yet, set up a vmkernel NIC on the Veeam subnet, for Instant Restore/SureBackup etc. But I didn't think this was a requirement for traditional restores?
I've had a quick search and I thought that thick disks were the only requirement for Direct SAN restores.
ferrus
Veeam ProPartner
 
Posts: 127
Liked: 20 times
Joined: Thu Dec 03, 2015 3:41 pm
Location: UK

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby Shestakov » Thu Dec 03, 2015 4:56 pm

Hi ferrus,
Yes the thick disks is one of the requirements, besides the proxy must have write access to LUNs where VM disks are located.
What about backup, when you perform it, is the proxy used? What version of vSphere are you at?
Thanks!
Shestakov
Veeam Software
 
Posts: 4856
Liked: 395 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby ferrus » Thu Dec 03, 2015 5:07 pm

Direct SAN is used during the backups, and we're on ESX 5.1
Might be a good point about the RW access. I read that Veeam automatically prevented write access to the LUNs to stop accidental damage, but our storage admin might have presented them RO as well.
ferrus
Veeam ProPartner
 
Posts: 127
Liked: 20 times
Joined: Thu Dec 03, 2015 3:41 pm
Location: UK

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby Shestakov » Thu Dec 03, 2015 5:15 pm

Yeah, it worth checking if the proxy has the write access.
Also note that for ESX 5.1 restore of IDE disks in the Direct SAN Access mode is not supported.
I would also recommend reading VMware article about transport modes.
Thanks
Shestakov
Veeam Software
 
Posts: 4856
Liked: 395 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby skrause » Thu Dec 03, 2015 6:48 pm

ferrus wrote:Direct SAN is used during the backups, and we're on ESX 5.1
Might be a good point about the RW access. I read that Veeam automatically prevented write access to the LUNs to stop accidental damage, but our storage admin might have presented them RO as well.


Veeam doesn't automatically make the LUNs read only, it does stop them from being auto-mounted and potentially being formatted accidentally though.

You have to do some work in DISKPART to get a LUN to be read only (thus why we never really went to direct SAN for our setup, the running of commands in DISKPART to keep my production storage from being wiped made me nervous).
Steve Krause
Veeam Certified Architect
skrause
Expert
 
Posts: 296
Liked: 45 times
Joined: Mon Dec 08, 2014 2:58 pm
Full Name: Steve Krause

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby ferrus » Wed Dec 09, 2015 11:30 am 3 people like this post

Just a quick update, I've managed to workaround the issue.
The disks were presented RW, the VMs satisfied all the requirements - the issue appears to be entirely down to the incorrect proxy selection.

In the Restore VM wizard, if the correct proxy is manually selected rather than left to Auto-detect - Direct SAN mode is used.
Thanks for all the replies.
ferrus
Veeam ProPartner
 
Posts: 127
Liked: 20 times
Joined: Thu Dec 03, 2015 3:41 pm
Location: UK

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby btridon » Wed Dec 23, 2015 9:21 am 1 person likes this post

Hello ferrus,

i've encountered the same issue few months ago.
I want just to add some tricks that I found for this same case.

So, we used the Direct-SAN mode to backup and we wanted to use it for the recovery part.
We all know now that mounted LUN on Microsoft Server are in RO but we didn't want to put any LUN online (because of some people in our company who are very curious)

So this is the trick (and it's work) :

In a Server 2008 OS

Run CMD in admin mode and type :
1.diskpart
2.list disk (check the windows disk ID of the RO LUN)
3.select disk n (n is the windows disk id)
4.attrib disk (check the read-only state of the disk)
This will show the attributes disk. If the disk is set to Read Only we will be unable to write data to it. Run the commands below to remove the read only attributes and allow us to write to the disk
5.ATTRIBUTES DISK CLEAR READONLY
6.attrib disk (check again the new read-only state of the disk, see the difference)

With this tricks, LUN are always offline in the disk management window and VMFS datastores are always in the same state.
The only difference, and the great one that it's now possible to write on it (D-SAN restore is possible now!)

For suspicious person, you could try it on a test's VMFS Lun.

With Server 2012 and higher
Open the Powershell console in admin mode and type :
2.Get-disk (list disk)
3.Set-disk "Windows disk id" -IsReadOnly $False (the same that before with CMD : ATTRIBUTES DISK CLEAR READONLY)

It does the same that before.

I hope it will be interesting for someone.

Have a good day ! :D
btridon
Veeam ProPartner
 
Posts: 7
Liked: 1 time
Joined: Mon Oct 26, 2015 10:39 am
Location: FRANCE
Full Name: Benjamin T.

[MERGED]: DirectSAN thinking...

Veeam Logoby Buh95 » Wed Dec 23, 2015 10:05 am

Hi all,

Just want to share a subject with you, about DirectSAN configuration, and precisely about the way to protect VMFS Datastores that are presented (zoned and mapped) to a physical Veeam Server.

Two months ago, we’ve put in production a new Veeam server (V8u3) :
- Physical Dell Server with his own SAS local storage as repository
- Only one Veeam Proxy : the Veeam server itself
- The Veeam Server is “FC attached” to our Production SAN, to be able to backup VM using DirectSAN access.

No real problems at the end to put the infrastructure in place (thanks Veeam for simplicity…).
And no regret, DirectSAN access performance is here…
… Until we decided to test Full VM restoration:

As you may know, when you enable DirectSAN access on your physical Veeam proxy server, default behavior for full restauration is to use DirectSAN access too : When the restauration process begins, proxy is setup for DirectSAN, Datastore are connected, so let’go…

But by default, Your Veeam installer have set the Windows Server SAN policy to “Offline Shared”, so all your connected datastore are, by default and by design, not initialized, and so in Read Only mode.

At this point, any attempt to restore a VM via DirectSAN will failed with a pretty “VDDK Error 16000” (I.e. unable to write to your datastore).
So what… if we want to take advantage of DirectSAN for restauration, we have to put our datastores in Write access mode… but HOW ? What is the best way to do that ? I can say, after looking for a while, that any instruction about this is not clearly mentioned by Veeam documentation (and support confess me this after some rich discussions).

As far as I know, you have those options:

- You decide to give up DirectSAN access for restore operation. But even if you configure your proxy to failover to network (NBD) mode, this failover does not occur if the datastore is write protected (perhaps any new features about this in V9…). To use network mode, the only way is to install another Veeam proxy server and force this proxy to act as end point for sending data to your vCenter, not a really “sexy” solution…

- Initialize each disk/datastore from the Veeam Server point of view (Right-Click -> Initialize, from your Veeam server Disk Management Console). In theory, this not as risk (I’ll let you read the excellent article about this http://rickardnobel.se/vmfs-exposed-to-windows-san-policy/ ). Until, one of your colleague decides to work in the disk management console for any reason, and make THE mistake that he shouldn’t have done (delete volume on datastore for example). VMFS header corrupted and so on… Several dozen of VMs lost, Not really reassuring…

- The option that we choose : by default, we were all agree that letting datastores in read only mode was the best solution to protect our production VMware infra. So we’ve scripted, with Powershell, a way to simply put the concerned datastore in write mode using the SET-DISK command let. Example : you want to restore a full VM in the datastore that is viewed by you Veeam server as disk number 6, you pass this command before restoring :

* Set-Disk 6 –isreadonly $false
After restore operation, you rollback your datastore in read only mode :
* Set-Disk 6 –isreadonly $true

I don’t know if there is another solution… and I’m curious having your experience of this DirectSAN feature in production.

I think that Veeam should manage this datastore access layer automatically in the job (really simple in powershell). It would be the easiest and the most secured way of using DirectSAN access. But today, it’s not the case and I hope V9 will be the one…
Buh95
Influencer
 
Posts: 14
Liked: 3 times
Joined: Tue Nov 17, 2015 1:31 pm
Full Name: H.Schema.

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby PTide » Wed Dec 23, 2015 10:09 am

Hi,

Thank you for your feedback!

(and support confess me this after some rich discussions)
Could you please post your case ID?

Thank you.
PTide
Veeam Software
 
Posts: 3019
Liked: 246 times
Joined: Tue May 19, 2015 1:46 pm

Re: [MERGED]: DirectSAN thinking...

Veeam Logoby foggy » Wed Dec 23, 2015 3:24 pm

Buh95 wrote:- Initialize each disk/datastore from the Veeam Server point of view (Right-Click -> Initialize, from your Veeam server Disk Management Console). In theory, this not as risk (I’ll let you read the excellent article about this http://rickardnobel.se/vmfs-exposed-to-windows-san-policy/ ).

I guess you meant bring the LUN online, but not initialize it (at least, this is what the article is talking about).
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby ferrus » Wed Dec 23, 2015 3:51 pm 1 person likes this post

Or you could just leave it presented RW, safe in the knowledge that when the rogue sysadmin wipes the disk - you can be back online in no time, thanks to your safe & reliable Veeam backups!! :wink: :lol:

I want a Veeam pen for that ...
ferrus
Veeam ProPartner
 
Posts: 127
Liked: 20 times
Joined: Thu Dec 03, 2015 3:41 pm
Location: UK

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby ferrus » Wed Dec 23, 2015 3:53 pm

Seriously though, are we unusual in having our disks presented RW?
ferrus
Veeam ProPartner
 
Posts: 127
Liked: 20 times
Joined: Thu Dec 03, 2015 3:41 pm
Location: UK

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby PTide » Thu Dec 24, 2015 9:31 am

are we unusual in having our disks presented RW?
Placing disks in RW is OK but only for restore purposes - one should not keep them RW all the time, especially if some rouge-admin is around. Here is the example that some people definetily put disks in RW mode.
PTide
Veeam Software
 
Posts: 3019
Liked: 246 times
Joined: Tue May 19, 2015 1:46 pm

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby Buh95 » Mon Dec 28, 2015 7:26 am

Case ID : 1081850

Foggy : yes, you're right, it's "bring online" and not "initialize".
Buh95
Influencer
 
Posts: 14
Liked: 3 times
Joined: Tue Nov 17, 2015 1:31 pm
Full Name: H.Schema.

Re: VM Restore using nbd, instead of direct SAN

Veeam Logoby foggy » Mon Dec 28, 2015 4:02 pm

Veeam B&R should switch the LUN to write mode during restore, so I recommend contacting support if this does not occur and you have to do this manually.
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Next

Return to VMware vSphere



Who is online

Users browsing this forum: vishalgupta and 12 guests