![]() Interesting to see Fortinet switches mentioned in storage, I was wondering OP wasn't using Arbua. Literally any opinions or advice is welcomed. We get MBs transfer rates, not GBs.Īll of the VLANs can communicate, theres no additional hops being made, we can't see the traffic outside of the specific networks.ĭoes anyone have any ideas of anything we can check please? Or from my description is anything wrong? We put this solution in summer last year and it has never performed well. We are experiencing such slow speeds within the VMs, it is almost unusable. There are 2 Netgear switches inbetween the hosts and the Nimble for failover, each VLAN has 2 ports per host and each has one connection into each switch. Right now we have a couple large datastores on the Nimbles and allow DRS to control placement.We have a Hyper-V 2019 Datacentre Clustered environment, 10GB Netgear 4300 Switches and a HPE hybrid Nimble (flash cache + spinny disks), there are 2 hosts (HP D元80 Gen10), identical spec with 9 ports over multiple teamed NICS (all 10GB apart from management), all on sperate VLANs (iSCSI, VM Client Network, Cluster Shared Volume & Migration). Would we create multiple datastores for each customer/backup job so that the job could do all of the VM's in a single snapshot without having to delay any other job. So my question was how to organize the backup jobs with the VM placement on the datastores to get the most of using Nimble snapshots just for the duration of the backup. we do not retain any volume collections on the Nimble. The proxy servers have the datastore LUNs mapped to them for SAN transport on backups. So we are trying to leverage Nimble snapshots to minimize the effect of the snapshot on the VM's for the backups. There are backup copy jobs to send the backups to a couple different offsite repositories. We use SRM and soon to be Zert0 for replicaiton and failover to our d/r site. We do not use Nimble replication for offsite as we don't have one offsite. The Veeam repository storage is on a separate IBM V3700. In our environment we only have the 1 Nimble as primary storage for VMware. In the VM i get the Warning "Failed to prepare VM for processing from secondary storage snasphot, failing over to primary storage snapshot"Įdit: If needed i can open a ticket, so that i do a remote session with a Veeam Engineer to get a look at these jobs. Somehow Veeam wants to look for the replicated storage snapshot first instead of creating the primary storage snapshot, then replicate it and then use the replicated copy as a data source to do place the backup files on the Scale-Out Repository is the blog Post outdated with the GA Release of Veeam 9.5? When i start the Backupjob the third thing which Veeam tells me is "cannot find matching replicated copies of Nimble Snapshots" and if i wouldn't tick "Failover to primary storage Snapshot" Veeam wouldn't do anything. The Replicated Copy should be used as a data source. I also configured secondary Targets where i added Nimble Snapshot and Nimble Snapshot Replicated Copy. My Backup-Repository is a Scale-Out Repository from the Backup Proxy which also sees the Nimble Volumes via iSCSI Hope somebody can enlighten me a little bit, because i couldn't find a "best practice" for Veeam and Nimble.Ĭan it be that the Blog Post is totally outdated? ![]() ![]() So would it be better to put all LUNs/Datastores/Volumes into 1 Big Volume Collection since Veeam will be steering the Nimble Replication and Snapshots? Since VMs with different Priorities can reside on different Datastores it wouldn't make sense to create many Volume Collections on the nimble right? Then i would need to create another Job in Veeam that uses the replicated Nimble-Snapshot as a source to get the Snapshots from the replication-nimble to the Repository. Then i would use these Jobs in Veeam to make a Schedule for Prio-1 where the First Backup goes to the Primary Nimble-Snapshot and then as a secondary Destination the Replication-Nimble is assigned. I would use Tagging in vmWare to define which VM has Prio-1, Prio-2 and so on, so that the VM with the Tag Prio-X gets into the corresponding Veeam Job. Prio 1 = 1 Snapshot on the local nimble, 4 weeks of snapshots on the replication nimble and 8 weeks on the Repository Server). We have different Priorities for virtual machines in vmWare where each priority is given different retention times for the backup (eg.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |