Refs iscsi veeam. Not a support forum! Skip to content.

Refs iscsi veeam It’s formatted with ReFS too (64k blocksize) and it runs flawlessly. Your REFS problems with Veeam will be on Veeam server VM. I have a Windows Server 2019 Server, and I initally mounted the iSCSI connector, and let MABS format the volume as ReFS as a datastore for MABS. Our implementation consists of 3 backup repositories with ReFS, all with 64K blocksize. I learned the hard way how ReFS upgrades between Windows versions. This drive is set in Veeam as Repository for Copy Job to take advantage of Fast Clone feature etc. During a recent discussion with someone at Veeam, they mentioned that we should change the way we use our QNAP NAS boxes to ReFS by presenting them as iSCSI. Another solution could be to use Linux as a repo formatted XFS, which gives not only the What is the best approach and what do I need to be aware of when moving a ReFS repository to a new Veeam Server (and not ending up with a RAW volume)? Would it Following the design workshop with our Veeam solution engineer, we redesigned our repositories to be plain ReFS volumes with Veeam’s in-built data reduction. (DSR) location. It seems Veeam, iSCSI and 10GB aren't the best friends I hope this solutions may help someone with similar problems. ReFS 2019 vs. 15 posts tsightler wrote: ↑ Wed Mar 18, 2020 3:08 am There's no issue with this. Best of luck. In many situations, the backing storage is either, in a virtual environment, a Synology NAS (there may be a QNAP or two According MS the update will fix the issue but you have to format the disk again with REFS. UseUnbufferedAccess, DisableHtAsyncIo and V11a. We have two dedicated iscsi vlans with non routable ip ranges. I've not done much other than the basic with Veeam but like I said we're a really vanilla shop we don't do anything super clever. As far as I can tell, we'll need a Windows server that connects to the iSCSI and formats it as ReFS. I have truenas core with ZFS setup in various locations. 523 In many small environments that are already using some kind of Ethernet based storage, an iSCSI volume presented to the Veeam server in a VM, and formatted using ReFS is a common configuration. In fact, you do not need REFS Since VEEAM 9. The backups stopped getting corrupted, our backup SANs reduced down to hundreds of IOPS and were even able to do proper data progression again for the first Veeam Community discussions and solutions for: Windows 2019, large REFS and deletes of Veeam Backup & Replication . Currently I’m testing iSCSI on main site. Or change synthentic full to active full if you don‘t have the space to create an iscsi LUN. You shouldn't be surprised if the ReFS file system becomes corrupt when the NAS looses power or network suddenly. I have installed a windows 2019 server with veeam 12 and mounted qnap iscsi lun on win2019 formatted as refs. ReFS is not supported on SAN-attached storage. Now we have two different options to connect the iSCSI LUN to the infrastructure: 1. Since then we have seen few gotchas (recently resolved by Microsoft with the latest March 2017 patches) and we'll talk about that as well and few Just a quick post; the latest Windows Server updates for 2012R2, 2019 and 2022 (haven’t seen 2016) can cause ReFS issues. Topology is as below. My estimation is that with the latter you still can leverage advanced ReFS integration because the repository is hosted on Windows Server 2016, however i not sure if my estimation is correct perhaps someone from Veeam can shed some [UPDATE] This recommendation is still valid in 2021. Veeam cannot connect to iscsi luns itself. of course active fulls are ok but 1. Backup to Tape job around same thoughput. What would be nice, is a way to verify what Veeam is configured with on a Refs repository, 4Kb or 64Kb cluster size, and what the ReFS volume is currently running as cluster size. Background configuration is that they are using in both their primary and secondary datacenters a Synology NAS that is connected to their Windows Repo server as an RDM disk presented via ISCSI to their ESXI hosts, volume is formatted REFS, 64k blocks, the usual. 2 posts • Page 1 of 1. But I’m also thick provisioning and it has more space than it needs. Ajout d’une seconde carte réseau au serveur Veeam pour l’accès ISCSI aux LUN. I know by default Microsoft has chosen to leave trim disabled on ReFS v2 volumes. Before the accident, from the QNAP side, the network setup was an Veeam will run its data mover service on the server and you will get good performance. After upgrade, such backup repositories will work as backup This question is both related to Vmware and Veeam best practice, but let's try it here. FAQ; Main. from this time i not using ReFS on 2012R2,2016,2019. Users can also use SMB to mount the volume to the backup server directly. Search. Post by HannesK » We only use the Synology NAS as a host for block volumes (iSCSI). From the user perspective the obvious differences are Windows vs Linux, and the fact that ReFS From Windows Server 2016 it is recommended to use REFS. 2 ReFS partition on it, one of them is the biggest one 60 TB connected using ISCSI. iSCSI with REFS is likely unsupported because these boxes are usually not on the Windows Server Hardware compatibility list. With this integration between the two product, users can now design a repository that combines the speed of a non-deduplicated array, with some important space savings that usually belongs to those dedicated appliances. I agree with gentlemen, that you should go with Hardened Immutable Repo for Veeam with xfs. Unfortunately for smaller location, i do not have server its not possible to have server due to budget constraint and only fewer number of people working in that location. The NAS is used only for copy backup jobs from Veeam and is only connected to that server. Let me know this topology is ok and is the Veea If you do no know much about Hardened Repository in Veeam VBR v11, read here to learn more about:I was asked, if a hardened repository can be a extent of a Scale Out Repository (SOBR). Old server was 2022, everything was RGijsen wrote: ↑ Mon Jan 07, 2019 1:37 pm I don't see how you'd want Veeam to improve that; a side effect of either deduplication or ReFS Blockcloning is that files that would have been sequential, now are spread out over your physical disks. Old server was 2022, everything was working. Veeam Community discussions and solutions for: How to provision a 1,5 PB ReFS Repo in 2024? of Veeam Backup & Replication. On top of it I use ReFs as filesystem and this disk is configured as Backup repository within a SOBR. Veeam will run its data mover service on the server iSCSI allows you to use a Windows repository with ReFS which leverages FastClone. How would Veeam Community discussions and solutions for: REFS issues (server lockups, high CPU, high RAM) of Veeam Backup & Replication Veeam Community discussions and solutions for: Considering REFS for a small deployment, advice needed of Veeam Backup & Replication . It's a fairly With NTFS, we improved the stability and sustained backup performance a zillion times over ReFS (we now do about 300MB/sec opposed to 10 with ReFS). We avoid using SMB and have never tried the old "Linux Server over SSH" trick. ) These gains are only possible if we I did a fresh Veeam VM install with 2025, installed also 12. We present to it via iSCSI a volume from our Nimble Array, formatted ReFS, and use it as a backup target for Veeam. Now, it's true that the iSCSI thing said above is definitely a don't do that, but by reading around I see many complaints about ReFS reliability, in particular when used with veeam and iSCSI. However, iSCSI will work with MTU 1500, but the most performance would be to use it with MTU 9000. The only information is that it's not supported. Is it still worth using the old but rock solid NTFS? ReFS and Veeam Really Saved Us 10 Terabytes of Disk Space. 5 was about the new advanced ReFS integration, which I’ll cover in this post as it is a significant technology for Veeam. Veeam backups compressed, writing to backup repo, processing rates around 275MB/s. I am trying ReFS to avoid ReFS, if possible. Besides that, those updates can iSCSI allows you to use a Windows repository with ReFS which leverages FastClone. 1. Guide for deploying TrueNAS systems as a Veeam backup solution. Comprehensive data protection for all Please note that currently we are using 77 Veeam servers (with QNAPs). what i now will do is. The virtual Veeam Backup server uses a local installed MSSQL 2016 as staging server. ### ReFS is only good for any method that synthesizes VBKs. It was done by my colleagues. (Here is a good article explaining ReFS vs NTFS for backup. Okay! We will configure using the default, because to use MTU 9000 I need to make an infrastructure change. There is a posting by Anton Gostev in the Veeam Forum, which clarifies the matter. ReFS does not support SAN There are reasons to choose NTFS, and others for REFS. The service provider side storage is made up of multiple physical servers dedicated as repositories running Server 2019 (patched, AV exclusions, and registry optimizations, basically every suggestion we have found here) hosting 3x50TB in my backup environment I have an ISCSI Target mounted on a physical Host (Windows). NFS now has some issues too according to antons newsletter. The repository was on the SAN iSCSI 10 GbE and the volume was “RAW”. Normally there are no issues with it. I'll like to reinstall that server and add the repositories (volumes with REFS) to a new Veeam server. Archive. This is done over a 10Gbe network, the Windows box has a Edimax EN-9320TX-E and the Synology has their official 10Gbe card installed, all connected to a Netgear XS708T switch and link speed showing as 10G across the board. Comprehensive data protection I recently lost a ReFS volume on a NAS (QNAP TS-832PXU), connected to a Windows 2019 server through iSCSI. End result is that our backup and management layer costs Hi guys. exe command (separate from main Veeam tools but provided by them) and this also [For releases prior to 4] For data recovery, the target ESXi host initiator must be manually connected to the storage iSCSI target. It was created for those rare situations where a ReFS-backed repository is in use, and a user does not want Veeam Backup & Replication to use Fast Clone at all. That's not the case with NFS so you would lose potential ReFS benefits. If all the data currently living on the fast-clone supported ReFS "rehydrates", the XFS-based repository will be quickly overwhelmed given how many fast clone copies exist in the ReFS repo. One of the biggest advantages is ‘Fast Cloning Technology’ which enables synthetic full backups One of the key technologies of 9. With a ReFS repository in place, mind the following: Latest Windows updates are installed on the repository server. Running on small devices like NAS with iSCSI mapping to windows os, and big repos with serverhardware and 100TB+ with local storage or SAN attached storage. Does someone of you have an idea how I can do this? My idea was the In our case - there is Veeam Server running on Windows 2016 which has iSCSI Disk attached directly to the System and formatted as 4TB with ReFS 64K. SISR4 Chapitre 14 - Page 24 Configuration de la connexion iSCSI : programme Initiateur iSCSI . Do you wish to learn more about why the Storage LUN Better is better than a Mapped Network Drive etc. This allows the disks to be either be reattached to a VM in a new Option 1: Setup the NAS as an ISCSI device and direct connect from the VBR repo server to the NAS as an ISCSI volume. Veeam backups un-compressed, writing to backup repo, processing rates around About ReFS, i once asked QNAP Support if it is fine to Format a iSCSI Lun from QNAP NAS with ReFS. You can do ReFS on a block volume presented through iSCSI from a Synology NAS to a Windows Server. I would suggest to keep it “as simple as possible” If the workstations ReFS is unlikely to be the problem on its own (I don't think it's Synology either), it's Veeam's recommended filesystem for Windows based repositories and does have some other enterprise application use cases these days such as Citrix PVS and If you had mounted it to a server using iSCSI and formatted the drive with ReFS, then I would say stick to synthetic fulls because ReFS supports fast clone and you could offload almost all load to the backup storage via the file system. The change was night and day. Get a Quote (408) 943-4100 and can connect to a variety of storage systems. I tried the one tool out there that ReFS allows to use the Veeam Fast Clone feature which allows very fast synthetic operations for full backups and merges. This paper series will provide an overview of Do not use ReFS with iSCSI or FC SANs unless explicitly supported by the hardware vendor. Product Management Analyst @ Veeam Software. maybe on WS2022 the support is better. I created Synology LUN and connected it to the VBR server via iSCSI with ReFS and configured Synthetical Full because of the FastClone option. Also the ReFS piece too. I have a QNAP TES-1885U enterprise NAS that I wanted to use (completely) as Veeam repository for backup, the NAS have a single RAID array of 75 TB capacity. Connect the iSCSI LUN directly into a virtual windows server. It will add local immutability to your backup infrastructure. 5 U3a i create all my primary backup target repos with ReFS/64k on Windows Server 2016. I want to offload all of the backups to a iscsi disk and I don't have enough space for all the files without block clone. Thanks to Veeam's Would VEEAM know to "wait" for ReFS to finish with dedupe and compress before adding more files? Other tips to migrate are also welcome. Well, today also XFS with block cloning. The ReFS allocation unit size is 64 KB. The other one is 15 TB mounted through the datastore of VMWare vsphere cluster of 3 ESXi hosts. I am using ReFS with iSCSI drive attached to windows server 2016\2019 and performance is superb. Win2016 ReFs repository server freeze during Back-up copy. Possible explanations Issue with iSCSI and ReFS. In addition I must say that my Veaam is placed on win server 2019, not 2016. 334 Veeam Roles installed : Backup Repository, backup gateway, backup proxy REFS version 3. SISR4 Chapitre 14 - Someone, who probably wants to be anonymous, made a mistake when we originally set up our backup repositories We use ReFS, and the block size was set to 4K, which is the default, while the recommended block size is 64K. Which means random IO for your disks. This is because iSCSI LUN is connected directly to the Veeam server (no additional data transformation layers like VMDK). 0. Veeam Backup for Microsoft 365 (VB365) stores backup data in a Microsoft Jet database . We also are using Veeam agent to Backup Virtual machine with ISCSI connection. Virtualization station severely limits the CPU and RAM resources you can use unless you go for a really expensive unit. 5 or an earlier version. The change was night and Best practice: the Veeam server should be installed inside a VM. Our issue comes with Thin provisionned iSCSI LUN of 50 TB Networks Flat network Jumbo frames on every devices. In general, for our NAS backup NTFS or ReFS makes no difference. Do you wish to learn more about why the Storage LUN Better is better than a It is recommend that the repository VM either uses directly mounted iSCSI, or as RDMs in Physical access mode. R&D Forums. Power failure is one thing. As this means random I/O on the used storage a high IOPS and bandwidth storage is preferred. ReFS supported configurations must use Windows Server Catalog certified hardware. If you don't join the There are multiple possibilities for getting a corrupted refs Partition. On the QNAP, I have created a RAID6 and a LUN with a 512B sector. The rest of the servers remain on the backup ReFS repository. While using NTFS or using a SMB share, your virtual full back-ups will always take Soho nas is not recommended as a veeam repository. Hello, We are looking to move from virtual Veeam servers to a capable physical one. Can I: Connect the iSCSI target directly to our ESXi host and add it as a datastore. They confirmed it is ok. Main reason initially was due to lack of stability I saw quite often in its early days. Synthetic full backup takes 17 hours, daily backup is 1 TB. As veeam support suggested, i stopped all veeam services, reconnected iSCSI The main consideration here is whether or not you want to use ReFS, assuming the Windows server used for the repository is Windows Server 2016. Any "gotchas" with this set up performance wise? 2. I might still go with W2022 & ReFS. Possible, but not very likely (see above). Searching for over an hour now how can i add a backuprepository using MS-iSCSI-Initiator. Hyper-V host is Dell Server PowerEdge R760xs Server connected also with Type Server, Dell EMC ML3 Tape Library. Re: Backup to Disk - Synthetic Full - very Slow. 5 and Microsoft ReFS – Win Win for a Virtualization Admins, but this was before the release of ReFS and before Veeam 9. If you want to have a ransomware protected backup environment, you should have a look at the linux hardened repo or SOBR with capacity tier. The storage is direct connected to backup server via 10 GbE iSCSI. I don‘t know about the virtual switch configuration. 31 posts Previous; 1; 2; jja Enthusiast Posts: 46 Liked: 8 times Joined: Wed Nov 13, 2013 6:40 One is a local StorageSpaces "RAID" with a ReFS/NTFS partition and the other one is an iSCSI target on a Synology NAS. I did a fresh Veeam VM install with 2025, installed also 12. With the fastclone feature, you will get spaceless synthetic FullBackups. We moved back NTFS and we'll never look back for the data I’m currently experimenting by performing a Full (not Quick) ReFS Format from the Win2019 Server on the iSCSI attached Target/LUN which is (as seen from within DSM on the One topic came to my mind today when I was going a little bit deeper into FastClone with ReFS. This would allow you to use REFS or XFS Refs is hands down better when it comes to storage usage, especially if you have GFS enabled. This would allow you to use REFS or XFS filesystems for block-cloning. This As a service provider we have the requirement to seed data onto local devices that we can transport around. With Veeam, we have a baremetal backup, so we can restore this backup to a new computer (example Laptop broken) and from our test it quickest to copy backup file from NAS to SSD drive (Large Block Copy) then plug the SSD drive on the new computer with USB3 and I think the software (Veeam) need to actively support this. I'm looking for some advice about saving backups to an iSCSI target using Backup & Replication. And Note: Note: iSCSI gives you the option of using a Windows repository with ReFS or a Linux repository with correctly configured XFS storage to use FastClone. Does Veeam storage integration know anything about MPIO? If the proxy servers have Microsoft MPIO installed for iSCSI will Veeam attempt to connect on multiple paths? Currently our proxy servers has a NIC on each storage subnet for iSCSI. Joe Alliance Partner: Pure Storage. Program Category: Veeam Ready - Repository . I So, I have been implementing REFS for pretty much any Veeam Repo's I've deployed for the past year or two. Before we switched our backups, all the data backed up was 19. Using the Microsoft iSCSI Initiator to mount the disk and format is with ReFS 64K on a VM using the vmxnet3 network adapter and 10GbE LAN 2. I generally say you need to complete two full backup retention periods if Hi there, doing my first steps with VEEAM B&R. Re: ReFS / scale out / migrate to new array. We have seen a lot of problems with the ReFS integration and Veeam. The repositories are on a Dell MD3460 (40 disks) Performance at first was extremely fast but degraded with time. I'm okay with that for my back-up storage, but something to consider! The back-up server needs to be Windows Server to create a ReFS volume. All of you guys gave me a lot of information already, the most important one was actually with ReFS problem Though. As I remember on v11 it was written in the “Action” description. exe command (separate from main Veeam tools but provided by them) and this also A few weeks ago, Anton Gostev from Veeam wrote about a new, otherwise undocumented tool in Windows 2019 called “refsutil”. Last year we installed on the same machine Veeam Backup for Microsoft 365 side by side with Veeam Backup & Replication. We have about 240TB of Veeam repositories on iscsi formatted with ReFS (consultant did I have a ReFS iSCSI target at ta Synology NAS and it is running like a charm for months, it ain't super fast but it is doing its job. I have a exist repository using refs block clone on a refs volume using storagespace. But you can search the forums for "iSCSI ReFS" and find a plenty of examples of such repositories. Ressource monitor show that the disk are in no way at maximum load. Initially we had Veeam backup to ReFS on that, and initially is was working well. Is a ReFS volume on an iSCSI LUN hosted from a Synology NAS a good thing to do? The reason for this is to gain performance by utilizing faster synthetic fulls. If our backups are at risk (because of these ReFS issue) we must implement this to every VM, but so far only in one location we got RAW unexpectedly. adb file in the repository. I have a volume being served via iSCSI and mounted to a Windows Server 2016 box and formatted with ReFS. SISR4 Chapitre 14 - Page 25 . Then backup to that datastore from within Veeam Since I installed the HP intelligent provisioning update, there has been no issue with accessing the ReFS volume. Host-based backup of VMware vSphere VMs. Imaging having to restore a 5TB VM from that storage. thanks You're right, probably it's a ReFS problem but as we have a second volume on the same server with the same setup coming from the same storage array and this one doesn't show any problems, it could also be a problem with the ReFS API calls from the Veeam software. 10 REFS Registry keys : RefsDisableDeleteNotification=0x1 This question is both related to Vmware and Veeam best practice, but let's try it here. Therefore, see this the below iSCSI is preferred to using SMB. Not a support forum! R&D Forums. [For releases prior to 4] The proxy server IQN and Veeam iSCSI IQN used for host discovery must be registered with the same host on the storage. Post by tschwendemann » Mon Feb 13, 2017 7:49 am. After that main Backup is done we have a Backup Copy Job trough IPSec to our Branch Office where we also have Synology - Veeam Backup & Replication installed on a VM, the same VM is used as the backup repository - You have a NAS device with an iSCSI LUN - iSCSI LUN is directly connected to the "Veeam Backup & Replication" VM. Alliance Product: FlashArray//C. iSCSI Multipath needs that to work correctly. iscsi block lun + Server 2016 REFS + synthetic fulls + block clone = the best it is going to get Stick the iscsi on it's own vlan of course refs really saved the day with NAS appliances. Also, built-in dedupe in Windows is a shared engine between NTFS and ReFS. For Veeam REFS is a no brainer. Hardened repositories can be Performance Tiers It would be better to use iscsi and refs, if that‘s the case. Microsoft has demonstrated that they're not ready to take ReFS seriously, or any aspect of 2016 for that matter, with too many things being pushed off to Server 2019. I need to move a bunch of GFS backups to a new Repo. Most likely it comes from here, where it more clearly states that iSCSI SAN is not possible for Storage Spaces. Do Veeam Community discussions and solutions for: ReFS is not supported on SAN-attached storage of Veeam Backup & Replication . Use cases: 1) Backup Copy Job with GFS policy as the GFS VBKs will be synthesized and they will also benefit from space saving. Once I replace these Repos, When using ReFS you have the benefit of virtual full back-ups that take up almost no space. 3 hypervisor. Initialisation et formatage ReFS du deuxième disque. I’ve been running a synology in the same fashion with an iSCSI mount on the VBR, refs 64K. 5 release. Otherwise i would go with NTFS. Keep in mind that the Archive and Object storage nodes are displayed only if you have added CHAP authentication is not supported for storage systems working over iSCSI. In case I lose my Veeam Server and need to rebuild a new server can I just move and connect that existing ReFS repository to the new server? The Veeam Server and the iSCSI-connected NAS (with the ReFS repository) are both located in the 2nd. Recommendation See! Background info: We utilize ReFS both on our client side local storage (iSCSI NASs) as well as our service provider side. Using open-iscsi on Ubuntu 20. DELL ME4012 for Repository - Questions. SAS connections are not supported. We have also seen raw disks on time from mishandling the iscsi LUN by IT staff. ReFS considerations. For my Windows File Servers NFTS is the way to go still. That way, e. 2 terabytes in total. IPv6 Support Following the design workshop with our Veeam solution engineer, we redesigned our repositories to be plain ReFS volumes with Veeam’s in-built data reduction. If I have a Backup Copy Job sitting on a ReFS repo is there anyway I can move those files to another ReFS repo (different volume) and retain the space savings or once I copy those files off the ReFS volume they were Note: Note: iSCSI gives you the option of using a Windows repository with ReFS or a Linux repository with correctly configured XFS storage to use FastClone. However, after about two weeks already, we started to get performance issues. Topics Posts Last post; Veeam Backup & Replication Comprehensive data protection for all workloads I'd have to create a VM network to the iSCSI vswitch or just run iSCSI over their production network - I believe it's not recommended to mix production/iSCSI traffic. But it has the No storage spaces or SAN/iSCSI techniques is used here. We were simulating disaster recover procedure. HannesK Product Manager Posts: 14807 Liked: 3067 times Joined: Mon Sep 01, 2014 11:46 am Full Name: Hannes Kasparick Location: Austria. Depending on the external volume, what I have found is that some permit the formatting with ReFS, some do not - but when you do the backup copy to the external media and create the GFS retention, that is a synthetic operation so in that respect BCJ is eligible to benefit from ReFS, but not when you copy off those backup files and they'll literally be copying the Not sure why the RAW partition gets protected, but we only support the following file systems with Veeam Agent for Windows: - FAT32/exFAT, NTFS, ReFS May I ask, why you want to connect a Linux volume to a windows machine? Just connect your iSCSI volume to a Linux machine and use our Veeam Agent for Linux to protect it's content. The issue is we have 2-3 VM BDR servers which also have SOBRs and the local storage is ReFS. SISR4 Chapitre 14 - Page 27 . DaveWatkins Veteran Posts: 370 Liked: 97 times Joined: Sun Dec 13, 2015 11:33 pm. 30MB/s speed (2x for read write) isn´t that good. consume much more space. ReFS on Hardware or Software RAID? Comprehensive data protection for all Storage Server -----iSCSI-----(ReFS) ----- Veeam Server I figured the second approach would be a bit better, at this point I don't plan on implementing CSV much like the blog. The following registry value exclusively controls whether Veeam Backup & Replication will attempt to use Fast Clone with Windows Repositories and has nothing to do with SMB/CIFS repositories. All vm backups store in refs volume. a full VM We have one hp g10 server(30 vms), 1 qnap nas with 9 TB storage. Would still be interesting to hear any ReFS horroror actually non-horror (good) stories folks have experienced with ReFS. We wrote about Veeam and ReFS in detail in our post here – Veeam 9. when I begin getting my new arrays installed & switching things over, I think I’ll just be looking at going with XFS. Reading data for the "to tape job", is no problem as well. Suddenly, after a restart of the Windows server, the volume showed up as RAW. Veeam 9. iXsystems recommends using iSCSI on TrueNAS 13. Is that a good way or not? If not give me the best approach to backup my vms. sys" in C:\Windows\System32\drivers, for example to refs. You can create an ISCSI target or LUn on a Synology DS923+. 1 after Veeam released its version 9. Best, Fabian I ended up attaching the iSCSI to VMware and then create a datastore on the Qnap iSCSI target. I haven’t yet pulled the plug as far as deploying ReFS on any of my Repos. 2. DAS or FC-SAN block storage is preferred over ISCSI. - What storage appliance do you have? We had two QNAP Storage - How many vms will be backed up? We had 72 VMs with hyper-V will be backuped up. One thing I mentioned is the change of used RAM of Metafile at the tool RamMap. I experienced similar issue, minus the BSOD, when I attached a large ReFS volume via iSCSI from a Dell SAN. For no known reason to us, REFS at various customers sites has imploded multiple times on us leaving us with RAW volumes that apparently have no way of being repaired. Re: Veeam Host Upgrade + ReFS setup. This is working fine. I'm pinging the forum to see if anyone else is running a similar configuration. Afterwards please rename the original "refs. We had If buying a qnap is already set in stone, then please create an iSCSI LUN on the NAS and connect from your vbr server with iSCSI to the NAS. therfor all data on the RAW Device are lost. Also keep in mind if you wish to use ReFS then the storage must be "local" to Windows which would also mean using iSCSI. Veeam B&R and our main Synology are located in the same location within same subnet. We have one legacy setup with iSCSI, which craps out even faster on ReFS (the iscsi time outs seem to make it worse) Top. CIFS is really bad. I have the strange feeling that Storage Spaces is causing some issues, so I will change the RAID setup. 2. The proxy and repository role are installed together on a separate virtual server, repository is mounted to the proxy/repository server via 10Gb7s iSCSI network, repository is formatted with ReFS. I'm planning to migrate 100+TB of backup data from a ReFS-based repository to an XFS-based repository within an SOBR. the only way is to buy a software which can recover REFS. Similar with a Windows host too. Every so often a backup gets corrupted and is detected either via Veeam's built in backup health check or via Veaam's validator tool. Considering REFS for a small deployment, advice needed. Two questions: The following limitations apply when Veeam Backup & Replication uses Fast Clone for Microsoft Windows or SMB backup repositories: Veeam Backup & Replication does not use Fast Clone for backup repositories configured with Veeam Backup & Replication 9. Buy a eSATA 6Gpbs PCI-e card in the server Hey all. I had all the luck with the ReFS Repo and it failed a couple times, I 1)Is it best to detach the extents from the SOBR / Veeam and the move the ISCSI storage across to the new servers, re-add back to Veeam / SOBR and rescan? 2)Is it best to create new extents on the 2022 servers, add them to the current SOBR and seal off the extents of the 2019 servers so that data is only added to the 2022 extents? Here's what I have observed after some testing with regards to Veeam 9. R&D Forums . My goal is to use a 20TB ReFS backup repository, where the file system is formatted with ReFS 64k cluster size. Currently one iscsi drive is NTFS and the other is ReFS. Anyway, the server needed to be rebooted, and now, the Connection to the iSCSI device is being made still by windows, everything looks fine, but the ReFS volume NEVER shows up under Computer Management- In my last post, I outlined a number of new enterprise scalability features: Backup acceleration technologies, full VM-restore acceleration technologies and core engine enhancements. So i thought if they say its fine, it should also be supported by MS. 04LTS to mount the disk and format it with XFS 4K on a VM using the vmxnet3 network adapter and 10GbE LAN VMware host > iscsi lun Virtualized Veeam Server > direct attached iscsi lun (as backup repo) > formatted ReFS We did a couple of tests. The advantages with using REFS compared to NTFS are big : you can use synthetic full backups so allows you to have much more restore points on the same size of storage and is much more faster because pointers are being used to If you must use a NAS (don‘t do it ), then use iscsi. Veeam Community discussions and solutions for: DELL ME4012 for Repository - Questions of Veeam Backup & Replication . vdmk), in my opinion - its old concept. SISR4 Chapitre 14 - Page 26 . And then I would connect the iSCSI LUN directly to the VM. 2022 of Veeam Backup & Replication. adrian138 Influencer Posts: 24 Liked: never Joined: Wed Aug 08, 2018 7:41 am Full Name: adrian reinhard. 1 64K, and created a repository to that Windows VM with a target of the drive letter for the ReFS iSCSI disk. That meant no RAID controllers, no FC or iSCSI LUNs via a SAN whether that was a high end one or and entry level one that you normally only use for backup purposes. There was a post where someone had Running Veeam B&R version 10 on Windows 2012 r2 fully patched. Why are you virtualizing Veeam in that setup? I think that ReFS is resource intensive and delicate enough to add more factors to the equation 2. But, it is not supported by Microsoft. The volume is formated as reFS May I ask what do you mean with "Loop"? I can share some thoughts about the safety considerations of your Veeam Community discussions and solutions for: ReFS 2019 vs. On the downside this can result in random I/O, e. Re: REFS 4k horror story. Create iSCSI Targets/LUN. Since formatting our backup hard disks with ReFS and setting up the Today I changed my setup and all of my jobs will write the backups to the two (local SAS and iSCSI) ReFS repositorys. We've used REFS (because it is recommended by Veeam) for several smaller sites with iSCSI mappings to a Synology or just VMDK's on ESXi hosts. 5TB from IOMEGA, formant using ReFs with 64K blocks. SISR4 Chapitre 14 - Page 28 . Active full backups behaviour of 600GB source data Thoughputs highs at the begining Memory increasing quickly on the proxy/repository server until 40GB. Hi Guys, lot of my customer has Veeam as virtual machine in VMware and using the virutal disk as repostitory (. A For back-up copies to NAS, I use iSCSI and ReFS 64k file system to get fast merge/synthetic operations using fast block clone technology. On the primary site, Plan is to have VM with ReFS storage connected With Resilient Filesystem (ReFS) integration into Veeam Availability Suite 9. It was t limited ReFS to Storage Spaces and standalone disks only. There are pre-built options, which allow you to configure it Veeam Community discussions and solutions for: Veeam repository from Netapp, S3 or Repo of Veeam Backup & Replication R&D Forums So you recommend that I mount volumes from Netapp FAS with Iscsi and format them with Refs? Top. We tried both a direct partition (windows disk manager -> format REFS), as well as creating a storage space with the single volume also formatted REFS. when reading a synthetic full backup file because the data blocks are distributed over the disk. Before I was using If the volume is dedicated to Veeam backups, you can also use a larger block size; you are not going to waste partially written blocks, since all files will be way larger than that value. e Veeam Backup for Microsoft 365 uses these backup repositories only for data backup. It is currently Fri Dec 20, 2024 5:24 am. Veeam has much more experience with ReFS and how they trigger it so it is worth a Although not technically required, Veeam recommends the use of ReFS over NTFS for performance reasons so we tend to prefer this option. Then mounted RAW LUN to Windows VM, witch will be a Veeam Repository and formatted as ReFS. After connecting it to the Veeam machine, I formatted it as NTFS with a 64KB block size. PS: But just so you know, using ReFS and a NAS via iSCSI is not supported by Microsoft. We are using a ReFS volume under Windows Server 2016 as the target for our backup jobs. Such volumes are used for service purposes and are filtered out. It is the target for our Veeam backup jobs ; The VeeamReplica volume is presented to our VMware setup and is the target for our Veeam replication job; When these volumes are created on the Nimble array I have to choose what Nimble calls a The Veeam virtual machine is connected to a QNAP TS-873AU-RP (QTS) NAS via iSCSI. Use reFS as the filesystem in Windows for the connected iSCSI LUN. Part of the announcement for 9. Just want to make sure that the ReFS filesystem will work on the windows 2016 when the If you want to use block clone the question is probably more accurately what are the pros and cons of XFS+iSCSI vs ReFS+iSCSI. I'm using Windows 2019 and configured iSCSI with a volume of 1. 5 included integration with the Resilient File System, otherwise known as, the ReFS file system from Microsoft. Random I/O profiles on spinning disks will be much slower than sequential I/O. sys_original, copy the contents of the archive into the same folder. 1 (when used with Windows 2016) to use the new block cloning. b) USB3. Let’s dig in! The following registry value exclusively controls whether Veeam Backup & Replication will attempt to use Fast Clone with Windows Repositories and has nothing to do with SMB/CIFS repositories. ReFS over iSCSI to a NAS is not officially supported by Microsoft, so Microsoft says it might break and we won't help. This tool provides a mechanism to triage and recover failed ReFS volumes. Post by DaveWatkins » Thu Feb 15, 2018 To summarize, the January 2022 cumulative update problem affects both removeable drives and fixed drives (direct attached, iscsi) with ReFS 2 or lower. I do like the option of mapping the iSCSI LUN to another server if the VM/hosts go offline. Now there are random crashes, ram usage goes up, CPU is 100% by system proccess. Contains Azure Blob Storage Archive access tier and all Amazon S3 Glacier storage classes. It is connected to the network over iSCSI (Jumbo Frames activated). I am considering using either QNAP or NAS server. All data is on the iscsi hard drive. Last visit was: Fri Dec 20, 2024 5:24 am. The post in the Veeam digest indicated that it existed, was probably good, but no one really knows what it does. 2022. There has been a lot of discussions about ReFS 3. x not compatible with ReFS as it's removable storage and not supported. 5. - How is the LUN connected to the repository server? iSCSI, FC, SAS? ISCSI Connection. The Veeam Backup for Microsoft 365 repository is currently hosted on a 64KB I cannot find any official information from Microsoft that ReFS is supported for basic disk on iscsi. Have 2 NAS connected, no drive Letter assigned. g. Sorry never dare to try this. Then the The two are connected via iSCSI (MS iSCSI initiator) and the volume (currently 20TB) is partitioned with ReFS, 64k block size. Post by In a VMware infrastructure I have a virtual Windows File server with a mounted iscsi hard drive. Best regards, Hannes Hello everybody,I have the following question regarding Backup Copy Jobs:I will create Backup Copy Jobs with Immediate Copying Backup Jobs are configured with incremental + Synthetic Full Backups going to Windows Repo (ReFS 64KB) connected via iSCSI to our NAS storage, Utilizing FastClone option. The backup server is physical R720, with 10 GbE The VeeamBackup volume is presented via iSCSI to our Veeam physical proxy server and formatted ReFS. The backup will just leave there for GFS purpose and no new backup will write to there. SMB based storage should be avoided (only experimental support). Yes, go with iSCSI and REFS. 04 installed and am at the point of where I want to setup the data volume where the backup repository itself will be. After copying the new refs. What would be the best optimization when we have Veeam + Synology in our Environment. We use CEPH as a backend storage system, for various reasons we would like to keep the size of the iSCSI disks to a managable size, say maximum 10TB per disk. All Veeam Servers are installed on Windows Server 2016. 3, migrated old config and attached backup data disk over iSCSI, with Refs on it. Just for clarity, I’d add “Repository” to your Windows VM objects running ReFS/iSCSI in your diagram, as they will be used for the Repositories Veeam component. And it is not planned in the short term. I have changed two jobs, one is writing backups to the RefS iSCSI target, the other one to the local ReFS SAS volume. Do Backup Storage is an ISCSI target formated as REFS with 64k cluster, volume size 40 TB Software : Windows 11 Enterprise (REFS is natively supported on it) Veeam components version : 12. 5 integration with ReFS and Storage Spaces. Other reason is I didn’t want to go through the hassle of creating a new Repo, then spending days migrating data here/there/ever Our Veeam physical proxy server is currently running Windows Server 2019 Standard version 1809 which is the Long-Term Servicing Channel. There is almost no documentation or Basically i am trying to implement a Veeam backup solution that will use ReFS and windows server 2016. While our ReFS and XFS systems are not entirely identical the good thing is we have some backups which are on quite similar storage on the source and destination of a backup copy. Thank you. We are planning to deploy Veeam backup and replication on Hyper-V Guest VM and connected with Synology NAS for Backup. Is it even a supported set up? From what I've read and my understanding of how Veeam does things like merges and synthetic fulls, I'm Your direct line to Veeam R&D. Not a support forum! Backup repo is a Synology nas and the Veeam B&R server has an iscsi target to the Synology. Your direct line to Veeam R&D. I am new to Linux and am working on setting up a Linux Hardened Repository to move my backups to. Have seen google posts about adding a “UseCifsVirtualSynthetic” reg key, which appears to be for older version of B&R, tried it anyway Should I set them to LAN target? For the backup jobs I am reading data from storage snapshots on the source side and writing data directly to a volume on my proxy server that is formatted ReFS. If you use iSCSI the disk is managed completely by Windows and can be formatted with any filesystem you choose. I think it should be your Veeam VM the one running the modern Windows edition and not your hypervisor system. (check ReFS version using fsutil fsinfo refsinfo <drive letter> ) Anyone know if the February 2022 cumulative update has the same problem ? During backup we get warnings from Unity that the proxy servers are connected on a single path. We opened a Veeam ticket (02163118) but when Veeam support found out that the issue also happens with normal file copies to the REFS they basically told us that it is not a Veeam issue. Thoughputs drops to 0 after processed one disk and iSCSI LUN not responsive for few minutes. Hello Everyone, we had the same Issue on Re: Veeam B&R to Freenas ISCSI - REFS Post by Gostev » Fri Nov 15, 2019 5:40 pm this post Yes, ReFS via iSCSI is a supported configuration that is fairly common. Yes, we have connected our iscsi storage directly in to the vm. Quick links. Reading Veeam's best practices, I've had no problems in formatting it with 64KB block size, but I'm not sure about configuring a ReFS is ok, but ideally it needs to live on a Windows Server machines. And after two months restoring a VM would be slow as hell, with about 30MB/sec max. From there I created a new virtual disk that I attached to the Veeam server, formatted it with ReFS, then disconnected the disk and attached it to a local proxy. However: a) iSCSI too slow as only 1Gbps switches and 1Gpbs NIC. We're currently backing up to QNAP devices using SMB shares, but are looking to move to iSCSI to take advantage of ReFS. Is there som Hello, I wanted to be sure that fast clone is enabled but I can’t see it anywhere. The server that is Backup Copy target is running Windows 2016 and all drives (except the system drive C:) is formatted with REFS 64K. But if managed properly, it provides a lot of advantages over NTFS Veeam Community discussions and solutions for: Backup Optimization: Storage, block sizes, RAID, backups of Veeam Backup & Replication . Need more time to see how CIFS may not perform as well as iSCSI, though your mileage may vary. Suggestions? Top. @Scott - agree. With that question, as @Gostev notes, there's little functional difference from the Veeam perspective between these two. Technically you don't even need to disconnect the iSCSI unless for some reason your storage system requires this. Get a real dell/hp/Cisco server and you won't have any weird issues or data loss. We've had a couple corruptions of ReFS volumes, which is the reason to avoid it. I don’t like running REFS on a NAS however because it likely is a software-based array with no batter-backed cache, and this can result in REFS filesystem Anything to watch put for thats specific to Veeam? Maybe disable all Veeam services before upgrade? I want to make use of Server 2019 ReFS , block cloning and de-duplication. For my environment. VBR is installed inside a VM to have an abstraction layer from the physical machine and to have the ability to test backups by creating VMs on the Hyper-V host. Last step -> Reboot Veeam Server This solved our problem. If windows cannot see them, veeam can not use them. It’s formatted as ReFS (64KB). If the service "VeeamAUX" host with Veeam IQN exists, it should be As I can see they are using ReFS File System. Now I want to move that repo to a new server by preserving all the backups and chains. Veeam Backup for Microsoft 365 uses these object storage repositories only for backup copy. 5 a whole bunch of features was integrated. After the installation, ReFS volumes are shown as RAW and are no longer accessible; so if you’re using ReFS for your repositories, then take be aware of this when installating the update. sys please execute this command: bcdedit /set testsigning Then please create the following registry keys on the server in question: Just make sure to configure your iSCSI network properly and do not change settings on the fly, and you will be good. HannesK Product Manager Posts: 14810 Liked: 3068 times Joined: Mon Sep 01, 2014 11:46 am Full Name: Hannes We installed Veeam Server all in one. There is another iSCSI Volume mounted to the same repository server. Category Description: Primary backup target solutions that have been qualified as meeting or exceeding both functional and performance tests for backup and restore operations. In fact, V11 is so highly optimized for deployments on general-purpose servers that backup performance can exceed 11GB/s with a single box! This topic is the continuation of the previous discussion, where some recommendations were no longer correct because they were made a few years ago, and the But I think it leaves the Veeam GUI with very little information to verify, if a ReFS repository actualy is configured correct. Before W2016, yes indeed. (in older Posts from 2020 Veeam suggested to use REFS for iSCSI Currently have a Veeam server which makes Backup Copy to another server. But i will check it again in the link you provided. At the moment I am running Storage Spaces and I want to change it to a HP RAID. Since this is a pretty new device, we will create both on the fly. So how about: 1. You just resize the device then rescan the devices in Windows and it will detect the new size of the device and show to space free, then resize the volume online. Top. I have Ubuntu 22. Last week @tsightler asked me if i head any real world performance comparisons between ReFS and XFS. Windows 2019, large REFS and deletes. In Veeam B&R I am creating a new job with a Windows Agent backup because I am using the iscsi hard drive and Veeam would not see the iscsi in their normal job and would therefore not be able to save. You could always spin up a Windows VM to act as the repository and connect to the Synology using iSCSI, though it would be recommended to use a physical Veeam Community discussions and solutions for: UseUnbufferedAccess, DisableHtAsyncIo and V11a of Veeam Backup & Replication . This is probably the best advice as noted by Nico. For Windows Server 2016 (or later) repositories, formatting volumes into ReFS, will allow utilizing Fast Clone technology, which drastically improves performance of the synthetic operations. take much longer 2. Format the disk As many you know the ReFS supported storage deployment option has “fluctuated a bit. Is it a 1GbE network? Maybe you can add the Synology as iSCSI volume to the Veeam Server and format it with ReFS 3. Not a support forum! Skip to content. but mostly leaning towards going with XFS. Honestly, I never did estensive tests on this configuration, but for Veeam backup storage I used 64kb raid blocks and 64kb NTFS blocks as a best practice, but I say it again with no validation Veeam can use both local and remote storage, so i wouldnt go with iscsi but simply with a remote repository within Veeam. We have a VMware Infrastructure with 4 Nodes. Other reason is I didn’t want to go through the hassle of creating a new Repo, then spending days migrating data here/there/ever So we have a Veeam "head" running as a VM with all the services and I'm assuming when I add this physical Windows box as a backup repository it will install the data mover stuff and know the target volume is ReFS. However, there's currently a bug on the Microsoft side in ReFS and Windows dedupe interop which impacts NAS backup specifically, so go with NTFS. I have also run Veeam's COFI. iSCSI with NTFS would be better. Veeam Backup & Replication. Backup Optimization: Storage, block sizes, RAID, backups By the nature of Block Cloning the most disk space savings are had on the Full Backups. One of my customer has new Storage Array and Physical backup server. I have a Synology DS920+ at home and use both iSCSI and NFS in VMware which works great for Veeam. I would imagine its going to be a pain to get them both to ReFS and dedup/cloning? Just a quick post; the latest Windows Server updates for 2012R2, 2019 and 2022 (haven’t seen 2016) can cause ReFS issues. I get full saturation on a 1g link. 5 sees the storage fine but the 2 big signs that REFS is not being detected properly are being shown: Option 1: Setup the NAS as an ISCSI device and direct connect from the VBR repo server to the NAS as an ISCSI volume. They proposed using the AWS storage gateway and just attaching it as an iscsi disk to the Veeam server itself, and setting the repository as that iscsi disk. Before the accident, from the QNAP side, the network setup was an I have a volume being served via iSCSI and mounted to a Windows Server 2016 box and formatted with ReFS. There are literally thousands of people running QNAP and Synology as iSCSI + ReFS backup targets for Veeam B&R without any single issue. now I have to decide with the same customer whether to switch to ReFS or stay on NTFS. After that, choose any GFS Setting you want. tschwendemann Lurker Posts: 2 Liked: never Joined: Thu Sep 19, 2013 12:53 pm Full Name: Tobias Schwendemann. Good news: yes it can! But you have to take some facts into account. Products. From a best practice Veeam Community discussions and solutions for: ReFS strange performance issues of Veeam Backup & Replication . VMware vSphere . "Good enough" is probably the main point Probably it's "good enough" and if you have a second backup copy, then the risk of losing data would be close to zero. Regards David One of my biggest wishes for the next update is that Veeam removes the ReFS suggestion from the Repository wizard. Format the disk with REFS again, restart the server (2 - 3 Time) and check the stability of the REFS Disk (ISCSI Target) if ReFS is so problematic that any small NAS reconfiguration can ruin all volume, so I'm right now revert back all my connected to Veeam volumes to NFTS, It's definitely better for me to keep my head calm rather to have performance improvements from unreliable ReFS. We have noticed some strange performance issues when the servers are writing to disk, and the block size is the probable datastores are vmfs6, repository is a ReFS 64kb volume on another SAN I'm fairly new to Veeam, and the way that I have set it up is using a protection group for the cluster, and then a volume based agent backup on that to get at the actual LUNs We use an EQL SAN meaning that I cant integrate to that with Veeam and grab the LUNs at the storage level Dear Veeam Community We plan to use a Nimble Storage as Backup-Target. Perhaps a bit late to be useful but I wouldn't use a Qnap as iSCSI target or virtualization station for a Veeam backup repo. This NAS will be the target for Veeam backups. My Veeam server is a virtual W2012R2 running on a brand new ESXi 7. This means as space is freed up on the ReFS volume, our Nimble storage array will not see these savings. I use iSCSI to mount LUNs to repository servers in two ways: 1. So for example we would provision a customer with one or more 10TB iSCSI disks. I could connect directly to Windows VM iSCSI initiator, bypassing ESXi ISCSI configuration, but my argument that if I loose Repository VM, I can connect RAW disk quickly to a different Windows VM on that ESXi host, bypassing ISCSI configuration in The advantage of iSCSI over SMB / NFS is, that you can format it with REFS. 5 with support for the block clone API. From a best practice Reinstalled with Server 2016 ReFS -> performance was way better, in fact so ok'ish that we started using it for Veeam storage (while continuing to run Netapp Snapshots & Snapvault to Secondary, previously we wrote the Veeam backups to Netapps, too, via SMB3) Your direct line to Veeam R&D. Though, we only encoutered this problems with the 10GB Ethernet. Backend and/or frontend. Comprehensive data protection for all workloads. With an iSCSI target you still have to run the server on other hardware, be it bare metal or a VM. 0 with a Veeam scale-out repository architecture. And you can leverage FastClone if you mount it to a Windows 2016 or above and format the iscsi LUN with refs (On Linux also possible with xfs). Installed Latest version of Veeam Backup and Replication software on Windows 11 OS and tried to attached iSCSI Drive( NAS Synology) which is formatted using ReFS. We have ceph and emc mounts in larger I recently lost a ReFS volume on a NAS (QNAP TS-832PXU), connected to a Windows 2019 server through iSCSI. Sounds confusing, agree. You can see that it was a Synthetic Full but. We have 2 iSCSI connections, one over a 10GB Ethernet and the other with a simple 1GB Ethernet. perjonsson1960 Synology block size is 64K and so is our REFS block size when formatting. I've had a look and can't find much on setting this up with Veeam. Veeam Community discussions and solutions for: ReFS on Hardware or Software RAID? of Veeam Backup & Replication . With support for SMB/CIFS, NFS, AFP, ashleyw wrote: So unless you have a 4 node hyper converged infrastructure running just for backups, the main benefit of using Re-FS on top of ZFS is that we get maximum performance and capacity on the spindles with the benefits of application aware de-dupe in Server 2016 that is coming in Veeam 9. Hello Hannes, If i choose "Shared Folder", the option "backup cache" is not available. Veeam Backup & Replication does not display volumes and snapshots with the '"VeeamAUX'" prefix in the storage hierarchy. I realize that NAS’s are less than desirable, and my standard procedure is now to I created a LUN on a NAS (Synology Rackstation), presented it to a Windows 2016 Server VM as a drive via iSCSI, formatted it as ReFS 3. So, I have created an iSCSI target on a NAS and am not sure the best approach to save my backups to it. I’m using Synology NAS connected directly via iSCSI to the Windows Server 2022. . It‘s better, because veeam has access to the file system. ReFS strange performance issues. Almost every aspect of it has already been brought up here by some other users. They are a required component for Veeam, as are Repositories, beit the “default” Proxy/Repository (i. Both Repo's are about the same size, round about 15TB each. (or later!) Treat ReFS like that friend that is always late or Hey all. We have not seen this issue on Windows 10 Pro OS as we have tried from Windows 10 Pro laptop as well. This server is pretty beefy with 16 cores (32 threads), 128GB of RAM and a 50TB ReFS disk volume as the Veeam repository. Now NTFS formatted backup repository disk is far too slow for Veeam merging Need to use ReFS but only have option for external storage. To answer your question about Proxies → yes, Proxies are needed. but see no reason to use SMB or NFS as target with a Linux-based NAS. This volume is attached to the proxy server via a 10gig iSCSI connection to the brand new Nimble array. That's not an issue of Veeam persé, juts a side effect of the technology used. They need to be connected and visible for the windows OS in the windows disk manager to use them with veeam. ekbbcr nymofvk xwapnn tgkzbdgm eockfq apttgjp stn jswzg mbtp yvirucob