StarWind Software

We have a client that is using the HCI Appliance and is wanting us to backup the configuration. I have found online that you backup the files but I am not seeing this anywhere in the software, so with that I am not sure if its a version issue or what. The client is using version 1.5.460.5391+76fc51b do we need to upgrade them to another version to get the backup config options?

Hi,

Updating is doing the backup of the config files, yet backing up the configs is not the intended use of the update.
Could you please let me know what is the intention? If the main purpose is updating, you are welcome to update. If you would like to back up the configuration, see https://www.starwindsoftware.com/best-p ... practices/.
Also, you need to copy the following files: StarWind.cfg, /headers contents, hba_rescan.conf, and network configurations. StarWind.cfg and /headers contents can be pulled out by log collection.

I am working an older ticket from someone that used to work for us. In the ticket he stated "I reached out and had a call with Starwinds they have passed this over to R&D and there is currently now backup feature within the GUI." So I guess I am looking at how we do the backup feature within the GUI. I didnt see that as an option anywhere. Is this something that is maybe in one of the updates beyond where we are currently?

Many thanks for your update!
Can I please have the case number?
Could you please rephrase your request? Is it related to the integration of the backup software or solely backing up the config files? Or, does it relate to backing up the config files only during the update?
The config files can be fetched through the log collection. The only time you will need them is when the VMs are heading towards the redeploy.
StarWind.cfg is backed up during the update.

Sorry don't have a case number as this is an old ticket with us. I am trying to clean up some old ones and get them closed out. I am thinking they were wanting to backup the configs to store them offsite incase something happened and we would need to reinstall for some reason.

Thanks for your update! Please make sure to copy the files I mentioned earlier.

This is my first time touching these for the client. Is there a guide to where or best way to back these files up? I have been looking for the files through ssh for the past 20 minutes but have come up empty.

There is no guide.
Copy the following files/directories to the logs.
cp /opt/starwind/starwind-virtual-san/drive_c/starwind/hba_rescan.conf /opt/starwind/starwind-virtual-san/drive_c/starwind/logs
cp -a /etc/netplan/ /opt/starwind/starwind-virtual-san/drive_c/starwind/logs
cp /etc/fstab/ /opt/starwind/starwind-virtual-san/drive_c/starwind/logs
Finally, You need to pull the CVM logs in the standard way (Log in to the Web management interface -> Select the gear-shaped button -> Expand the VM name view -> Support Bundle). Check that the files you attempted to pull out are in the log bundles (they should be under /opt/starwind/starwind-virtual-san/driv_c/starwind/logs in the archive)

Last but not least: please make sure to follow backup best practices and have solid backups https://www.starwindsoftware.com/best-p ... practices/. Solid backups of your production VMs are the only thing you can count on in case of encryption.

/opt/starwind/starwind-virtual-san/drive_c/starwind/hba_rescan.conf
- This does not exist I only see hba_rescan.ps1 and hba_rescan.py

cp -a /etc/netplan/
- Found this directory

cp /etc/fstab/
- Found this file

It exists only in the Ubuntu-based CVM.
there should be a file with *.conf at the end, or it is a very old CVM, and you need copy the *.py file.

Ok got all the files in the log directory and kicked off the support bundle. Do you know if this takes a while before you see the files? I am not seeing anything in the log directory.

The log collector pulls the entire /logs directory. Make sure you've copied the files/directories there.

As a side note, CVM, in its current state, does not allow re-using old data in the new VM deployment that straightforward. We are working on it.