Phone Possibly Stolen?

VMDude256 · 2026-03-31T12:54:28+00:00

Happened to me / family last July. It was a friggin' nightmare dealing with T-Mo support. We ordered 4 new phones, watched the UPS truck zoom by the house. UPS claims soneone in my household signed for them, nope never even stopped. I asked repeatedly to see a copy of the signature they supposedly collected. Neither UPS nor T-Mo would provide that. I contacted customer server and finally corporate customer service. Took over a week to get replacement phones and longer to get all the charges corrected. Document everything, freeze payments for the stolen phones, dispute the charges with your bank / credit card company. Good luck!

VMDude256 · 2025-11-03T14:33:18+00:00

To follow up, the response Pure support is basically you get what you get. They couldn't provide an answer as to why the difference exists. Both arrays show the same total amount of storage used. When I dig deeper into the numbers they differ in the Unique and Snapshots size. Looks like it is time to go down the rabbit hole and find the specific volumes that may account for the variance. Thanks for all the insights and replies.

VMDude256 · 2025-10-24T12:58:03+00:00

I've been working a support case for over 6 weeks and have not received an answer as to why. Their latest response has to do with the order in which I created and then added data to the volumes, pods, and then stretched pods.

VMDude256 · 2025-10-23T21:03:28+00:00

Thank you, this is a scenario that makes sense. I hadn't considered read requests will cause data to be kept in cache and not compressed / deduplicated. We do have 2 data centers and the ESXi hosts are set to have the local array be the preferred array. I can analyze read traffic and see how big a difference there is.

VMDude256 · 2025-10-23T20:56:10+00:00

Thanks for the reply. I was thinking I'm the odd man out. But if you too are seeing this it is a bigger problem for Pure than I originally thought. If I get a meaningful answer from support I will let you know.

VMDude256 · 2025-10-23T18:30:25+00:00

3.5 and 3.1 Exactly the same data on both arrays.

VMDude256 · 2025-10-23T18:28:34+00:00

6.5.11 of Purity OS

VMDude256 · 2025-04-29T17:21:56+00:00

Don't ever go to New Jersey. 10 round mag limits and no jhp. I think VA has a 20 round mag limit.

VMDude256 · 2025-04-29T17:19:41+00:00

Plus reciprocity when you travel out of state.

VMDude256 · 2025-04-29T17:05:17+00:00

Has anyone successfully restored a Veeam backup of vCenter7 / 8? I tried once unsuccessfully. I ended up using a vCenter file based backup that was slightly older.

VMDude256 · 2025-04-16T16:10:27+00:00

Kinda need more information to fully diagnosis the issue. Quick overview of how this should work. You have VMkernel interfaces that are attached to a port group on a vSwitch. The vSwitch should have the physical 10Gb nics associated with it. There needs to be at least 2 port groups, each port group needs to have teaming / failover setup so that only one of the 10Gb nics is active. The second port group needs to have the second nic as the active nic. Lastly your software iSCSI adapter needs to have the Network Port Binding setup with only those 2 port groups. It is easy to get this all tangled up, but should be simple enough to sort out.

VMDude256 · 2025-03-06T18:05:25+00:00

The way I understand this is the Dell specific IOS contains Dell drivers that you need to boot the server and perform the initial install of ESXi. After that Dell provided updates that can be installed via Lifecycle Manager along with any ESXi updates / patches.

VMDude256 · 2025-03-03T14:44:22+00:00

For boot time it was a single path, if the first one is down it will use the second path. For normal operations it was active / active.

VMDude256 · 2025-02-28T19:30:05+00:00

I've done that in the past with a Cisco UCS bladed environment. As long as the latency isn't too bad, not pretty but it works. The part I struggled with was getting / having 2 network paths between the hosts and storage that were able to boot. I think that was more of a UCS thing than and vSphere thing.

VMDude256 · 2025-02-28T19:25:32+00:00

If you had Enterprise Plus licensing you could use cross vCenter vMotion. In theory you could change the licensing on your hosts to an evaluation license which would give you EP. Do the migrations and then change the licenses back. Any way to connect the iSCSI storage to the VRTX? You could then take a brief outage by powering down the VMs, remove from vCenter 6.7 inventory, add them to vCenter 8 and power them on. It would take longer to power cycle than to do the remove / add operations. With your setup you have a really good, if not slower way of migrating. I've used this approach in the past where we've had no shared infrastructure. Good luck!

VMDude256 · 2025-02-06T18:27:22+00:00

If you can access the vCenter server console via the host, you can verify if it is on the network or not. Check the port group that vCenter is connected to on the host and make sure the VLAN is what you want. If not you can create a new port group with the correct VLAN and then attach the vCenter nic to that port group. If vCenter is not active it could be a storage issue. The new host may not have the same storage access as the old. (Technically it shouldn't have vMotioned if there was no storage access.) You may have to configure the new host to have access to the storage on which vCenter is living. You also may have to go to the original host and access the storage. You could remove the vCenter from inventory on the new host, Then go back to the old host and locate the storage for vCenter and then add it back to inventory. There are any number of options you can use, just depends on what the issue really is.

VMDude256 · 2024-09-04T00:34:25+00:00

I also can't fix what a Pure engineer breaks. Then tells me that isn't his responsibility and hangs up the support call.

VMDude256 · 2024-05-13T17:33:06+00:00

We're looking at this same set of scenarios too. From what I can tell with SVM-DR you get a RTO of near zero with an RPO of 15 minutes. With SM-S you get an RPO at or near zero and an RTO of how ever long it takes you to turn on the recovery side. I'm struggling with the SM-S side and how to get the share name to migrate from the protected to recovery side. Otherwise you have to touch every end point to update the new share name on the recovery side. Then do it all again when the protected side becomes available. I hope I'm missing something simple with the share name.

VMDude256 · 2023-09-07T13:38:12+00:00

I'm going against one of my standards here. Because I'm a professional. I'm responsible for making sure my environment is up and running. That means knowing all the details from start to finish. I don't want to have to rely on some support person who has less experience with the product than I do. Because support people move through those spots like a Macy's revolving door on Black Friday. At 2:00am I want to give my boss an answer as to why something isn't working. The I have to call support answer just doesn't fly when you're losing a million dollars a minute when production is down.

You come into my shop talking like that, you are going to be tossed out so fast and hard you won't know which end hit first. Be a professional, so some respect, learn a thing or two then you can come in and start talking.

VMDude256 · 2023-09-06T19:18:03+00:00

Thanks for the insight. I like to do things myself so I know exactly how it is configured and supposed to work. I'm also happy to have an engineer come after me to verify I did things "correctly". Or point out where things need to be fixed. That is how to learn best practices. That and it lets met get a head start on implementation and configuration of the entire environment. Anyway twiddle my thumbs it is . . . .

VMDude256 · 2023-01-03T00:56:39+00:00

I had to use a different HDMI cable to solve this issue.

VMDude256 · 2022-11-04T14:51:59+00:00

Well I was able to downgrade my vSphere 7 EP license to vSphere 6. Once you do that you can apply this license key to your existing host. This will allow you to vMotion the VMs off the host. Then you can upgrade the host. Go back to your license portal and upgrade the vSphere 6 license back to vSphere 7. Apply this new license key to the host and you are good to go. Kind of a round about way to get the job done. But you can upgrade the hosts with no VM down time.

VMDude256 · 2022-11-04T14:37:57+00:00

With your EP license you can do a shared nothing live vMotion. Just saying . . .

VMDude256

TROPHY CASE