SnapCenter 6.x Upgrade Issue

[TMADOCTHOMAS]

I'm about to upgrade our SnapCenter infrastructure from 5.0P2 to 6.1P1, with the exception of five SQL Servers running Windows Server 2008R2 and 2012R2 [and yes we are pushing them to migrate to new servers]. Those Windows versions can't run SC 6.x [or for that matter some of the new prerequisites like the new PowerShell version requirement].

The problem: I just discovered that the IMT indicates that both 6.0.1 and 6.1 running on the SC server is not compatible with 5.x Windows or SQL plug-ins. I could upgrade only to 6.0 I suppose, which can run the Windows 5.x plug-in and possibly the SQL one [I say possibly because the online documentation and IMT for the plug-in say the SQL 5.x plug-in is compatible, but the IMT for the server says it is not].

Any suggestions? Is 6.0 sufficiently stable without going to 6.0.1 or 6.1? Is 6.0 in fact compatible with the SQL 5.x plug-in?

[PravinKumar]

Hi Tim,

Yes, you can upgrade SnapCenter to 6.0 and keep the plugin 5.0P2 Servers running Windows Server 2008R2 and 2012R2.

Refer to the SnapCenter 6.0 release notes under section: Supported upgrade paths : https://library.netapp.com/ecm/ecm_download_file/ECMLP3323468

SnapCenter 6.0.1P1 and 6.1 P1 has below bugs are fixed:

6.0.1P1 Release:

Key         Summary  

CSNAPC-5385 Fix for ONTAP SVM/vServer name resolution issue.  

CSNAPC-7216 SnapCenter upgrade error out with schema error.  

CSNAPC-7046 After upgrading to SCE6.0, LastFullBackup on exchange server doesn't update if backup is taken on passive node  

CSNAPC-6293 SCO non-root user clone fails when login banner contains dynamic values.  

CSNAPC-5476 SCO clones fail intermittently when junction Path for the newly created clones are not present in Zapi Response.

CSNAPC-7506 Ignore OMS and agent entries from oraInventory file.  

CSNAPC-7885 SCO 6.1 Resource group backup fails for ASM over NFS setup  

CSNAPC-7017 SCO RAC Upgrade : Schedules are not running.  

CSNAPC-6437 After SC 6.0 upgrade unable to list policies during modify Oracle RAC resource  

CSNAPC-7219 SnapCenter 6.0.1 : Intermittently MySQL service pegging the CPU at 99%.  

CSNAPC-7433 Memory issue for SCW service after upgrading to SC6.0 in clustered setup  

CSNAPC-7558 SC F5 HA : Scheduler Restart Failure with error " SnapCenter Server is unable to restart Scheduler service"  

CSNAPC-6886 Windows SC F5 HA : "RabbitMQ Connection Failure" alerts are thrown.  

CSNAPC-7535 SC on LINUX HA : RabbitMQ alert seen when upgraded from SC 6.0 or SC 6.0.1  

CSNAPC-6739 SC HA replication fails in windows after upgrading to SC6.0.1  

CSNAPC-7588 Snapcenter_RemoveSecondaryBackup is not Creating Jobs or Populating Fields in SC UI  

CSNAPC-7945 Clean-up Secondary Backups job fails when triggered from SC GUI after upgrading to SC6.1

CSNAPC-7861 SCSQL backup fails due to "The target principal name is incorrect" when Force Encryption is set to True after upgrading SnapCenter to 6.0  

CSNAPC-5973 SCSQL backup fails if Force Encryption is set to True in SQL Server  

CSNAPC-6502 SnapCenter 6.0 generates psd1, psm1, and ps1xml files in the temp directory when running SCSQL backup job with MSCS. 

CSNAPC-6519 SnapCenter 6.0 Audit log integrity check failure issue  

Known Issue    

CSNAPC-6554 When installing or upgrading SnapCenter from version 5.x to 6.0, SnapCenter installs RabbitMQ and Erlang, adds the host, adds the user, and sets permissions for the host.

If there is a mismatch between the default Windows user home directory and the home directory environment variables (HOME or HOMEDRIVE and HOMEPATH) due to a mapped network drive or virtual drive, the upgrade from SnapCenter 5.x to 6.0 will be successful, but the RabbitMQ configuration will not be completed.

6.1P1 release:

The SnapCenter 6.1P1 release includes both bug fixes and security updates. Please note that this release also includes issues fixed in SC 6.0.1P1. For more details, please refer to the README notes.

Bug ID         Description

CSNAPC-6554  SnapCenter upgrade from 5.x to 6.0 was successful but RabbitMQ configuration didn't happen.

CSNAPC-8140  SCO: When ASM FD is disabled SnapCenter backup fails

CSNAPC-8125  [Supportability] Provide options to re-run migration of existing schedules in SnapCenter

CSNAPC-8126  SCO: When the listener is set to clone fails

CSNAPC-7864  Improve SnapCenter Retore Performance.

CSNAPC-3855  SQL-NFS restore is not working post storage tech refresh with the old backups

CSNAPC-8177  ANF Backup: Clean up stale snapshot entries from SnapCenter Metadata as part of VBSR operation.

CSNAPC-6471  Supportability: The SCC DB2 Plugin logs, all DB filenames during discovery leading to unnecessary big log files

CSNAPC-8180  Secondary TPS should work independently of Primary TPS

Release notes:  https://library.netapp.com/ecm/ecm_download_file/ECMLP3337665

Thanks and Regards,

Pravin Kumar

[TMADOCTHOMAS]

Thank you very much @PravinKumar ! I had seen that in the documentation, however the IMT provides inconsistent information. As I said:
----------------
I say possibly because the online documentation and IMT for the plug-in say the SQL 5.x plug-in is compatible, but the IMT for the server says it is not
----------------
So even though the documentation says it should work, the IMT indicates specifically that the SQL 5.x plug-in is not compatible. I'm guessing that's likely inaccurate but don't know for sure. That's what I'm trying to find out in this post.

Regarding the release notes, are those release notes for just the patches - i.e. does this describe what P1 patched in 6.0.1 and 6.1, or does it describe what the original 6.0.1 and 6.1 patched from 6.0 [if anything]?

[PravinKumar · Accepted solution]

Hi Tim,

Please find the IMT report attached for  Snapcenter 6.0 with Snapcenter plugin for SQL 5.x , it confirms supported.

All are different versions from 6.0 -> 6.0.1 -> 6.1.  P1 patches are respective patches for those specific versions. Yes release notes covers the P1 patch details.

Please let me know if you have any further queries.

Have a good day!

Thanks and Regards,

Pravin Kumar

[TMADOCTHOMAS]

Excellent, thanks @PravinKumar !