Diskxtender manual

This rollback feature recovers the database and releases the session lock automatically. The audit log contains any messages relating to the rollback. This is a review of storage group information we had already covered in an earlier module. These groups are called cascaded storage groups. The storage group with the other storage groups as members is called the parent. The storage groups, containing only devices, that is contained within the parent storage group is referred to as the child storage groups.

Only a single level of cascading is permitted. A parent storage group may not be a child of another storage group. Empty storage groups can be added to a parent storage group as long as the parent storage group inherits at least one device when the parent storage group is in a view. A parent storage group cannot inherit the same device from more than one child storage group. A child storage group may only be contained by a single parent storage group.

No parent storage group can be FAST managed. Masking is not permitted for a child SG which is contained by a parent SG already part of a masking view.

Masking is not permitted for the parent SG which contains a child SG that is already part of a masking view. A child SG cannot be deleted until it is removed from its parent SG. The example shows how to use both symaccess and symsg commands to create storage groups. Note that the symaccess command allows you to create the storage group and simultaneously add devices or child storage groups.

The symsg command allows one to create an empty storage group first and then populate it with devices or child storage groups. Here are some other commonly performed Storage Group operations. Storage Groups can be renamed if needed. The valid arguments for the slo and wl options are listed.

Of course the array should be configured with appropriate drives to support the SLO. Limits are set on a per-storage-group basis. The VMAX3 system then monitors and enforces against these set limits. Please take a moment to review them. They prevent applications from using more than their allotted share of VMAX3 front end resources.

TheparentSGmayalsohaveitsown assignedlimit. Also,theindividualchildSG limitsmaynotexceedtheparentsassignedlimit. The default mode is Never which implies a staticevendistributionofconfiguredlimitsacrosstheparticipatingdirectorsinthe. SettingthedynamicdistributiontoAlwayscausestheconfiguredlimitstobe dynamicallydistributedacrosstheconfiguredports,allowingthelimitsoneachindividual porttoadjusttofluctuatingdemand.

As an example if the mode is set to OnFailure in a two-director port group which is part of a masking view, both directors are assigned half of the total limit. If one director goes offline, the other director will automatically be assigned the full amount of the limit, making it possible to insure the application running at full speed regardless of a director failure. Onlyonelimitcanbesetperstoragegroup,anddevicesinmultiplestoragegroupscanonly adheretoonelimit.

NEVER is the default. Port groups contain front-end director and port identification. A port can belong to more than one port group. Ports can be added and removed. When a port group is no longer associated with a masking view, it can be deleted. These are some of the operations commonly performed on a Port Group. Port Groups can be renamed if needed.

An initiator group is a container of one or more host initiators Fibre WWNs. One cannot mix different types of initiators i. In addition, all child IG names added to a parent initiator group must contain the same Initiator type. If this is not set, then the first available LUN on each individual port will be chosen. These are some of the operations commonly performed on a Initiator Group.

Initiator Groups can be renamed if needed. A Masking View is created by associating one initiator group, one port group and one storage group. So a masking view is a container of a storage group, a port group, and an initiator group. When you create a masking view, the devices in the storage group become visible to the host. The devices are masked and mapped automatically. These are some of the operations commonly performed on Masking Views.

Note that the symaccess backup command will back up the entire VMAX3 masking database. This lesson covers host considerations related to storage provisioning. The port flags settings can be overridden at the initiator or initiator group level. This feature allows specific host flags to be enabled and disabled on the director port. After a flag is set for a group, it cannot be changed on an initiator basis. After VMAX3 devices have been provisioned to a host by the creation of a masking view, the operating system on the host must be made to recognize the device.

To accomplish this a SCSI bus rescan must be initiated from the host. The bus rescan commands vary from operating system to operating system. While they work reliably in most cases, they may not work for every version of a particular operating system.

That is why it is advisable to verify the accuracy of these commands by checking the vendor documentation. Since there are several flavors of commercially available Linux, there are a variety of ways that the SCSI bus on those systems can be rescanned. The methods documented here are taken from the Linux host connectivity guide.

The EMC commands are convenient to use but the vendor supplied commands are the most reliable. In the event a host adapter fails, or needs replacement, you can replace the adapter and assign a set of devices to a new adapter by using the replace action in the following form:. This lesson covered host considerations related to storage provisioning.

We will show how Unisphere is used to manage auto-provisioning groups. We also show the use of the Storage Provisioning Wizard which greatly simplifies storage allocation.

The hosts currently configured can be listed by clicking on the Hosts section button.. From Hosts view you can create new Hosts, Host Groups cascaded initiator groups or click on a Host and Provision Storage to the Host, set flags, delete, or view its details. The detailed view of a Host allows further actions. In order to provision storage to a Host we first use the Create Host Wizard to create the initiator group for the Host.

Click on the Create Host link to launch the Wizard. One can optionally click on the Set Host Flags button to override any port flag settings. This is continuation of the Create Host Wizard.

To set host flags one can click on the Set Host Flags button. One can choose to override any of the other port flags listed as well. In this example we are not doing any overrides. To view the details of a Host select the host in the host list view and click on View Details.

The Host has two initiators and no Masking views. The Consistent LUNs option is enabled. The Related Objects frame has various links depending on the Host.

Clicking on the Initiators link will show a listing of the initiators in the host. The Modify button allows one to add or remove initiators from an existing Host. Modify Host can be launched from the detailed view of a Host or from the hosts listing page. To remove an initiator select the initiator from the lower half of the dialog box and click on Remove.

To add a new initiator select an available initiator or type in the WWN in the Add initiators field and click on Add. The Provision Storage to Host wizard simplifies the process of provisioning storage to a host. The wizard will create the desired storage groups, port group and masking view. The storage groups are created with the required service levels, workload type and capacity. The wizard can create stand alone storage groups or cascaded storage groups.

The wizard is typically launched from the context of a host initiator group , either from the hosts listing or the detailed view of a host. In this example the Storage Provisioning Wizard has been launched from the context of an existing Host, hence the Host does not have to be specified. The title of the dialog includes the host we are provisioning to Provision Storage to sun Type in a name for the Storage Group to be created. One can specify different Service Levels for each child storage group.

In this example the Add Service Level button was clicked once. This created two request entries as shown. Type in the desired name for each of the Child Storage Groups. Use the Workload Type pick list to choose the desired workload type. Finally enter the desired number of volumes and the volume capacity for each storage group and then click Next. We can see that we have created the request for two child storage groups.

We have set the desired service level, workload type, number of volumes and volume capacity for each. The Avg. Response time column indicates the expected response time for the selected service level and workload type. Then click Next. In this example we are creating a new Port Group edit the name of the new port groups as needed. Click Next. Note that ports that an HBA are zoned to show up automatically. One can click on the Include ports not visible to the host to show all ports and choose them if necessary.

The wizard will show the Port Group recommendation dialog if the port selections do not match the recommendation. In our example we had chosen only two ports in the port group, hence the recommendation dialog pops up.

Click on OK to dismiss the dialog and continue with the provisioning process. On the review page click on the Run Suitability Check button to see if the array can meet the Service Level Objectives for the provisioning request. In order for the Suitability check to work the VMAX3 arrays must be registered for performance data collection. The Masking View name can be edited as needed. In this example the green check mark indicates that Service Level Objective for provisioning request will be met.

The Job has been successfully executed. The provisioning task will either find existing devices or create new devices as needed to satisfy the provisioning request. To see a listing of all masking views click on Masking View in the Hosts menu. Select the masking view and click on View Connections to see detailed information about the view. Storage group management is done via the Storage Groups Dashboard. Click on Storage section button to see the Storage Groups Dashboard.

In this lesson we will focus on managing storage groups. Click on the Total icon in the top left to navigate to the Storage Groups listing. New storage groups can be created either by clicking on the Create SG button in the storage groups listing page or clicking on the Provision Storage to Host common task in the Storage section menu. Both will launch the Provisioning wizard shown on the screen.

This wizard is identical to the wizard we saw earlier in this lesson, the only difference is that one has the ability to choose the host to which this storage should be provisioned as well. To modify a storage group, select a storage group from the storage group listing and click on Modify to launch the Modify Storage Group dialog.

Note that for cascaded storage groups, the dialog will always show the parent and child storage groups even if the modify button is clicked from the context of one of the child storage groups. One can make the desired changes i. One can run the Suitability Check when modifying storage groups. Once the desired changes are made add the job to the job list or run now. To view the details of a storage group, select a storage group from the storage group listing and click on View Details. The detailed view of the storage group shows detailed information on the storage groups and has links to the related objects and to the performance views.

The related objects has various links depending on the storage group. It will show the Volumes link clicking on the volumes link will list the volumes in the storage group.

One can also modify the SG or provision this SG to a host from this view. From this view, you can create new port groups or click a port group and delete or view its details.

The detailed view of a port group allows further actions. In the Create Port Group dialog, type a name for the port group and select ports from the available list. Click OK to complete the creation of the port group. The new port group will be listed in the Port Groups view. To see the details of a specific port group, select it in the Port Groups view and click View Details. You can Delete the port group from the detailed view. The Related Objects frame has various links depending on the port group.

All port groups will have the Ports link. Clicking the Ports link will show a listing of the ports. The other possible related object is Masking Views This link will appear if the port group is part of one or more Masking views.

Clicking the Ports link in the Related Objects frame of a port group will show the ports listing. You can remove a port from the port group by selecting the port from the list and clicking Remove. To add ports to the port group, click Add Ports. From this list, you can create new masking views or click a masking view and view its details, view its connections, or delete the same.

The detailed view of a masking view allows further actions. As we have already see the Provisioning Wizard will create masking views as part of the provisioning process as well.

Creating a masking view from this page requires the manual selection of Host, Storage Group and Port Group. As we have already see the Provisioning Wizard will create masking views as part of the provisioning process.

However one can choose to manually create a masking view by clicking on the Create Masking View button in the masking view listing. The Starting LUN number should be specified.

Click OK to complete the creation of the masking view. The new masking view will be listed in the Masking Views page. The masking view connections page allows you to see all the components that make up the masking view.

The connections page contains three tree lists for each of the component groups in the masking view - initiators, ports, and storage groups.

The parent group is the default top-level group in each expandable tree view and contains a list of all components in the masking group including child entries which are also expandable.

To filter the masking view, single or multi-select hold shift key and select the items in the list view. As each selection is made, the filtered results table is updated to reflect the current combination of filter criteria.

This view can be extremely useful for troubleshooting. As an example, you could filter the view by choosing only one of the initiators and one of the ports and see which of the initiators is logged in to the array.

To see the details of a specific masking view, select it in the Masking Views listing and click View Details. Click the Delete button to delete the masking view. Clicking these links will show a listing of those objects. Management of auto-provisioning groups with Unisphere was covered.

We also showed the use of the Storage Provisioning Wizard which greatly simplifies storage allocation. We illustrate with an example scenario. In this example we have an application server configured with two HBAs that required storage for two different applications. The service level requirements for the two applications are different. To satisfy the requirement of different service levels we will provision storage to this server by using cascaded storage groups.

Zoning of the HBAs to the ports can be confirmed by looking at the switch. In this example we use the symaccess list logins command to confirm that the servers HBAs have been zoned to the ports of the VMAX3 array.

We first create a file with the WWNs of the initiators. Then we create the initiator group with the consistent LUN option. We confirm the creation of the initiator group. We can use the symaccess show command to confirm that the initiator group has the correct WWNs. We then examine is contents with the symaccess show command.

We use the symdev list command with the notinsg option to list devices on the array which are not in any storage groups. The output shows us a listing of devices of such devices. The questions marks in the SA:P columns also indicate that these devices are not mapped to any front-end port. So we can safely assume that these devices are unused. We use devices for building the required storage groups. The storage groups are built as shown on the slide.

The parent storage group is populated with the two child storage groups. The symsg list detail command shows the storage groups we just created. Legend: Flags: Device E mulation. We finally create the masking view with the initiator group, port group and the parent storage groups we had recently created.

We can now go to the application host and perform a SCSI bus scan to discover the newly provisioned devices. The symaccess show view command shows us the details of the masking view. The output is long so we have broken the display over three slides. This slide shows the host initiators. This slide shows the port details. This slide shows the storage group details.

A SCSI rescan was performed on the application server. The syminq output shows the four VMAX3 devices that were provisioned to this server. The other highlighted column shows the VMAX3 logical volume numbers of We have set a bandwidth limit in this example, we have also set the dynamic distribution to always. The symsg list command shows the storage groups.

There is an explicit setting on the parent as well. We have set a bandwidth limit in this example this is less than that of the parent. The show output shows us that the bandwidth limit for this SG is while that on the parent is The pg option limits the output to the specified port group. The v option is supported for further detail.

The columns display all the available capacity and IOPS quotas and bandwidth quotas enforced within port groups. The pg option limits the output to the ports in the specified port group. The columns display all the available capacity and IOPS quotas and bandwidth quotas enforced by front-end directors. Moving a device to another SG will not disrupt the host visibility for the device, if any one of the conditions are met: Moves between child SGs of a parent SG, when the view is on the parent SG.

Moves when source SG is not in a masking view. If none of the conditions are met, the operation will be rejected, but the move can be forced by specifying the '-force' flag. Note that forcing a move may affect the host visibility of the device.

The symsg syntax is shown on the slide. To convert a standalone storage group to a cascaded configuration, the command supplies the name of the standalone storage group to be converted and the name of the new child storage group. Upon successful completion, the parent storage group retains the name of the standalone group and the child storage group is given the new child name. If the storage group starts in one or more masking views, at the end of the operation all of the views will be moved to the parent storage group.

To convert a cascaded storage group to a standalone configuration, the command supplies the name of the parent storage group to be converted to a standalone storage group. Note that this conversion is allowed only if the cascaded SG has a single child SG. Upon successful completion, the standalone storage group retains the name of the parent group. If the parent storage group starts in one or more masking views, at the end of the operation all of the views will be moved to the standalone storage group.

The symsg convert cascaded command allows the non-disruptive conversion of a standalone storage group to a cascaded storage group consisting of a parent SG and a single child SG. If the standalone storage group has a Host IO Limit, then the user must specify if after the conversion the limit will be set on the parent or the child storage group.

The symsg convert standalone command allows the non-disruptive conversion of a cascaded storage group consisting of a parent SG and a single child SG to a standalone storage group. This lab covers Cascaded Storage Groups, moving devices non-disruptively between storage groups and changing the SLO on storage groups. This module covered storage allocation of VMAX3 storage to hosts using auto-provisioning groups.

The workload planning features viz. The bottom right part of the dashboard shows information on the configured SRPs. For a given SRP one can see the allocated capacity. One can choose to check the Display Subscription box to see subscribed capacity as a percentage.

The Demand Report in the lower half of the output shows the demand from the perspective of the various SLOs that are in use on the array. As an example one can see that One can click on the Reports links to see the demand reports from a Storage Group and Workloads perspective. Recall that each of the disk groups is pre-configured with Data devices of a specific raid type.

The SRP utilization alert is enable by default with the default threshold policies shown. Please note that the default threshold policies cannot be modified. To setup customized thresholds, click on the Create button. In the Create Thresholds Policies dialog, pick the Symmetrix system from the dropdown menu, then pick the category from the dropdown menu. Then, highlight the pools to which the policy should apply, and choose the threshold levels, then the OK button to create a customized threshold.

This lesson covers the monitoring to storage group SLO compliance and storage group performance. The summary view of each VMAX3 array has various sections. The colors of the icons indicate the SLO compliance of the storage groups. The numbers indicate the number of storage groups in each category. Clicking on the icon will direct you to the appropriate listing. Setthresholdto5 MOSmaximum tosaveallsamples. IfyouhavequestionsrelatingtotheNemoUserClub,pleaseemailusatnemosupport anite.

Pleasecontactusatthefollowinglocations:EuropeandAfrica Email nemosupport anite. Home Documents Nemo File Manager. Post on Jan 83 views. Wait approximately 3 minutes after all expansion shelves are turned on, then push the power button on the controller.

Data Domain Hardware Installation 49 Take a moment to become familiar with the controls and indicators on the front of the new Take a moment to become familiar with the controls and indicators on the front of the new platform for DD Data Domain Hardware Installation 50 Take a moment to become familiar with the controls and indicators on the back of the new Take a moment to become familiar with the controls and indicators on the back of the new platform for DD Data Domain Hardware Installation 51 Take a moment to become familiar with the controls and indicators for the Network Interface Take a moment to become familiar with the controls and indicators for the Network Interface Card NIC on the back of the new platform for DD Data Domain Hardware Installation 52 Compare the front of the new platform the front of the new platform with previous generations.

Data Domain Hardware Installation 53 Take a moment to become familiar with the controls and indicators on the front of the new Take a moment to become familiar with the controls and indicators on the front of the new platform. Data Domain Hardware Installation 54 Take a moment to become familiar with the controls and indicators on the back of the new Take a moment to become familiar with the controls and indicators on the back of the new platform.

Data Domain Hardware Installation 56 This module covered the topics shown This module covered the topics shown. Data Domain Hardware Installation 57 After hardware After hardware installation, you perform initial configuration of the system as described in installation you perform initial configuration of the system as described in this module. Data Domain Hardware Installation 58 Obtain important configuration information before you start working in the configuration wizard.

The system installation documentation provides a worksheet for gathering the information. For the initial configuration, make sure that you have the following information on hand during the procedure: Login default password. The Data Domain system default username is sysadmin while the default password is the serial number.

The serial number located on the back panel and should be a 10 digit number. Initial configuration also requires a fully qualified hostname for the Data Domain system. You should also have Site domain name, and any licenses for the site. If the information is available at initial configuration, you should also note CIFS authentication details, and backup server and administrator details.

Best practice is to have a separate domain administrator account and password. For the backup servers, note that the configuration default uses the asterisk to allow everyone in facility to write to the backup.

This could be a security violation at the site. In most cases, you should specify which hosts are permitted. Space is also provided for a description of the physical location of the system. The location should be descriptive enough to allow support to quickly identify the system, for dispatch information. For example, this might include the facility location, as well as server location within the facility. For the mail server, note that this SMTP server in the location must be able to relay email externally to data domain support; a change or addition in the mail relay may be necessary.

The firewall should be configured so that only required and trusted clients have access to the Data Domain system. Port LED color is blue. Data Domain Hardware Installation 61 To begin configuration configuration, launch the terminal program on your laptop and configure the following communication settings: 3. Enable logging of the session.

Log in to the system. Data Domain Hardware Installation 62 At the first login, the configuration utility starts.

The configuration utility guides you through the configuration steps one section at a time If the CLI Configuration Wizard does not start immediately the first time you log in you can run it at any time by entering the through the configuration steps, one section at a time.

If the CLI Configuration Wizard does not start immediately the first time you log in, you can run it at any time by entering the command: config setup.

Complete all six sections. At each prompt, enter a value, OR Enter a question mark? Follow the configuration utility instructions for entering appropriate values. At the end of each configuration section, you can choose to: Save — Save the displayed configuration. Cancel — Delete all new values and go to the next section.

Retry — Restart the input entry at the beginning of the current section. The value entered previously appears as the default value at each prompt. For each configuration section, you are prompted to answer a series of questions. At the end of each section, a summary of your entries is displayed. You can accept or reject your changes and go to the next section, or return to the beginning of that section and change any of the settings.

When you select Retry, you are shown your previous entries for each prompt. After the configuration is completed, the CLI prompts you to reboot the system if a reboot is required. To activate licensed features installed on your system, enter a valid license key. Enter the license characters, including dashes, for each feature you have licensed. If using the CLI, press the Enter key. For example, enter dd Enter a domain name, such as corporation.

For example, enter xyz. Configure Ethernet Interfaces Ports 1. Enable the port. Select whether or not to use DHCP on the port. Press Enter to accept these values. In this case, use the net hosts command, which is described in the DD OS 5.

Press Enter. If you have additional Ethernet ports, set them up as described above. After saving the port configuration, allow up to two minutes for the Data Domain system to update the interfaces.

Enter the following information: System : Admin Host Required Enter a hostname that will have administrative access to the Data Domain system.

When you log into this host via the internet or intranet, you can view system logs and run system commands. The hostname can be a fully qualified domain name, a simple hostname, or an IP address. Admin Email Required Enter the email address or a group alias that is to receive email from the Data Domain system.

The system uses the email address as the sender of alert and autosupport email messages from this system, and also as the recipient for these messages.

The alert command manages the alerts history file and who receives email notification for system alerts. For more information about autosupport and alerts, see the DD OS 5. The alerts and autosupport reports display the location. Determine your local time zone.

Otherwise, warning messages might display when the system reboots. Enter: ping hostname where hostname is the hostname or an IP address associated with the interface being tested. Each interface must have a unique hostname or IP address. Data Domain Hardware Installation 63 After you install one or more expansion shelves in the rack, use this procedure to add shelves to the volume y p , p and create RAID groups. If the drive letter is not the same, change the drive letter to match the drive letter for the old Extended Drive , using Disk Manager in Windows.

Verify that the drive letter for the new drive is the same as the drive letter for the old Extended Drive. Verify the service starts successfully and the Extended Drive has an "Online Status". Right click on the media in the DiskXtender Administrator, and choose "Edit Tasks" from the flyout menu.

Choose the "File Restore" task from the drop down menu, and complete the wizard. This will re-populate the new Extended Drive with the file and directory structure of the old Extended Drive. Enable the DiskXtender Move Schedule. Use this step if you have Centera Media. Set the Startup type back to "Automatic". Do you know of any way to get the data from a DiskXtender system directly from media, bypassing the DiskXtender software.

Post a Comment. My Plain Blueberry Juice.