Recent Content
Hi Guys - a customer has pointed out some confusing information regarding FA, ESXi ISCSI and port binding
According to https://core.vmware.com/resource/best-practices-running-vmware-vsphere-iscsi#sec7262-sub12 port binding is unsupported if the FA has iscsi-interfaces in 2 subnets. On https://support.purestorage.com/Solutions/VMware_Platform_Guide/User_Guides_for_VMware_Solutions/FlashArray_VMware_Best_Practices_User_Guide/VMware_and_iSCSI_FAQs#NIC_Teaming_vs_Port_Binding.2C_which_should_I_use.3F|https://support.purestorage.com/Solutions/VMware_Platform_Guide/User_Guides_for_VMware_S[…]ay_VMware_Best_Practices_User_Guide/VMware_and_iSCSI_FAQs it is stated "So which should you use? The answer here is clear, port binding whenever possible. This is not only recommended as a best practice with Pure Storage but by VMware as well."Solved77Views0likes12CommentsIs the concept of "refreshing" volume groups possible
Is the concept of "refreshing" volume groups possible on an existing copy of a volume group? Let me rephrase. Say I setup a volume group (VG) of 24 volumes (PRD01) that are for a production database. I want to snapshot that group of 24 volumes and create a copy of it to repurpose as a prod support DB copy (COPY01) and another copy to mount on another server to get backed up (COPY02). When its time to backup the server again can I refresh the data of PRD01 group to COPY02?68Views0likes18CommentsDoes anyone have any advice for stork pods that keep restarting
Does anyone have any advice for stork pods that keep restarting with: ``` Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x29aad38]``` I'm running storkctl Version: 2.7.0-2e5098a and k8s version 1.22.5Solved51Views0likes14Comments