SnapCenter Software 5 Manuals ( CA08871-403 )

to Japanese version

Prepare for Snapcenter Server and Plug-in installation

Provides a condensed set of preparation instructions for installing the SnapCenter Server and the SnapCenter Plug-in for Microsoft SQL Server.

Domain and workgroup requirements

SnapCenter Server can be installed on systems that are either in a domain or in a workgroup.

If you are using an Active Directory domain, you should use a Domain user with local administrator rights. The Domain user should be a member of the local Administrator group on the Windows host.

If you are using workgroups, you should use a local account that has local administrator rights.

License requirements

The type of licenses you install depends on your environment.

License Where required

SnapCenter Standard controller-based

Required for FAS or AFF storage controllers

SnapCenter Standard license is a controller-based license and is included as part of the premium bundle. If you have the SnapManager Suite license, you also get the SnapCenter Standard license entitlement. If you want to install SnapCenter on a trial basis with FAS or AFF storage, you can obtain a Premium Bundle evaluation license by contacting the sales representative.

SnapCenter Standard capacity-based

Required with ONTAP Select and Cloud Volumes ONTAP

If you are a Cloud Volumes ONTAP or ONTAP Select customer, you need to procure a per TB capacity-based license based on the data managed by SnapCenter. By default, SnapCenter ships a built-in 90-day 100 TB SnapCenter Standard capacity-based trial license. For other details, contact the sales representative.

SnapMirror or SnapVault

ONTAP

Either SnapMirror or SnapVault license is required if replication is enabled in SnapCenter.

Additional licenses (optional)

SnapCenter Standard licenses (optional)

Secondary destinations

It is recommended, but not required, that you add SnapCenter Standard licenses to secondary destinations. If SnapCenter Standard licenses are not enabled on secondary destinations, you cannot use SnapCenter to backup resources on the secondary destination after performing a failover operation. However, a FlexClone license is required on secondary destinations to perform clone and verification operations.

Host and port requirements

Hosts Minimum requirements

Operating System (64-bit)

Contact Fujitsu support personnel

CPU

  • Server host: 4 cores

  • Plug-in host: 1 core

RAM

  • Server host: 8 GB

  • Plug-in host: 1 GB

Hard drive space

Server host:

  • 4 GB for SnapCenter Server software and logs

  • 6 GB for SnapCenter repository

  • Each plug-in host: 2 GB for plug-in installation and logs, this is required only if plug-in is installed on a dedicated host.

Third-party libraries

Required on SnapCenter Server host and plug-in host:

  • Microsoft .NET Framework 4.7.2 or later

  • Windows Management Framework (WMF) 4.0 or later

  • PowerShell 4.0 or later

Browsers

Chrome, Internet Explorer, and Microsoft Edge

Port type Default port

SnapCenter port

8146 (HTTPS), bidirectional, customizable, as in the URL https://server:8146

SnapCenter SMCore communication port

8145 (HTTPS), bidirectional, customizable

Repository database

3306 (HTTPS), bidirectional

Windows plug-in hosts

135, 445 (TCP)

In addition to ports 135 and 445, the dynamic port range specified by Microsoft should also be open. Remote install operations use the Windows Management Instrumentation (WMI) service, which dynamically searches this port range.

For information on the dynamic port range supported, see Service overview and network port requirements for Windows.

SnapCenter Plug-in for Windows

8145 (HTTPS), bidirectional, customizable

ONTAP cluster or SVM communication port

443 (HTTPS), bidirectional; 80 (HTTP), bidirectional

The port is used for communication between the SnapCenter Server host, plug-in host, and SVM or ONTAP Cluster.

SnapCenter Plug-in for Microsoft SQL Server requirements

You should have a user with local administrator privileges with local login permissions on the remote host. If you manage cluster nodes, you need a user with administrative privileges to all the nodes in the cluster.

You should have a user with sysadmin permissions on the SQL Server. The plug-in uses Microsoft VDI Framework, which requires sysadmin access.

Top of Page