Jul
06

Recovery Points and Schedules with Near-Sync on Nutanix

Primer post on near-sync

For the GA release near-sync will be only offered with a telescopic schedule (time based retention). When you set the RPO <=15min to >=1 min you will have the option to save your snapshots for X number of weeks or months.

As example if you set the RPO to 1 min and schedule 1 month retention it would look like this:

X= is the RPO
Y = is the schedule

Every X min, create a snapshot retained for 15 mins (These are the Light-Weight Snaps. They appear as normal snap in Prism)
Every hour create a snapshot retained for 6 hours.
Every day, create a snapshot retained for 1 week
One weekly snapshot retained for 4 weeks (If you select a schedule to retain for 7 weeks, Y would be 7 weeks and no monthly snap would occur)
One Monthly snapshot retained for Y months.

Subject to change, as we’re still finalizing sizing and thresholds based on real-world testing but the user will have an option to change these retention values via NCLI.

SCHEDULE

Jul
06

Delete AFS Forcefully

There can be instances when graceful removal of file server does not work and you may see following errors, this can happen when the file server is not available and has been deleted without following the right process. Sometimes the FSVMs get deleted instead of using the delete workflow in file server section of Prism.

ncli fs delete uuid=________________________
Error: File server with uuid xxxxx-xxxxx-xxxxx is offline and unable to fetch file server VMs.

Use the following command to delete the file server permanently from the Minerva Database. This is run from any CVM.
minerva –fs_uuids _________________ force_fileserver_delete

file server UUID can be obtained from ncli fs ls command.

Jul
05

Powering Off and Starting Up AFS – Native File Services on Nutanix

There really isn’t a need to shut down AFS but moves and maintenance are a part of life. Here are the steps for a clean shutdown….

-DL

Shutting Down:
• Power off all guest VMs on the cluster, leaving only FSVM’s and CVM’s powered on.
• From any CVM run: minerva -a stop
• The stop command will stop AFS services and power off the FSVMs for all File Servers
• Once only the CVM’s remain powered on, run Cluster Stop from any CVM.
• Power Off the CVM’s and Hosts

Starting Up:
• Power on Hosts
• CVMs will auto-start once the Host is up
• Once all CVMs are up, run Cluster Start to initiate cluster services
• Verify all services are up with Cluster Status
• From any CVM run: minerva -a start
• The start command will power on the FSVMs for all File Servers and start AFS services
• Power on all remaining guest VMs

BmPPOTXIcAA1jBj