#SnapCenter 6.0 MaxDB
1 messages · Page 1 of 1 (latest)
https://docs.netapp.com/us-en/snapcenter/protect-nsp/netapp_supported_plugins_overview.html In 6.0 they are included in the installation and you do not need to download them from another location.
Wow 🤩 Great!
I would stay away from 6.0 and 6.0.1 if you can for now. We have to reboot sc once a week now as there's a memory leak that crashes sc. I think a new version is coming.
Thanks 🙏
@tough wadi new version coming 6.1 31 Jan apparently.
@crystal gale thanks 👍 our SnapCenter Consultant will not be amused because he is currently updating all SnapCenter Instances to 6.0
@tough wadi good luck! I know there's other customers with the same issues I got. Hopefully you don't get it. Also don't update if you got any legacy hosts 2012.
@crystal gale any feedback on snapcenter on Linux.. any major issues you aware of..
@spice crown only use snapcenter for sql on windows servers. Up to 2022. Standalone vmware datastore sql servers fine and consolidated sql servers using iscsi is fine physical/virtual.
Ok.. and snapcenter 6.1 coming Jan 31 tomorrow ? I was about to install 6.0 stopped myself after seeing your message
Not sure if you want to install a version 1 day after release. Depending on how much changed with 6.1 I would at least wait 2 weeks.
@spice crown if you got no issues at present I would wait a while until feedback on 6.1. 6.1 should have the the bug fixes everyone is screaming out for. I had to reboot sc today sametime every week. Backups schedules just stop. So no choice need to upgrade. First though introducing a dev sc with a 2012 host to test if 2012 will still work using plugin 5.0 using sc 6.1. Obvs not supported but at least we have backups until the business moves the last 2012 servers to 2022. Nightmare... only upgraded previously due to another team virtualisation gun ho on updates
@near bobcat yeah see my update. Depends if you hit the weekly sc stops working issue
@spice crown hearing some noise on the website via pro service's should be tomorrow or shortly
SC 6.1 just got released!
Feature-wise nothing much new, but the bugfixes look promising.
Guess that's the one you're looking for?
@near bobcat yep just reviewing now and the other major bug csnapc-5385. Svm added as fqdn. Discovery of storage fails. Had to remove and readd two svms once a week as it drops the registration after snapcenter dies once a week from bug csnap-7219
The snaplock to secondary is a good addition to achieve immutable using sc for your vaults
The "Svm added as fqdn" should already be fixed in 6.0.1. At least Netapp mentioned that in a call I had.
@near bobcat when snapcenter dies I have to register both svms that I use for vmware datastores location. Only once a week. So don't know if it's part of that fix that's not working
After the stability of SnapCenter 4.7 to 4.9 increased slightly, we are now back in the time of SnapCenter 4.0 4.1 and so on. I can't understand the QA and I also don't understand the management why SnapCenter is developed so badly. What is the reason?
The current problem with the update strategy also no longer works. Hardly any P releases are developed, but always the next version. It's just stupid if you want to update from SnapCenter 5.0 to 6.0, for example, so that you can update the plugins bit by bit. The release 6.0 brings so many problems that this is not an option. So now you have to update directly to 6.1 so you have to update all plugins in the same maintenance window and hope that this works so far. What do you think?
@deft wigeon hmm lol I created a test sc starting off from 5.0p2 to 6.0.1. Lucky I did a delta snapshot as it died 😆 so did staged to 6.0 to 6.0.1 that worked OK for the wizard. Upgraded to 6.1 but for some reason the install needs a kick eg. Reboot the server or end task and rerun. So many bugs previously such as going to 6.0 from 5.0p2 required .net sdk reinstall after the sc install. But anyway 6.1 seems OK so far in test environment and works with windows 2012 with plugging 5.0 not upgraded. (Obviously not supported but it works!) If the test environment stays up over one week will upgrade in two weeks.
A lot of the bugs were to do with zapi to rest api. Again been there got the 👕