You are on page 1of 13

EMC TechNote: Integrating Celerra with Rational

ClearCase 2002.05.00
1 Introduction
This technical note describes the configuration environment used to test the integration of the EMC® Celerra®
Network Server with IBM Rational ClearCase 2002.05.00 operations. It details the configuration areas required
for a successful integration, where to get additional information, and presents information that you need to
consider when performing ClearCase 2002.05.00 operations with NFS and CIFS.
ClearCase is a software configuration management system developed by IBM Rational Software. This
distributed client/server application manages versions of files and directories by storing them in a database.
ClearCase allows you to track changes to every file and directory, and maintains histories of source code, test
suites, libraries, executables, and documentation.
The audience for this technical note is the installation and configuration specialist familiar with the Celerra and
IBM Rational ClearCase operations.

2 Integration Testing Overview
Integration testing evaluates the operation of an application in a variety of configurations, including:

Windows with CIFS protocol

• UNIX with NFS protocol
The integration tests identified specific configuration requirements and integration considerations which are
documented in this Technical Note.
Testing included formal certification using ClearCase Stress Test Harness (CCST), of ClearCase v2002.05.00
(including MultiSite) with Celerra for Windows, UNIX and multi-platform environments. CCST is a ClearCase
test tool designed by IBM Rational software that was used as part of this testing.

3 Terminology
Element — Files and directories that reside in ClearCase source control.
Storage pools — A set of files and directories inside the VOB that can be a source pool or a cleartext pool that
contains element data; or a derived object pool that contains derived objects.
Versioned Object Base (VOB) — A repository that stores versions of file elements, directory elements,
derived objects (an intermediate result of the build process under ClearCase control), and metadata.
View — An object that provides a work area for one or more users. It allows you to look at a specific version of
elements, files, and directories within a database through a given set of rules.
View tag — An object that allows you to access the view network-wide. The name with which users reference a
view.
VOB storage directory — The top directory in a directory tree for a VOB.
View storage directory — The top directory in a directory tree for a View.
VOB tag — An object that enables you to view information on a specific Versioned Object Base.

Integrating Celerra with Rational ClearCase 2002.05.00

1

05.00.00.6 multisite_p2002. Notify request). The value is returned in the negotiate command. branches. refer to section 4. The c subdirectory tree caches the recently accessed file elements and may experience high I/O.05.2 View Database Each View is also implemented as a directory tree whose top directory is called the View storage directory.00 MultiSite patch p2002. Table 1 Test and Configuration Environment Component Platform Version Software Windows 2000 Server.1.00 ClearCase patch p2002.05. All the View private objects text editor backup files for example are stored in a private storage area (.NT-9 ClearCase patch p2002.e.00 It fixes Solaris defect 4349744. The View holds an embedded database under the db subdirectory that is used to track correspondence between VOB and View objects.00.00.05. The s and db directories are critical directories and need a reliable storage device.00 2 . the following error may occur: Insufficient system resources exist to complete the requested service.NT-22 MultiSite version 2002.05.05. For information on accessing the EMC NAS Interoperability Matrix.1 VOB Database Each VOB is implemented as a directory tree whose top directory is called a VOB storage directory. clearcase_p2002.05. which prevents ClearCase clients from accessing VOB or View data stored on a NAS device.05.05. The actual data (all of the element’s versions) are stored in the s subdirectory tree. Integrating Celerra with Rational ClearCase 2002.05.05. Accessing the EMC NAS Interoperability Matrix.00. The d subdirectory tree stores the intermediate results of the building process and increases in size during the development process.05. SP2 ClearCase version 2002.00.NT-8 ClearCase patch p2002. The EMC NAS Interoperability Matrix contains the most up-to-date version information.3. The Windows client machine uses this value to limit the number of commands. A VOB holds an embedded database under the db subdirectory that stores all version control structures such as elements. If this parameter is set to the default value (127) during a Windows CCST session.NT-21 ClearCase patch p2002. the following parameter value was changed on the Data Mover: maxMpxCount=50.9.1..NT-7 ClearCase patch p2002.NT-1 Hardware Solaris 8 minimum patch required: 108727-09 ClearCase version 2002. 4 Test and Configuration Environment Table 1 shows the configuration environment used for this application test.00-1 Note: For the Windows CCST environment configuration.00-8 Data Mover 510 5. This parameter sets the maximum number of commands allowed without acknowledgement in the Data Mover (i. and versions. 3.s subdirectory).

be sure to use accesspolicy=NATIVE to avoid the following error when creating View or VOBs from Windows. Integrating Celerra with Rational ClearCase 2002.05. Check that root or the ClearCase administrators group has permission to write to this directory.00. In the Sort Search Results by box. 5 IBM Rational ClearCase For instructions on installing ClearCase MultiSite. refer to the online documentation at: http://www-306. 5.1 Configuration Requirements You can install the ClearCase release area on a Celerra shared file system. was used to verify the integrity of the data and metadata.1 Accessing the EMC NAS Interoperability Matrix Refer to the EMC NAS Interoperability Matrix for definitive information on supported software and hardware. The Celerra was configured to host ClearCase VOBs and Views for both UNIX and Windows clients on the same file system.nooplock ufscc1 /ufscc1 $ server_export server_2 -o \ access=unixvobsrvr:unixviewsrvr.root=unixvobsrvr:unixviewsrvr /ufscc1 $ server_export server_2 -P cifs –n ufscc1 /ufscc1 You must give root access to the ufscc1 file system for the hosts that run ClearCase VOBs and Views services. 3. Use the following operations for this configuration. To view the EMC NAS Interoperability Matrix: 1. Fibre Channel switches. When the same file system is used by the UNIX and Windows clients. Go to http://powerlink.4. The options accesspolicy=NATIVE and nolock are defaults for clients. Check of the VOB. select Score.ibm. network disconnects. In order to help maintain the data integrity with CIFS.00 3 . Testing activities were performed. dynamic file system expansion.nolock. using ClearCase commands. and virus checking. refer to Rational ClearCase Product Family Installation Guide for ClearCase MultiSite V2002. For ClearCase installation instructions.com/software/rational/support. Extensive testing of VOB and View creation with ClearCase was performed with the VOBs and Views storage directories located on a Celerra. check out. check in. oplocks on the Data Mover were disabled.com/. and reboots. ClearCase (including MultiSite) was successfully tested using CCST. cleartool: Error: Failed to record hostname "winviewsrvr" in storage directory "<Storage Directory name>". such as backup software. You can configure separate file systems for VOBs and Views in order to allow access to the VOB by the VOB servers only. and application support for Celerra network attached storage (NAS) products.05. as well as high-availability simulation to cover component failure/failover. Among the ClearCase operations tested were files and directories. The EMC NAS Interoperability Matrix appears in the list. and modification.emc. Search for NAS Interoperability Matrix. in the context of Celerra features such as TimeFinderTM/FS and SnapSureTM. Celerra file system feature interaction tests also covered quotas. Mount and export the file system to be used for VOB(s) and View(s) storage for NFS and CIFS: $ server_mount server_2 –o accesspolicy=NATIVE. 2.

For storage configurations and devices supported by ClearCase.ibm.capitals:*:4000:2000::: Group file example: users. With ClearCase for Windows.capitals::2001: With ClearCase for Windows. Note: If the user clearcase_albd . or the UNIX user management extension of a Windows Active Directory. Invoke the CLI tool for UNIX and Windows environments with the command. refer to Solution ID 26084 at: http://www-306.2 ClearCase VOBs and Views with Celerra You can use a Celerra in a ClearCase environment as a storage repository for VOBs and Views.capitals:*:1405:2001::: st1:<encrypted password>:4000:2000::: st1. This user is used by ClearCase services and must join the clearcase group. in the example below the name of the domain is capitals. The following sections provide examples. and multiprotocol environments with storage located on a Celerra. As an alternative. The clearcase_albd domain user and clearcase group must exist in the Data Mover password and group files if you choose this method of mapping users and groups to IDs.00 4 . ClearCase requires the Primary Group name of ClearCase users to be the same on both Windows and UNIX.com/software/rational/support/. is not defined for the Data Mover. you can set the variable CLEARCASE_PRIMARY_GROUP on Windows clients with the name of UNIX Primary Group. For example. UNIX and Windows users and groups must be mapped to the same UIDs and GIDs either by using local password and group file entries. the user st1 will have its Primary Group set to users on Windows and UNIX. In a multiprotocol environment. an error similar to this may occur when creating VOBs or Views: Failed to record hostname <VOB server name> in storage directory <Storage Directory name> 5. Table 2 Names Used in Examples Object Windows VOB server UNIX VOB server Windows View server UNIX View server Data Mover name Name winvobsrvr unixvobsrvr winviewsrvr unixviewsrvr dm2-ana0 Integrating Celerra with Rational ClearCase 2002. a domain group named clearcase should exist at installation time. cleartool. of how to create ClearCase VOBs and Views for NFS. Note: Windows entries contain domain names. This group is used by the ClearCase services and cannot be used by regular users. Table 2 outlines the names used in these examples. Since the two platforms have different restrictions (name length and case sensitivity) choose names that will fit both. CIFS. using the CLI. The following example shows how this mapping was done using local password and group files on the Data Mover for this testing.05. Password file example: clearcase_albd.If you are working with a multiprotocol ClearCase environment.capitals::2000: clearcase. You can also perform ClearCase operations using a GUI. a domain user called clearcase_albd is created at installation time. multiple entries in NIS.

the UNC pathname notation was used. on a file system shared with CIFS. Refer to section 5. the storage pathname for the VOBs and/or Views may no longer be valid.vbs nt_vob_tag vob_unix_cns.vbs cns_view_tag cns_view. /net was used. This will require a VOB relocation operation.2 Create ClearCase VOBs and Views for CIFS with Storage Located on a Celerra The environment for this example assumes Views are stored on a Celerra.1 for details. The simplest way to make the storage not dependent on the name of the Data Mover or file system is to create a separate automount point. If a Data Mover or the file system is changed.05. using either TCP or UDP over IP. A UNIX share can be accessed by /net/<hostname>.vbs 5.3.vws $ cleartool mkview –tag cns_view_tag –host unixviewsrvr –hpath \ $STGPATH –gpath $STGPATH $STGPATH 5.1 Create ClearCase VOBs and Views for NFS with Storage on Celerra The environment for this example assumes the application has VOBs and Views stored on a Celerra on a file system shared with NFS Version 2 or 3.vbs $ cleartool mkvob –c “test” –tag /cns_vob_tag –host \ unixvobsrvr –hpath $STGPATH –gpath $STGPATH $STGPATH The following command creates a dynamic View running on the local host unixviewsrvr with storage on a Celerra: $ STGPATH=/net/dm2-ana0/ufscc1/cns_view. The following command creates a VOB running on the local host winvobsrvr with storage on a Celerra: C:\> set STGPATH=\\dm2-ana0\ufscc1\cns_view. • The variable $STGPATH is set for readability. In this example.00 5 . • The storage pathname must be a valid pathname reachable from every ClearCase host in the network. Note: The /net is the automount point for all the Data Mover’s clients in the network.File system exported for NFS and CIFS clients by the Data Mover VOB tag VOB storage directory View tag View storage directory Windows tag for a UNIX VOB Storage directory for a UNIX VOB ufscc1 cns_vob_tag cns_vob. In this example. Notes for this example: • The variable %STGPATH% is set for readability. • The storage pathname must be a valid pathname reachable from every ClearCase host in the network.2. Notes for this example: • sh shell is used. The following command creates a VOB running on the local host unixvobsrvr with storage on a Celerra: $ STGPATH=/net/dm2-ana0/ufscc1/cns_vob.2.vws C:\> cleartool mkview –c “test” –tag cns_view_tag –host winviewsrvr –hpath \ %STGPATH% –gpath %STGPATH% %STGPATH% Integrating Celerra with Rational ClearCase 2002.

ccstg -proto=udp. 5.3 Create ClearCase VOBs for a Multiprotocol Environment with Storage on Celerra: With a Celerra. During the testing of Data Mover Failover and network disconnection.00. An entry in the /etc/auto_master map was specified. The following example shows the file system ufscc1 mounted with NFS v2 UDP.3 Integration Considerations All tests were performed using CIFS and NFS protocols.05. If a different NFS protocol version is used by the client.The following command creates a dynamic View running on the local host winviewsrvr with storage on a Celerra: C:\> set STGPATH=\\dm2-ana0\ufscc1\cns_view. • Working on the same elements in both UNIX and Windows environments. thus avoiding VOB/View relocation. it was deemed beneficial to keep VOBs and Views on separate Data Movers as it aided in the ability to recover. 5. a different option may be specified in the auto_ccst map.vws C:\> cleartool mkview –c “test” –tag cns_view_tag –host winviewsrvr –hpath \ %STGPATH% –gpath %STGPATH% %STGPATH% Note: You can use the syntax in the example in a .bat file. The VOB and Views pathnames will not change. you can create a Windows VOB tag for an existing UNIX VOB. Because the storage location must be reachable network-wide. This allows the following features: • Sharing of the same directories and files across UNIX and Windows environments.vbs C:\>set HPATH=/net/dm2-ana0/ufscc1/vob_unix_cns. Even though some tests experienced application errors. using either TCP or UDP over IP.05. This section describes the results of the testing and presents information you need to consider if you plan to integrate a Celerra with ClearCase 2002.vbs C:\>cleartool mktag –vob –tag /nt_vob_tag –host unixvobsrvr \ %HPATH% -gpath %GPATH% %GPATH% 5. A Data Mover or file system name change will be done only in the auto_ccst. The following command creates a Windows VOB tag for a UNIX VOB: C:\>set GPATH=\\dm2-ana0\ufscc1\vob_unix_cns. there was no loss of data. as is shown in the following example: /ccstg auto_ccstg That entry refers to the indirect map /etc/auto_ccstg that specifies the mount point for the storage: ccstg dm2-ana0:/ufscc1/& When the directory /ccstg is accessed.00 6 .3. the file system ufscc1 on dm2-ana0 will be automatically mounted. the automounter was used in the following way for convenience. It was sometimes necessary to restart ClearCase services to recover from some of these errors. • Eliminating the need for third-party NFS software on Windows and third-party CIFS software on UNIX.2.1 NFS File Access Protocols Tests with ClearCase NFS clients were executed successfully with NFS version 2 or 3.vers=2 dm2-ana0:/ufscc1/& Integrating Celerra with Rational ClearCase 2002.

4 Antivirus During testing. modify. the Celerra network interface was intentionally brought down during normal application usage.5. CIFS.3.3.3.2 Network Disconnections To investigate how an application responds. ClearCase services on the VOB server need to be restarted. it was not possible to start the ClearCase services with SHARE or UNIX security mode on the Celerra. With NFS. unlike NFS.com/software/rational/support.3 Quota Limit Exceeded To investigate how the application responds when a quota limit is exceeded. Rational recommends disabling the use of quotas on file servers used for VOBs and Views storage. For information.00 7 . EMC does not recommend that you manually disconnect the network. If the antivirus software removes a VOB component because of infection. VOBs and Views were located on separate Data Movers and the disconnection was executed on the Data Mover hosting the VOB storage because this is the most critical. an error was generated and the ClearCase services on the ClearCase VOB server needed to be restarted in order to resume operations. If the quota limit is reached during a check out.3. The file system usage was then increased by performing ClearCase operations. This behavior is the same as a native file server.5 Read-Only Mounts/Exports ClearCase operations were executed on a VOB with storage located on a read-only file system exported by Celerra. is a stateful protocol. because a network disconnect would not necessarily be a planned outage. ClearCase operations can proceed normally. it is not always possible to ensure file system availability during an entire application operation. it may be necessary to execute an undo check out before adjusting the quota limit to a new value. 5.6 CIFS Security Modes ClearCase operations were executed on a file system shared for CIFS with NT (default). the user may have issues that require a restore of the VOB. This section describes the types of errors that occurred when Celerra network disconnections occurred in a ClearCase environment. refer to: http://www-306. a file with a test virus was checked in. quotas were enabled on the file system. because ClearCase services require an authenticated Windows domain user. This statement is included in Rational Solution Id #155410410. With CIFS. For this reason. when the network was disconnected during ClearCase cycles of check out. 5. Integrating Celerra with Rational ClearCase 2002. Because the most common ClearCase operations imply writing to the file system. some operations may fail. when block quotas are exceeded on the file system hosting the VOB.3. With both NFS and CIFS. EMC does not recommend the use of antivirus software with ClearCase.05. if the interface was down for a period greater than 20 seconds. During this testing. A disk quota was intentionally set to a value lower than the disk space the user had already occupied. and check in commands. 5. The virus was detected and removed by the antivirus software. the operations stopped and resumed when the network became available. However. After this. UNIX.ibm. 5. It is necessary to give the ClearCase VOBs and Views servers read and write access to the file system exported by Celerra. and the interruptions caused by the network disconnect cause the current CIFS sessions to be lost and may result in the loss of data. and SHARE security modes.

potentially on a different Data Mover. is a stateful protocol. On the VOB server. The following scenario assumes that the fs_timefinder -S command was already executed. turn the mirror on: $ nas_fs -M on ufscc1_snap1 2. After the snapshot has completed. ClearCase will fail during the freeze/thaw. If fs_timefinder –R is run while ClearCase operations are using the standard file system. 8. unlock the VOB: $ cleartool unlock vob:<vob-cfs-tag> 9. the VOB must be locked. Wait for the command to complete. To establish the mirror: 1. the fs_timefinder –M refresh command was run with no impact for ClearCase operations during file system pause/resume. EMC does not recommend executing these commands while Windows/CIFS clients are running jobs. and is available for backup or other nonproduction purposes such as testing. lock the corrupted VOB: $ cleartool lock vob: <vob-cfs-tag> 3. restore the Snapshot Filesystem: $ /nas/sbin/rootfs_timefinder ufscc1_snap1 -R -F 4. 1. CIFS. In order to recover the situation. turn the mirror off: $ nas_fs -M off ufscc1_snap1 7.5. Wait for the command to complete. and the snapshot file system (ufscc1_snap1) exists. On the Control Station. Monitor the output of the command nas_fs -i ufscc1_snap1 and verify that the remainder value is zero. Unlock and mount the VOB. To have a consistent snapshot. you must restore a backup copy of the VOB. For testing with TimeFinder/FS on CIFS and NFS. lock the entire VOB: $ cleartool lock vob:<vob-cfs-tag> 5. On the VOB server.3. Integrating Celerra with Rational ClearCase 2002. and the interruptions from some Celerra commands cause current CIFS sessions to be lost. On the Control station. On the VOB server. The following example is a summary of the main steps to take if the VOB is corrupted and the snapshot ufscc1_snap1 contains a good copy of the VOB. Wait for the command to complete. Wait for the command to complete. unlike NFS. You can use the TimeFinder/FS feature to recover from a VOB corruption. Note that the VOB is not accessible until it is unlocked.7 SnapSure and TimeFinder/FS To investigate how an application responds to this Celerra feature.00 8 . 3. the file system ufscc1_snap1 can be mounted. 4. Celerra commands were intentionally executed during normal application usage.05. A session loss could cause data loss. 6. umount the corrupted VOB: $ cleartool umount <vob-cfs-tag> 2. EMC recommends issuing these Celerra commands only when there is no I/O activity. ClearCase works with the TimeFinder/FS feature of the Celerra if ClearCase and TimeFinder/FS operations are well coordinated. The amount of time the VOB is locked (thus unavailable) may be minimized by scheduling the TimeFinder/FS operations with the locking and unlocking of the VOB. On the VOB server. On the Control Station.

Resume ClearCase operations. During functionality testing with SnapSure. After the checkpoint is created. create a SnapSure checkpoint: $ fs_ckpt ufscc1 -C mtv3 4. 1.ckpt directory located at file system root level. ufscc1_ckpt1.05. lock the entire VOB: $ cleartool lock vob:<vob-cfs-tag> 3. On the VOB server. Resume ClearCase operations. It is being investigated by Rational. 5.bit file system ID. it was discovered that ClearCase fails when trying to access a file system where the . the . umount the corrupted VOB: $ cleartool umount <vob-cfs-tag> 2. Restore the Checkpoint file system: $ /nas/sbin/rootfs_ckpt ufscc1_ckpt1 -R 4. The amount of time the VOB is unavailable during SnapSure operations is minimal. On the Control Station. 5. the fs_ckpt –refresh command was run with no impact to ClearCase operations during file system pause/resume. On the VOB server. On the VOB server. ClearCase works with the SnapSure feature of Celerra.ckpt directory can be hidden from the NFS client through the following parameter setting: param cfs showChildFsRoot=0 Note: The Data Mover needs to be rebooted for this parameter to take effect. Unlock and mount the VOB. To create a checkpoint for the ufscc1 file system where the VOB resides: 1. In the following example we summarize the main steps to take if the VOB is corrupted and the snapshot ufscc1_ckpt1 contains a good copy of the VOB. Wait for the command to complete. it becomes available for NFS clients by means of the . Integrating Celerra with Rational ClearCase 2002.ckpt directory is present. You can further reduce this time by scheduling the fs_ckpt operations with the lock and unlock of the VOB. As a workaround.ckpt Directory Access for NFS Clients After a file system checkpoint is taken.8 Celerra . For testing with SnapSure on CIFS and NFS.3. unlock the VOB: $ cleartool unlock vob:<vob-cfs-tag> 5. can be mounted on the same Data Mover and is available for backup. On the VOB server.5. On the Control Station. the file system. You can use the SnapSure feature to recover from a VOB corruption. create the metavolume to host the checkpoint: $ nas_volume -n mtv3 -c d8 2. This directory is implemented using a 64.00 9 . The error is: Value too large for defined data type This is an application issue. A hotfix is available and referenced by Rational PMR#83654. lock the corrupted VOB: $ cleartool lock vob: <vob-cfs-tag> 3.

EMC does not recommend manually failing over a Data Mover while Windows/CIFS clients have jobs running. the error was always recoverable. after restarting the ClearCase services. that does not request write through on its own. to avoid possibility of data loss.05. 5.5. On NFS.10 Disabling Celerra File System Cache In order to enhance performance. a Data Mover failover resulted in data corruption. To avoid any chance of data corruption with an application. this is still a possibility. A Data Mover can also be failed over manually as part of maintenance activity. it is advisable to put VOBs and Views on separate storage to minimize possibility of data corruption in the event of a Data Mover Failover. In this case. such as ClearCase. EMC recommends planning a Data Mover failover for a period when there is no I/O activity. by default. in case one of the Data Movers was failed over. Integrating Celerra with Rational ClearCase 2002. ClearCase commands completed successfully during failover and failback operations. With this application. which are the most critical on a file system with cache disabled while storing the views on a file system with cache enabled (default). CIFS is a stateful protocol. On CIFS. ClearCase commands failed and could have possibly caused VOB corruption. With this application. a two times degradation of overall performance can be expected. some data could be lost and the VOB could become corrupted. the Celerra cache should be disabled. ClearCase commands failed and required ClearCase services to be restarted. therefore the interruptions caused by the failover cause current CIFS sessions to be lost and may result in the loss of data. This is done using the cifssyncwrite option provided with the server_mount command: $ server_mount server_2 –o cifssyncwrite ufscc1 /ufscc1 Note: Consider the impact that disabling the cache has on performance. If VOBs and Views were put on the same Data Mover. The response of ClearCase to a Data Mover failover was characterized by both manually failing over a Data Mover and by automatically failing over a Data Mover with active I/O. A compromise would be to store only the VOB(s). A recovery was only possible by restoring the VOB from the previous backup. Testing has shown that on average. to cache requests from the clients and flush to disk in the background.3. ClearCase could not recover the corrupted VOB. In the event the file system is unavailable due to shutdown or software failure for example. Celerra Data Movers are configured.9 Data Mover Failover and Reboot Celerra Data Movers achieve a high level of availability by automatically detecting and recovering from hardware and software failures.3.00 10 . VOBs must be locked before starting a manual failover. some operations will increase their execution time considerably. If VOBs and Views were put on two different Data Movers. Although EMC is not aware of any occurrence of this situation at a customer site. Unlike NFS. Figure 1 shows how different environment variables affect the balance between performance and high availability. It is also advisable to run frequent VOB backups as part of the enterprise backup strategy. Therefore. After restarting the service.

vbs/s/sdft/12/9/tmp_12632.05.3: No space left on device text_file_delta: Error: Trouble accessing file /net/dm2-ana0/ufscc1/cns_vob. the file system that hosted ClearCase VOBs and Views was extended during ClearCase operations without impact on the application.3.3: No space left on device cleartool: Error: Type manager text_file_delta failed create_version operation.txt text_file_delta: Error: Trouble writing to file /net/dm2-ana0/ufscc1/cns_vob. Environment Scenarios 5.txt. can be used to recover a situation where a VOB is running out of space. A possible solution is to use the nas_fs –x command to extend the file system.00 11 .11 File System Extension On NFS and CIFS. Extension of a file system. cleartool: Error: Unable to check in file500M. The above error means the file system where the VOB storage directory resides has run out of space.vbs/s/sdft/12/9/tmp_12632. through the use of the nas_fs –x command. suppose the following error occurs when you attempt to check in a file: cleartool> ci -nc file500M.High Availability QUADRANT II QUADRANT I -Celerra Cache disabled for VOBs and Views -Celerra Data Mover Failover -VOBs/Views on different Data Movers -Celerra Cache disabled for VOBs and enabled for Views -VOBs/Views on same Datamover -No VOB Backups -Celerra Cache enabled for VOBs and Views QUADRANT III QUADRANT IV High Performance Figure 1. For example. Integrating Celerra with Rational ClearCase 2002.

Version 2002.00 which can be found at: http://www-1. • Celerra User Information CD received with your Celerra.ibm. • Rational ClearCase Administrator’s Guide (UNIX/Windows). Integrating Celerra with Rational ClearCase 2002. type: $ nas_fs -x ufscc1 mtv11 This will extend the ufscc1 file system by the size of mtv11 that now can be used without the previous error.On the Control Station. Please send a message to mailto:celerradoc_comments@emc.com/support/docview.com with your opinions of this document.05. refer to the following online documentation: http://www-306.com/ and log in to Powerlink. or go to http://powerlink.com/software/rational/support/ 7 Related Information This section lists places where you can find additional information.emc.ibm. and overall quality of the user publications. organization.05.00 12 .com/software/rational/support/ 8 Comments and Suggestions About this Document Your suggestions will help us continue to improve the accuracy. 6 Troubleshooting For troubleshooting information.ibm.wss?uid=pub1g126550100 • Rational Solutions Knowledge Base Internet site: http://www-306.

Use.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS. and distribution of any EMC software described in this publication requires an applicable software license. All rights reserved. AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.05.00 13 . copying. Trademark Information P/N 300-001-116 A03 Integrating Celerra with Rational ClearCase 2002.2005 EMC Corporation. The information is subject to change without notice. EMC believes the information in this publication is accurate as of its publication date.Copyright © 1998 .