A media company replaced a failed fabric interconnect, and an XML export of service profiles, pools, and policies did not restore the interconnect system state. Which backup is built for that restore?
Select an answer to reveal the explanation.
Short Explanation
You kept the furniture list and then wondered why it would not rebuild the whole building. You need the full-state backup, because that binary snapshot is what restores a fabric interconnect's system state. A logical export is the inventory of profiles, pools, and policies, and renaming the file does not turn it into that snapshot.
Full Explanation
UCS Manager full-state backup is a binary snapshot of a fabric interconnect, including the system state needed for a domain restore. A logical configuration export is XML that describes service profiles, pools, policies, and templates. It is the right file for recreating those objects on a healthy domain, and it is not a substitute for the binary snapshot this media company needed after the interconnect failed. Saving the logical XML under a different name does not change its contents into a full-state backup. A host firmware package updates server components such as BIOS and adapters. It does not restore an interconnect configuration database, and it is not a backup format. The chassis discovery policy tells the domain how to bring a chassis online. It is not a stored copy of cluster state for both interconnects. Caveat: a full-state restore is disruptive and has to match the restore procedure for that domain, so it is a poor way to copy a handful of service profiles onto a system that is already up. Operational check: confirm a recent full-state file exists from the domain, use that file for the interconnect restore, and verify the cluster comes back before you rely on the logical XML alone.