EMC Symmetrix VMAX and Sybase ASE - Dell EMC Italy Symmetrix VMAX and Sybase ASE Applied Technology...

EMC Symmetrix VMAX and Sybase ASE Applied Technology

Abstract

This white paper describes EMC® Symmetrix® VMAX™ features and functionality related to storage provisioning and device migration. The EMC Enginuity™ 5874 features Auto-provisioning Groups and Enhanced Virtual LUN Technology are described for a Sybase ASE environment.

May 2010

Copyright © 2009, 2010 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com

All other trademarks used herein are the property of their respective owners.

Part Number h6204.1

EMC Symmetrix VMAX and Sybase ASE Applied Technology 2

Table of Contents Executive summary ............................................................................................4 Introduction.........................................................................................................4

Audience ...................................................................................................................................... 5 Terminology ................................................................................................................................. 5

Symmetrix VMAX with Enginuity.......................................................................6 Disk drive support ........................................................................................................................ 7

Auto-provisioning Groups .................................................................................7 Creating a masking view for an application or host ..................................................................... 8

Rules regarding views .............................................................................................................. 8 Provisioning storage for Sybase ASE.......................................................................................... 8

Enhanced Virtual LUN Technology .................................................................12 Rules regarding Virtual LUNs .................................................................................................... 12 Use cases for a Sybase ASE environment................................................................................ 13

Implementing Virtual LUN with Sybase ASE.......................................................................... 13 Conclusion ..........................................................................................................2


Executive summary The EMC® Enginuity™ storage operating environment provides the intelligence that controls all components in an EMC Symmetrix® VMAX™ storage array. While it shares many traits with the operating systems typically used to run large host computers, Enginuity is more specialized and specifically optimized for storage-based functions. It is driven by real-time events related to the input and output of data. It applies self-optimizing intelligence to deliver the performance, availability, and data integrity required in a platform for advanced storage functionality.

Enginuity, as a proven storage operating environment, carries all of its extended and systematic development forward in each successive Symmetrix platform generation. This means that all of the reliability, availability, and serviceability features; all of the interoperability and host operating systems coverage; and all of the application software capabilities developed by EMC and its partners continue to perform productively and seamlessly as underlying technology is refreshed.

Enginuity’s unique value grows from four key concepts:

Foundation—Preemptive multi-tasking, operational consistency, and security. Enginuity is the core intelligence to manage multiple shared resources across Symmetrix systems. It ensures investment protection and consistency over time in technology and operational processes. It provides built-in security capabilities while insulating powerful storage applications from technology changes.

Performance—Maximizing speed. Utilizing patented intelligent adaptive algorithms to manage data flow across channels, memory, and disks, Enginuity dynamically controls events in complex and highly variable environments to maximize application performance under any load.

Availability—Always accessible data. Enginuity manages data integrity through continuous checking of all data and hardware—from host to memory to disk and back again. This includes trend analysis and early detection as well as automatic failover and escalation when a problem does occur.

Open integration—Comprehensive coverage, guaranteed interoperability, and investment protection. EMC maintains the industry’s broadest, deepest, and most exhaustive storage networking interoperability program for hardware and software. In addition, using openly available application programming interfaces (APIs) and supporting SMI industry standards, EMC has enabled hundreds of independent software vendor applications to run on Symmetrix.

EMC recently introduced the Symmetrix VMAX Series with Enginuity. The new Symmetrix VMAX delivers the industry's first Virtual Matrix Architecture and revolutionizes the high-end storage market to set Symmetrix apart from all other competitive offerings. Symmetrix VMAX with Enginuity delivers a feature called Auto-provisioning Groups, which allows users to create independent groups for initiators, front-end ports, and devices, and associate and dissolve these groups into a masking view. In addition to Auto-provisioning Groups, Enginuity 5874 provides array-based data movement called Virtual LUN technology to enable transparent, nondisruptive data mobility between storage tiers for standard Symmetrix volumes.

There are other feature sets and functionality available for the Symmetrix VMAX systems with Enginuity 5874, however, this paper focuses on Auto-provisioning Groups and Virtual LUN technologies.

Introduction One of the most time-consuming tasks for a storage administrator is the provisioning of data storage for business applications and systems. EMC has developed new technologies to simplify this process and alleviate some of the redundant tasks associated with storage provisioning and data migrations.

This white paper demonstrates the integration testing that was completed using the Symmetrix VMAX system with Enginuity 5874 features and functionality, in a Sybase ASE environment. Implementing Auto-provisioning Groups and Virtual LUN technologies with Sybase ASE provides the capability to optimally provision storage and address LUN migration needs for a single ASE database, or an entire Sybase instance.


Audience This white paper is intended for storage architects, system administrators, and database administrators responsible for deploying Sybase ASE databases on EMC Symmetrix VMAX systems with Enginuity 5874.

Terminology Enginuity operating environment for Symmetrix

The EMC Symmetrix VMAX storage operating environment.

Enhanced Virtual LUN Virtual LUNs allow the migration of data between physical device types or protection types without application downtime.

Initiator group Contains the front-end director ports defined to a view. Port group Contains the host bus adapters (HBAs) defined to a view. Storage group Contains Symmetrix device IDs assigned to a view. Auto-provisioning Groups Allows the physical mapping of devices made up from initiator, port, and storage

groups to a specific host. Solutions Enabler Contains all of the EMC storage management software to provide a host with

SYMAPI shared libraries and the Symmtrix command line interface (SYMCLI). symaccess EMC Solutions Enabler command line interface (CLI) that enables the Auto-

provisioning Groups functionality. symmigrate EMC Solutions Enabler command line interface (CLI) that enables the Enhanced

Virtual LUN technology. Sybase ASE meets the demands of large and high-transaction volume applications, while providing a database management system. Its key features include on-disk encryption, small partitions, and new query processing technology that has demonstrated a significant increase in performance, as well as enhanced support for unstructured data management.

Auto-provisioning Groups, available with Solutions Enabler version 7.0, provides an easier, faster way to provision storage in Symmetrix VMAX arrays running Enginuity 5874.

Applications running on Symmetrix VMAX arrays require a fault-tolerant environment with clustered hosts and multiple paths to devices.

Auto-provisioning Groups was developed to simplify storage allocation in these environments. In the past, mapping and masking devices required a separate command for each initiator/port combination through which devices would be accessed. With EMC Solutions Enabler 7.0, the symaccess command allows the user to create a group of devices (storage group), a group of director ports (port group), and a group of host initiators (initiator group), and associate them in a masking view.

When the masking view is created, the devices are automatically mapped and masked to the host. After the masking view is created, any objects (devices, ports, or initiators) added to an existing group automatically become part of the associated masking view. This means that no additional steps are necessary when adding devices, ports, or initiators to an existing configuration. This reduces the number of commands needed for mapping and masking devices and allows for easier storage allocation and de-allocation.

Enhanced Virtual LUN Technology, available with Solutions Enabler 7.0, enables transparent, nondisruptive data mobility between storage tiers and between RAID protection schemes. Virtual LUN migration can be used to populate newly added disk drives or move devices between high-performance and high-capacity disks, delivering tiered storage capabilities within a single Symmetrix VMAX array. Migrations are performed while providing constant data availability and protection.

Enhanced Virtual LUN migration can be managed via the Symmetrix Management Console (SMC) graphical user interface, or the Solutions Enabler Command Line Interface (SYMCLI).


Symmetrix VMAX with Enginuity The Symmetrix VMAX system is an innovative platform built around a scalable Virtual Matrix design. It incorporates powerful new multi-core processors and can seamlessly grow from an entry-level configuration into the world’s largest storage system.

Symmetrix VMAX delivers the highest levels of performance, featuring:

• Support for 48 to 2,400 drives From 1 to 10 storage bays 240 drives per bay

• Support for 2 to 16 directors connected via a high-speed Virtual Matrix • Connectivity: Fibre Channel, FICON, iSCSI, GigE • 2x the front-end ports of DMX-4 • 2x the back-end ports of DMX-4 • Approximately 2x the IOPS performance of DMX-4 • Heterogeneous support for mainframe, UNIX, System i, and virtualized hosts Symmetrix VMAX offers the ultimate in scalability, including the ability to incrementally develop back-end performance by adding Symmetrix VMAX Engines and storage bays. Each VMAX Engine controls eight redundant Fibre Channel loops, which support up to either 240 or 360 drives depending upon configuration. Each VMAX Engine provides front-end as well as back-end connectivity.

Capacity and performance upgrades can be performed online while production applications are operating. In fact, all configuration changes, hardware and software updates, and service procedures are designed to be performed online and nondisruptively. This ensures that customers can consolidate without compromising availability, performance, and functionality, while leveraging true pay-as-you-grow economics for high-growth storage environments.

Figure 1. Symmetrix VMAX system features


Disk drive support The Symmetrix VMAX supports a 4 Gb/s back end, with a dual switched loop configuration providing redundancy, improved isolation of faults, and port bypass capability. The disk drives are installed in the front of storage bays and connect to a midplane. Each disk drive is integrated with a dual-port Fibre Channel Arbitrated Loop (FC-AL) controller with a Fibre Channel interface that transports the SCSI protocol. Each Symmetrix VMAX Engine controls eight Fibre Channel loops that support up to either 240 or 360 drives depending upon the configuration. Each VMAX Engine also provides front-end as well as back-end connectivity.

Symmetrix VMAX supports SATA (or Serial Advanced Technology Attachment) disk drives that are lower performance, higher capacity disk. These drives are typically used for backup consolidation, data archiving, and/or data warehousing applications not requiring high I/O transaction rates.

Lastly, enterprise Flash SSD (solid state disk) drives are supported. They are constructed with nonvolatile semiconductor NAND Flash memory and are packaged in a standard 3.5-inch disk drive form factor used in existing EMC Symmetrix system drive-array enclosures. These drives are especially well suited for low-latency applications that require consistently low read/write response times.

The following table describes all the available/supported disk drives for the Symmetrix VMAX system.

Table 1. Disk drive support

Drive type Rotational latency Capacity 4 Gb/s FC 15k 146 GB, 300

GB, 450 GB 4 Gb/s FC 10k 400 GB SATA II 7.2k 1 TB 4 Gb/s Flash (SSD)

n/a 200 GB, 400 GB

Note: 2 GB FC drives are no longer supported. All drives are formatted at the 520-byte sector (except for AS400, which is formatted at 528).

Auto-provisioning Groups Auto-provisioning Groups for Symmetrix VMAX is a new method of provisioning storage to a host. This new feature set helps meet scalability demands for modern storage provisioning requirements including:

• Storage arrays require 20 K devices (or more) • Large cluster implementations • Virtual machines / server farms The development of Auto-provisioning Groups is part of EMC’s “Goal Driven Storage Administration (GDSA)” initiative, which was designed to provide:

• Enhanced storage provisioning • Ease of use • Alignment of storage provisioning with customers’ day-to-day tasks EMC’s Symmetrix VMAX with Enginuity Auto-provisioning Groups utilizes a collection of grouping constructs called views that incorporate:

• Symmetrix devices (storage groups) • FA ports (port groups) • HBAs (initiator groups)


View creation incorporates mapping and masking of devices to FA ports and HBAs utilizing storage group (SG), port group (PG), and initiator group (IG) definitions. The initial implementation involves a few more “setup” steps than traditional symmask and symconfigure methods, but the payoff comes when daily storage administration tasks are necessary.

Creating a masking view for an application or host In order to create a masking view using Auto-provisioning Groups, a few logical steps are necessary. Figure 2 depicts a simplified configuration where storage is provisioned for a primary application on a production host. A backup server and a set of BCVs are also defined to the masking view.

Figure 2. Environment for Auto-provisioning Groups

In Figure 2, the initiator group named prodserv_hbas contains the WWN for HBA3 and HBA4. The initiator group named backupserv_hbas contains the WWNs for HBA5 and HBA6. Next, a port group named production_ports is created containing FA ports 01:0 and 02:0. At this point, prodserv_hbas, backupserv_hbas, and production_ports are connecting two hosts, through a SAN to the Symmetrix VMAX system. The last step in the process will be to create storage groups that will be automatically mapped and masked to the hosts. app1_std contains STD devices for the production server, app1_bcv contains BCV devices for the backup server, and app1dg is a device group containing all STD and BCV devices associated with the production and backup server hosts.

Rules regarding views A masking view can support many to one, many to many, or one to many relationships. For example, a port group could consist of four FA ports dedicated to Solaris hosts. This port group could be part of different masking views.

Updates to views are simple – if an application or host needs more storage, simply add more devices into the associated masking view whereby:

• New devices are automatically mapped and mask to the host. • No symconfigure or symmask commands are issued. Use the SYMCLI command symaccess to invoke initiator group functionality.

Provisioning storage for Sybase ASE Creating a port, initiator, and storage group are necessary tasks, all resulting in the creation of a masking (or storage) view. After the masking view has been created, the devices are available to the initiators on the storage ports. Host-specific commands can then be run to configure the devices to the operating system.


After these steps are complete, the devices can be used to create a Sybase ASE instance or database. The following Solutions Enabler commands will provision storage using Auto-provisioning Groups functionality for Sybase ASE.

1. This physical device command will provide a list of devices currently mapped to the host. a. sympd list

2. This Auto-provisioning Groups command will provide information related to the host HBAs including WWN, IP address, type, and username.

a. symaccess discover hba –v 3. This device command will provide a list of devices that are currently available, are not

currently clone devices, and are not mapped to another host port (FA). a. symdev list –sid 254 –RAID5 –nobcv –noport –N 30

4. This device group command will create a device group named SYB_devs. a. symdg create SYB_devs

5. This logical device command will add all devices in range 602 to 60F to the device group named SYB_devs.

a. symld -sid 254 -g SYB_devs addall -range 602:60F 6. This Auto-provisioning Groups command will create a storage group named SYB_stor using

the devices from group SYB_devs. a. symaccess -sid 254 create -name SYB_stor -type storage -g SYB_devs –std

7. This Auto-provisioning Groups command will create a port group named SYB_port using FA director 7e0.

a. symaccess -sid 254 -name SYB_port -type port -dirport 7e:0 add 8. This Auto-provisioning Groups command will create a group named SYB_hbas using the

HBA information defined in the file SYB_hbas.txt. The file looks like this: WWN:10000000c9563968

a. symaccess -sid 254 create -name SYB_hbas -type initiator -f /scripts/SYB_hbas.txt

9. This Auto-provisioning Groups command will create a masking view named SYBview using the previously defined storage, port, and initiator group information.

a. symaccess -sid 254 create view -name SYBview -storgrp SYB_stor -portgrp SYB_port -initgrp SYB_hbas

10. On a UNIX host, these commands are required for rescanning the buses, which will enable the host to see the newly configured devices. In some cases, a reboot is required.

a. cfgadm, or devfsadm, or a physical reboot The following figures all display information about the group setup.

Figure 3. symaccess command to display the masking view


Figure 4. symaccess command to display the initiator group

Figure 5. symaccess command to display the port group

Figure 6. symaccess command to display the storage group As seen in Figure 6, the devices 081:087 and 7E0:7E7 are contained in the storage group SYB_storage. These devices are accessible to the host and available for Sybase configuration.

The following display shows a listing of the devices that are mapped to the host. For display purposes, some of the output listing has been deleted.


licoc036# sympd list --------------------------- ------------- ------------------------------------- Physical Sym SA :P DA :IT Config Attribute Sts (MB) --------------------------- ------------- ------------------------------------- /dev/rdsk/emcpower0c 0087 10E:1 07D:C9 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower1c 0086 10E:1 08B:C6 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower2c 0085 10E:1 08C:C9 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower3c 0084 10E:1 08A:C5 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower4c 0083 10E:1 07D:D6 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower5c 0082 10E:1 07B:C7 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower6c 0081 10E:1 07C:D9 2-Way Mir N/Grp'd RW 6 /dev/rdsk/emcpower455c 07E7 10E:1 07A:D7 RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower456c 07E6 10E:1 08A:D8 RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower457c 07E5 10E:1 07A:D5 RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower458c 07E4 10E:1 08A:DA RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower459c 07E3 10E:1 08A:D6 RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower460c 07E2 10E:1 07A:D9 RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower461c 07E1 10E:1 08C:D2 RAID-6 N/Grp'd RW 4314 /dev/rdsk/emcpower462c 07E0 10E:1 07A:C4 RAID-6 N/Grp'd RW 4314

The devices can be configured for a Sybase ASE instance using a volume manager, UNIX symbolic links, or other. For the testing scenarios used in this paper, raw devices were used. Therefore, UNIX symbolic links are defined using a shell script as follows:

ln -s /dev/rdsk/emcpower455c master ln -s /dev/rdsk/emcpower456c sysprocs ln -s /dev/rdsk/emcpower457c sybsystemdb ln -s /dev/rdsk/emcpower458c datadev1 ln -s /dev/rdsk/emcpower459c datadev2 ln -s /dev/rdsk/emcpower460c datadev3 ln -s /dev/rdsk/emcpower461c logdev1 ln -s /dev/rdsk/emcpower462c logdev2

Once the links are in place, devices internal to the Sybase instance can be defined. The Sybase master, sybsystemprocs, and sybsystemdb devices are defined during the srvbuild process. After the Sybase instance is up and running, the database devices can be initialized using a script file that defines the physical and logical device names for Sybase.

disk init name=datadev1, physname="/usr/sybaseASE/ASE-15_0/devs/datadev1", vstart=1, size="2000M" disk init name=datadev2, physname="/usr/sybaseASE/ASE-15_0/devs/datadev2", vstart=1, size="2000M" disk init name=datadev3, physname="/usr/sybaseASE/ASE-15_0/devs/datadev3", vstart=1, size="2000M" disk init name=logdev1, physname="/usr/sybaseASE/ASE-15_0/devs/logdev1", vstart=1, size="1000M" disk init name=logdev2, physname="/usr/sybaseASE/ASE-15_0/devs/logdev2", vstart=1, size="1000M"

Next, create a database on the initialized Sybase devices.

create database TEST on datadev1=”2G”, datadev2=”2G”, datadev3=”2G” log on logdev1=”1G”, logdev2=”1G”


If more devices are needed to provision storage for backup servers, user databases, or other applications, the process simply involves adding more devices to the masking view.

1. This Auto-provisioning Groups command will add devices 800 to 807 to the storage group SYB_storage.

a. symaccess -sid 254 -name SYB_storage -type storage add devs 800:807 2. On a UNIX host, these commands are required for rescanning the buses, which will enable the

host to see the newly configured devices. In some cases, a reboot is required. a. cfgadm, devfsadm, or –rescan, or a physical reboot

If it becomes necessary to remove devices from the storage group, use one of the following commands and then rescan the host for the devices.

1. This Auto-provisioning Groups command will remove devices 800 to 807 from the storage group SYB_storage.

a. symaccess –sid 254 –name SYB_storage –type storage remove devs 800:807 2. This alternative command will remove the standard devices contained in the device group named

SYB_devs. a. symaccess –sid 254 –name SYB_storage –type storage remove –g SYB_devs –std

3. This alternative command will remove the source devices defined by the file SYB_devs.txt. a. symaccess –sid 254 –name SYB_storage –type storage remove –file SYB_devs.txt src

For more details on this new feature and functionality, refer to Storage Provisioning with EMC Symmetrix Auto-provisioning Groups. This technical note can be found on the Powerlink website.

Enhanced Virtual LUN Technology EMC Solutions Enabler’s Enhanced Virtual LUN Technology enables transparent, nondisruptive data mobility between storage tiers for standard Symmetrix VMAX system volumes. This technology is based on Symmetrix VMAX with Enginuity RAID Virtual Architecture and requires Enginuity code level 5874.

Enhanced Virtual LUN migration provides users the ability to move data between high-performance drives and high-capacity drives. This new functionality is used to either change RAID protection types, physical disk groups, or both. It allows the migration of data, independent of host operating systems or applications. It supports the migration of metadevices, and can utilize configured or unconfigured disk space for target devices. Unconfigured disk space has no hypervolume assignment. Configured disk space uses existing Symmetrix VMAX logical volumes that are not currently assigned to a host.

Migration is facilitated by the creation and movement of RAID groups. Upon completion of the migration, the original RAID group is deleted or the devices are reformatted.

Rules regarding Virtual LUNs • Enhanced Virtual LUN Technology works with all EMC replication technologies including:

SRDF® TimeFinder®/Snap and TimeFinder/Clone Open Replicator

• Only migrations of devices on local Symmetrix VMAX system units are allowed. • Once established, migrations cannot be canceled. • Protected devices cannot be moved to unprotected devices. • Target device migration must be unmapped and/or unmasked and cannot be allocated to configured

space. • Only one control operation can be executed on any device at one time.


• Migrations are managed as a session. Once the session is established, migration is monitored/managed

by the assigned session name. • Multiple migrations can be run in parallel sessions, with a maximum number of 16. • RDF devices cannot be specified as the target for a migration to configured space. • Use the SYMCLI command symmigrate to initiate Virtual LUN functionality.

Use cases for a Sybase ASE environment Virtual LUN technology can provide added benefits in Sybase ASE environments by allowing the device migration of a single ASE database or an entire instance. One business use case would involve the migration of a database that resides on RAID 1 devices, onto RAID 5 devices. Another advantage of using Virtual LUN technology would involve migrating a database to SATA disk for archiving purposes. Examples describing how these migrations could be implemented are described in the following section.

Implementing Virtual LUN with Sybase ASE It is important to understand the Sybase configuration prior to a virtual migration. For the purposes of this testing, a Sybase ASE instance was created on RAID 1 devices and was migrated to RAID 5 SATA devices.

Figure 7. Storage devices as they relate to the database instance

In Figure 7, the EMC PowerPath® devices 95D to 960 were used. UNIX symbolic links were defined so that a Sybase instance and database could be created using these devices. The three Sybase devices — master, sybsystemdb, and sysprocs — were initialized during the Sybase srvbuild process. Devices internal to Sybase were then initialized (via disk init), and a test database was created on four data devices (datadev1-4) and two log devices (logdev1-2).

Last, the devices 95D:960 are all assigned to an EMC Solutions Enabler device group named VLUN (not shown here). These are RAID 1 devices and will be migrated to RAID 5 SATA disk during the Virtual LUN migration process.

In order to perform a Virtual LUN migration, logical steps should be followed in this order.

1. Determine if there is sufficient free disk space for the migration.


Figure 8. Determine available disk space

The symdev list command shown in Figure 8 displays available RAID 5 7+1 devices as specified on the command line. The Symmetrix VMAX system used for this testing was configured such that disk group 1 contains only SATA drives. Based on this output, there are a sufficient number of devices, and enough capacity to perform a migration.

2. Validate the migration parameters.

Figure 9. Validate the migration parameters

This symmigrate command tests the user input to see if it would succeed at the current point-in-time given the specified parameters.

3. Once satisfied that it is safe to proceed, establish the migration session. This will start the synchronization process.


Figure 10. symmigrate establis The migration process can be performed on a database or application that is live. During an Enhanced Virtual LUN Technology migration, background locks are granted and released at various times throughout the process, the secondary mirror is synchronized with the primary, and finally, the primary and secondary device roles are switched. These operations happen in the background, and are completely transparent to the host or application.

4. As an optional step, run a query during the migration process.

Figure 11. symmigrate query

Figure 11 shows that the migration is still in progress. There is one device that has completed its synchronization (95D); there are eight more to go.

5. Verify the migration session to determine completion state. The verify option will report a success or failure state as in the following example;


licoc035# symmigrate -name SYBtest -sid 254 verify All session(s) with name 'SYBtest' are in 'Migrated' state.

Figure 12. Verify a successful and complete migration

In Figure 12, another query on the SYBtest session shows each individual device synchronization state.

6. The final step in the process involves a database integrity check. Several tests were performed to prove our testing was successful and that it did not adversely affect the database, or data integrity.

a. The Sybase instance log file was monitored for errors during the entire migration.

b. The Sybase instance was bounced (shut down and restarted) after the migration to ensure a clean restart.

c. The Sybase database was verified via dbcc checkdb to ensure no errors were incurred during the procedure.

Conclusion EMC Symmetrix VMAX with Solutions Enabler 7.0 provides many new features and functionality, including Auto-provisioning Groups and Enhanced Virtual LUN Technology. These new technologies provide an easier, faster way to provision storage in Sybase ASE environments, while enabling transparent, nondisruptive data mobility between storage tiers for standard Symmetrix VMAX volumes.


EMC Symmetrix VMAX and Sybase ASE - Dell EMC Italy Symmetrix VMAX and Sybase ASE Applied Technology...

Documents

Transcript of EMC Symmetrix VMAX and Sybase ASE - Dell EMC Italy Symmetrix VMAX and Sybase ASE Applied Technology...