#vvf
Après le rejet par les députés de la pétition réclamant la fermeture de CNews, la juriste Camille Broyelle explique pourquoi rien ne justifie, aux yeux de la loi, de maintenir la diffusion de la chaîne.
➡️ www.altereco.media/vvF
November 17, 2026 at 3:52 PM
[ New Post ] Upgrade vSphere 8 to VVF: upgrade vCenter - pt.1
As the end of life for VMware vSphere 8 approaches, upgrading from vSphere 8 to VVF must be planned carefully and executed on time.
nolabnoparty.com/en/upgrade-v...

#vmware #vvf #migration #vcenter #virtualization
Upgrade vSphere 8 to VVF: upgrade vCenter - pt.1 • Nolabnoparty
As the End of Life for VMware vSphere 8 approaches, the upgrade vSphere 8 to VVF must be planned carefully and executed on time.
nolabnoparty.com
November 17, 2026 at 8:11 PM
[Blog Archive] Upgrade #vSphere 8 to VVF: deploy the VCF Installer appliance - pt.2

After upgrading the vCenter Server, the upgrade vSphere 8 to #VVF procedure requires the deployment of the VCF Installer appliance.

Deploying the VCF Installer appliance and #softwaredepot #aggiornamento
Upgrade vSphere 8 to VVF: deploy the VCF Installer appliance - pt.2
nolabnoparty.com
November 19, 2026 at 8:03 AM
[Blog Archive] Upgrade #vSphere 8 to VVF: upgrade #vCenter - pt.1

As the end of life for VMware vSphere 8 approaches, upgrading from vSphere 8 to #VVF must be planned carefully and executed on time.

Depending on your business requirements, VMware allows migration to either #aggiornamento
Upgrade vSphere 8 to VVF: upgrade vCenter - pt.1
nolabnoparty.com
November 17, 2026 at 8:01 AM
[🆕] - vCenter Linking Replaces Enhanced Linked Mode (ELM) in VVF & VCF 9.x williamlam.com/2026/11/vcen...

#VCF9
November 18, 2026 at 6:02 PM
SRM is included in VCF and VVF from 2 November 2026. The interim key expires on 2 May 2027, and keeping DR after that means vCenter 9.1 and Protection and Recovery 9.1.3 at both sites.
Site Recovery Manager is now in VCF and VVF, but the interim key runs out in May
Since 2 November 2026 you can't buy Site Recovery Manager on its own any more. It's part of VMware Cloud Foundation and VMware vSphere Foundation, and Broadcom KB 461219 says every active VCF or VVF subscription is entitled to it. For a lot of estates that's genuinely good news. I've sat in more than one renewal where DR orchestration was the line item that got cut, and the recovery plan quietly became a runbook and a hope. It also comes with a date attached, and most teams will notice that date around March, which is about the worst time of year to notice anything. Below is what I've pieced together from the KBs and release notes: who's covered, where the key is, what to check before you apply it, and what getting to 9.1.3 looks like at both sites. ## Who is covered The KB is short and fairly direct. * **Active VCF and VVF subscriptions** are entitled, whether or not you owned SRM before. That covers adding it, renewing it and expanding it. * **Anything bought, renewed or expanded on or after 2 November 2026** already includes it. Nothing extra to do. * **Perpetual VCF licences are not covered** , with or without active support. The KB says those customers need a VCF or VVF subscription. Two things it doesn't say. It doesn't mention perpetual VVF, and it doesn't mention standalone vSphere editions. If either of those is you, get the answer from your account team in writing before you design anything around it. A verbal "should be fine" has a habit of not surviving the next renewal conversation. It's also worth being precise about what the entitlement is. The KB talks about Site Recovery Manager. In 9.1 the product you deploy is Protection and Recovery, which Broadcom's release notes describe as VMware Live Recovery renamed and folded into VCF, and the appliance carries site recovery, vSphere Replication, vSAN snapshots and replication, and cyber recovery workflows. The KB doesn't say all of that is included. Don't assume it is. ## Two ways in, if you already subscribe **Wait for 9.1.3.** Broadcom expects VCF and VVF 9.1.3 between February and April 2027, and that release adds the SRM entitlement automatically. You'll need the Protection and Recovery appliance on 9.1.3 and vCenter on 9.1 or later. **Take the term-limited key now.** This is the route if you need DR before 9.1.3 lands, or you're on vSphere 8 and can't get to 9.1 quickly. ## Getting the key It isn't where most people will look first. It sits in the Broadcom Support Portal under My Downloads, not in the licensing portal. 1. Log in to the Broadcom Support Portal and go to My Downloads. 2. Pick VMware Cloud Foundation or VMware vSphere Foundation, whichever you hold. 3. Choose version 9.1 or later, search for Protection and Recovery and open the group. 4. The key is a PDF listed as "Protection and Recovery (Key)". A few things about that key are worth knowing before you use it: * It covers up to 10,000 protected VMs. * It's an 8.1 key and Broadcom says it works on all supported SRM versions, so it should run against an existing vSphere 8 pairing. * It can't be split, combined, upgraded or downgraded, and it replaces the SRM keys already in vCenter. * It expires on **2 May 2027**. ## Check this before you apply it There's a second KB I'd read before going near the key. KB 438925 covers keys generated on or after 20 April 2026 failing with "The following serial keys are invalid" on older releases. Your new key was generated well after that date, so this applies to you. The fix is to be on a release with the updated licence validation. Broadcom calls the upgrade mandatory. The minimums it lists: * Live Site Recovery and SRM on the 9.0.1 to 9.0.2.3 line: 9.0.2.4. * Live Recovery on the 9.0.3 to 9.0.5 line: 9.0.5.1. * Protection and Recovery 9.1: 9.1.0.0100 or later. The original 9.1.0.0 is on the affected list. If the error still shows after the upgrade, the KB says to split and merge the licence in the Broadcom Support Portal to refresh its metadata. Because the key replaces what's already in vCenter, apply it in a change window, not as an admin tidy-up. Afterwards check every protection group and recovery plan is still healthy on both sites before you close the change. The date to put in the plan The term-limited key expires on 2 May 2027. After that, DR stops unless the Protection and Recovery appliance is on 9.1.3 and vCenter is on 9.1 or later, at both sites. ## The 2 May date Broadcom is clear about what happens on 2 May 2027. Unless the Protection and Recovery appliance is on 9.1.3 and vCenter is on 9.1 or later by then, disaster recovery stops working. Put that next to the 9.1.3 window. If 9.1.3 lands late in that February to April range, the gap between general availability and the key expiring could be a few weeks. And it's two sites, not one. Both ends of the pairing have to land on versions the interoperability matrix pairs, inside whatever change freezes your organisation runs around the end of a financial year. If you're on vSphere 8 with SRM today, DR has just become one more reason to get to vCenter 9.1. The key gives you roughly six months as you are, and the upgrade has to be finished by the end of it. ## What the move to 9.1.3 involves The Protection and Recovery 9.1 release notes are the most useful thing I found on what the upgrade looks like in practice. These are the parts I'd plan around: * **Versions.** Protection and Recovery 9.1 supports vSphere and ESX 8.0 Update 3 and later, and needs a supported vCenter at both the protected and recovery sites. If either site is below 8.0 Update 3, that's your first hop. * **It's a new appliance, not an in-place bump.** Coming from 9.0.2.3, the release notes say you first deploy the Protection and Recovery 9.1 appliance on both sites. Budget for IP addresses, DNS records and certificates for that. * **Replications change shape.** Upgrading vSphere Replication to 9.1 requires every replication to be reconfigured to enhanced replication. On a big estate that's real work and real network traffic, so schedule it. * **Older starting points need a stepping stone.** vSphere Replication 8.7 can't go straight to 9.0.x, it has to reach 8.8 first. Check your actual path in the interoperability matrix before you promise a date. * **Pair one service at a time.** Pairing several services at once can fail. The documented workaround is to pair them sequentially. * **Expect a couple of post-upgrade quirks.** "Failed to retrieve capabilities for site" is fixed by running reconnect on both sites. A test recovery can fail after upgrading from 9.0.4 or 9.0.5, and restarting the hms service clears it. * **If you replicate vVols, start that conversation now.** 9.1 is the last release that supports vVols for this, and Broadcom recommends moving those replications to array-based replication. None of that is unusual for a DR upgrade. It's just more than people tend to allow for when the line in the plan says "upgrade SRM". ## What I'd do this month 1. Confirm in writing that your subscription is active and which product it is. Perpetual estates need a different conversation. 2. Decide the route, key now or wait for 9.1.3, and write the decision down with a name next to it. 3. If you take the key, check your appliance version against KB 438925 first, then apply it in a change window and verify every protection group. 4. Put vCenter 9.1 and Protection and Recovery 9.1.3 at both sites into the plan now, working back from 2 May 2027 rather than forward from whenever 9.1.3 appears. Include the new appliances and the replication reconfiguration. Upgrade Runway does that arithmetic against your change freezes. 5. After the upgrade, run a full test recovery into an isolated network. A green pairing only means the two sites can talk to each other. If you want to see where your own estate stands, the DR Readiness Check walks through entitlement, the recovery site, identity, networking and testing in fifteen questions, including this expiry date. Related: VCF 9.1 disaster recovery, backup and restore, the four-layer protection model, and What you have to be able to restore, on proving recovery rather than assuming it. The staged path from vSphere 8 to VCF 9.1 covers the upgrade this deadline pulls forward. ## Sources * Broadcom KB 461219, Access to VMware Site Recovery Manager for existing VCF and VVF subscription customers * Broadcom KB 438925, invalid licence key errors on older SRM, Live Recovery and Protection and Recovery releases, and the minimum fixed versions * Broadcom, Protection and Recovery 9.1 release notes, for compatibility, the upgrade path and known issues _Checked against Broadcom KB 461219, KB 438925 and the Protection and Recovery 9.1 release notes on 15 November 2026. Views are my own._ More on VCF This is one of the VCF pieces here. The rest are grouped by problem rather than by date on the VCF index, which is the fastest way to find the one you actually need. The free planning tools run in your browser, with nothing sent anywhere. They are all on the tools page, from Estate Readiness Triage to the Restore Evidence Check.
www.mohammadsiddiqui.com
November 17, 2026 at 9:00 PM
Een nieuwe politieke partij: VVF, Vereenigde Vaderlandsche Fascisten.

(waarschuwing: het bekijken van onderstaande foto kan ernstige schade toebrengen aan uw gezondheid!)
November 10, 2026 at 12:17 PM
#RYR80FZ: Malta Air (#Boeing 737MAX 8 200 • 9H-VVF)
3.7 km out at 37000 ft - heading NE with 958.2 km/h. AGP ➜ GOT
https://globe.adsb.fi/?icao=4D244A
https://www.jetphotos.com/photo/keyword/9H-VVF
1000 • 10:16:50
#GWT #EDXW #adsb
November 13, 2026 at 9:18 AM
#RYR43SY: Malta Air (#Boeing 737MAX 8 200 • 9H-VVF)
10.0 km out at 34025 ft - heading SW with 982.9 km/h. GOT ➜ AGP
https://globe.adsb.fi/?icao=4D244A
https://www.jetphotos.com/photo/keyword/9H-VVF
0743 • 12:17:02
#GWT #EDXW #adsb
November 13, 2026 at 11:18 AM
🇲🇽 XA-VVF - AIRBUS A320neo - VOI7731/Y47731, Chicago O'Hare (ORD) to Del Bajio (BJX) - 6.4 mi away @ 30650 ft, heading SW at 505 mph. Spotted 14x before. [02:14:12 AM CST] #0D1151 #XA_VVF #A20N #VOI7731 #Y47731 #ADSB #ADSBbot
November 16, 2026 at 8:14 AM
電工2種、試しに使いまわしで1番をやってみたけど、練習でケーブルの再利用は厳しいというのが解りました。VVFの1.6の2芯3芯だけ買い足すかな…あとリングスリーブも足りなくなるな…。
November 10, 2026 at 9:09 AM
youtu.be/9kMM3pvGUHE?...

九計画実施済
gikiiUGInyy,,,..giiXXG
X
vVF-19eXGkXX-118Znyy
xxxx
サヨナラノツバサ ~ the end of triangle
YouTube video by Ranka Lee = Megumi Nakajima - Topic
youtu.be
November 7, 2026 at 2:36 PM
As letras escolhidas foram... VVF!
November 6, 2026 at 3:26 PM
部屋片付けてたらズタボロのVVFケーブル出てきたんだけどなにこれ
November 4, 2026 at 11:46 AM
Flight: RYR5377
Registration: [9H-VVF]
Aircraft: B38M
Airline: Ryanair (RYR)
Route: Brussels South (EBCI) -> Adolfo Suarez Madrid-Barajas (LEMD)
Time: 2026-11-04 13:23
Terminal: 2
Interesting: First seen
[Track flight]
[🌍 Website]
[🌐 All socials]
November 4, 2026 at 12:00 PM
Incendio Recter a Imola (BO). Gli interventi di Arpae per le verifiche, nessuna problematica ambientale

Arpae è stata allertata dai Vigili del fuoco (VVF), nella serata del 3 novembre 2026 [.....]
Incendio Recter a Imola (BO). Gli interventi di Arpae per le verifiche, nessuna problematica ambientale
Arpae è stata allertata dai Vigili del fuoco (VVF), nella serata del 3 novembre 2026 [.....]
bologna.gaiaitalia.com
November 4, 2026 at 1:56 PM
L’avenir du VVF, mis à la vente, est incertain. Pour éviter une fermeture définitive, tous les acteurs sont mobilisés en quête d’une solution.
"Ce n’est tout simplement pas rentable" : ce VVF du Cantal cherche un repreneur
Le village vacances du Lioran, sur la commune de Saint-Jacques-des-Blats, a baissé le rideau le 19 septembre, comme chaque année à cette période.
l.lamontagne.fr
November 3, 2026 at 1:46 PM
🇲🇽 XA-VVF - AIRBUS A320neo - VOI7866/Y47866, General Guadalupe Victoria (DGO) to Chicago Midway (MDW) - 5.3 mi away @ 38475 ft, heading NE at 560 mph. Spotted 13x before. [01:54:31 PM CST] #0D1151 #XA_VVF #A20N #VOI7866 #Y47866 #ADSB #ADSBbot
November 3, 2026 at 7:54 PM
"Roméo s'est éteint dans mes bras à 6 ans et demi" : Manuela Lopez "anéantie", elle pleure la mort d'un être cher à son cœur
➡️ https://l.voici.fr/vVf
November 2, 2026 at 2:41 PM
i wrote a song for sburb.exe that just got featured in the newest sound page animation & its one of my favorite things ever & i need everyone ever to see it (:
youtu.be/C-ESzMEs3AQ?...
#homestuck #sburb
[S] QYXNTY ZXHMA NLKQM VVF LPOQ HRLS
YouTube video by 7000SKELETONS
youtu.be
October 31, 2026 at 9:47 PM
低圧屋内配線の工事で使用する絶縁電線(VVFなど)の被覆を剥ぎ取る際、芯線を傷つけないように使う専用の工具はどれ?⚡
​A. ワイヤーストリッパ
B. モンキレンチ

​【正解】A:ワイヤーストリッパ
#電気工事士 #電工 #資格試験
November 1, 2026 at 10:51 AM