HIBERNATE · DATA OUT TO S3NC2 NODESRESUME · DATA BACK FROM S3YOUR RESTORE RATEnot enteredfrom your docs · not a Nutanix number-DATAS3 OBJECT STORENO RATE-TARGET

Reported (the lab's record of the public Nutanix blog, which we opened): Nutanix states that NC2 preserves cluster data and metadata by backing it up to Amazon S3 while the bare metal nodes are shut down, and positions hibernation for clusters that are not in use — test and development environments idle at weekends, or disaster recovery where recovery point objectives are a day or more. source The blog gives no restore rate and no resume duration, and carries a 2022 notice.

Not opened: the Nutanix Support portal limitations and resume documents are behind a sign-in. No rate, duration or figure from them appears here, and this figure ships no default restore rate.

Ours: The clock assumes the whole dataset must rehydrate before the cluster counts as back; that is our model, not a Nutanix statement. The rate is one aggregate number for the whole cluster, as your documentation states it; no per-node multiplier is applied. An RPO measured in days is a strong hint that the round trip is not quick; that is our reading, not Nutanix's.

The data ticket: out to S3 on the back lane, home on the front laneMetering gate: opens with YOUR rateHydrate time inside your targetHydrate time past your targetHow long you were hibernated (optional)No rate has been entered, so there is no clock and no verdict. Whatever the rate is, this dataset needs at least 6.25 TB per hour to be back inside 8 h. The rate is your own input from your current documentation. It is not a Nutanix or CloudLab number. The clock assumes the whole dataset must rehydrate before the cluster counts as back; that is our model, not a Nutanix statement.