Looking for:
SnapDrive, SnapManager, and SnapCenter - FlackBox |
Snapdrive for windows free download.NetApp SnapDrive For Windows
Steps 1. Review the system requirements and the Interoperability Matrix at support. Prepare each Windows host in your SnapDrive configuration. Prepare each storage system in your SnapDrive configuration. Set up your user credentials for SnapDrive. Install or upgrade the FC or iscsi components. If you are upgrading an existing SnapDrive installation, perform the recommended upgrade preparations.
Install the SnapDrive components. You can use these components together to enable SnapDrive workflows, including provisioning, Snapshot copy management, backup, restore, and mounting operations. The following SnapDrive components are integrated in the software and are automatically installed during installation. The module does the following: Resides in the Windows Server computer management storage tree Provides a native MMC snap-in user interface for configuring and managing LUNs Supports remote administration so that you can manage SnapDrive on multiple hosts Provides SnapMirror integration Provides AutoSupport integration, including event notification SnapDrive command-line interface The sdcli.
You can perform the following tasks with the sdcli. SnapDrive supports PowerShell versions 2. Underlying SnapDrive service This software interacts with software on the storage system to facilitate LUN management for the following: A host Applications running on a host.
Note: For the latest system requirements information, see the Interoperability Matrix at support. NET Framework 3. NET Framework 4. SnapDrive licensing Your SnapDrive license can reside either on the local host or on the storage system that you are using SnapDrive to manage. Storage system licensing enables you to execute SnapDrive operations only on a storage system that has the SnapDrive license installed. Host-side licensing enables you to execute SnapDrive on any SnapDrive instance on your host system.
SnapDrive 7. You are required only to set up your virtual storage server credentials. You are required to have SnapRestore and FlexClone licenses before setting up your virtual storage server credentials.
You should be. Verify that the host meets the minimum requirements for use with SnapDrive. Determine whether the Microsoft iscsi Software Initiator program is installed. If you are running Windows Server , the iscsi Software Initiator comes built in with the operating system, but you must enable it.
Determine whether SnapDrive has been previously installed. Verify that the storage system meets the minimum requirements for use with SnapDrive. After you verify that licenses for FC, iscsi, or both are enabled on your storage system, you must start the services by entering the fcp start command or the iscsi start command at the storage system command line. How volume space is used SnapDrive uses space on a storage system volume for LUNs and their data, and also for the data that changes between Snapshot copies, the LUN's active file system, and for metadata.
Volume size rules Storage system volumes that will hold LUNs must be large enough to hold all the LUNs in the volume, as well any Snapshot copies if Snapshot copies are created.
The following factors govern the appropriate minimum size for a volume that holds a LUN: If the LUNs are space reserved, then the volume must be more than twice the combined size of all the LUNs on the volume if a Snapshot copy of the volume is created. This enables the volume to hold the LUNs in a fractional reservation area. No matter how much the contents of the LUNs change between Snapshot copies, the entire contents of the disks are written to the volume. The volume must also provide enough additional space to hold the number of Snapshot copies you intend to keep online.
The amount of space consumed by a Snapshot copy depends on the amount of data that changes after the Snapshot copy is taken. The maximum number of Snapshot copies is per storage system volume.
Key points when SnapDrive checks and resets options: When you start SnapDrive When you create a LUN When you connect a LUN to a host The following table shows the defaults that are reset and when those resets take place; you should not change these values. Reservations are an attribute of the LUN; they are persistent across storage system reboots, takeovers, and givebacks.
If these operations do not have sufficient unreserved free space, they fail. However, writes to the LUNs with reservations enabled continue to succeed. You can enable reservations for LUNs contained by volumes with volume guarantees of any value.
However, if the volume has a guarantee of none, reservations do not provide protection against outof-space errors. Disk space usage with space reservation When space reservation is enabled, the amount of space available on a volume containing LUNs determines whether Snapshot copy creation can take place.
When you first create a LUN with space reservation enabled, it is granted a space reservation equal to its size. This reserved space is subtracted from the total available disk space on the storage system volume on which the LUN resides. When you create a Snapshot copy of the storage system volume holding the LUN, that Snapshot copy locks down all the disk blocks occupied by live data.
By monitoring the remaining available space in the storage system volume, the available space in the volume determines whether Snapshot copy creation is allowed. When the amount of available space on the storage system volume falls to below the threshold you set to prevent overwriting space reserved LUNs, Snapshot creation is blocked. Considerations for setting fractional reserve Fractional reserve, also called LUN overwrite reserve, enables you to control the size of the overwrite reserve for reserved LUNs and files in a volume.
By using this volume attribute correctly you can maximize your storage utilization, but you should understand how it interacts with other technologies. The fractional reserve setting is expressed as a percentage; the only valid values are 0 and percent. Setting fractional reserve to 0 increases your storage utilization. However, an application accessing data residing in the volume could experience a data outage if the volume is out of free space, even.
In addition, you can optionally use the volume autogrow capability to decrease the likelihood of volume Snapshot copies needing to be deleted automatically. If you enable the autogrow capability, you must monitor the free space in the associated aggregate. If the aggregate becomes full enough that the volume is prevented from growing, more Snapshot copies will probably be deleted as the free space in the volume is depleted.
If you do not want to monitor aggregate free space or have volume Snapshot copies automatically deleted, you can set the volume's fractional reserve setting to This requires more free space up front, but guarantees that data modification operations will succeed even when the technologies listed above are in use. The default value and allowed values for the fractional reserve setting depend on the guarantee of the volume: Volume guarantee Default fractional reserve Allowed values Volume 0, None 0 0, File.
You accomplish this by providing the name for the vfiler unit rather than the name of the physical storage system to create a connection. It is transparent to the host whether the attached storage system is a physical storage system or a virtual vfiler unit. Note the following restrictions to MultiStore support: SnapDrive is supported on vfiler units only when using the iscsi protocol.
SnapDrive service account requirements To perform functions related to SnapDrive for Windows on either the host or a storage system, SnapDrive must be able to use a service account that has specific types of access established. You must be able to log in to the host using the service account. Note: If you change the password for this account for example, from the Windows login panel , you must make the same change to the password that the SnapDrive service uses to log in.
The service account must have administrative rights on the host. If you are using RPC, the service account must be a domain account, or you can configure passthrough authentication.
If you are using RPC, the host and storage system must belong to the same domain as the service account or to domains that have direct or indirect trust relationships with the domain to which the service account belongs, or you can configure pass-through authentication. This feature, along with CIFS share dependency removal, enables you to perform SnapDrive-related operations without having root access on the storage system.
It also enables you to set a default transport protocol in case one has not been specified for individual storage systems. The httpd. Using the domain administrator account for authentication results in significantly reduced performance. To avoid this issue, you must use a storage system account for authentication instead of the domain account.
Setting up your group Managed Service Account on Windows Server Windows Server enables you to create a group Managed Service Account gmsa that provides automated service account password management from a managed domain account.
Setting up a gmsa eliminates the need for administrators to manually administer passwords for these accounts. Before you begin You have a Windows Server domain controller. You are a Windows Server domain member with permissions to set up and administer the gmsa. About this task You cannot use a gmsa on storage systems configured with RPC protocol settings.
Create a KDS root key to generate unique passwords for each object in your gmsa. Create and configure your gmsa: a. Create a user group account with administrator and domain administrator privileges. Add computer objects to the group. Configure the gmsa on your hosts: a. Enable the Active Directory module for Windows PowerShell on the host where you want to use the gmsa account. To ensure that your newly-installed role or feature is automatically updated, turn on Windows Update.
Restart your host. Configure SnapDrive with your new gmsa account by installing your SnapDrive service without providing a password. Pass-through authentication might be required in the following situations: You do not have a domain controller available. You want to install your Windows host as a stand-alone server in a workgroup environment without any dependency on another system for authentication, even if there is a domain controller available.
Your Windows host and the storage system are in two different domains. Your Windows host is in a domain and you want to keep the storage system in a workgroup with no direct access by domain users or the domain controller.
Configuring SnapDrive pass-through authentication If you are using RPC authentication, you must ensure that pass-through authentication is configured correctly for SnapDrive on both the Windows host and on the storage system. Before you begin You must have root privileges on the storage system.
You must have administrator privileges on the Windows host. If you have a clustered SnapDrive configuration, you must use a domain account to run the cluster service, and all nodes of the cluster must be in the same domain.
However, the storage system can be in a different domain or workgroup. Therefore, make a note of the user name, including the letter case lowercase or uppercase of each character in the user name.
No comments:
Post a Comment