4.0
Table Of Contents
- Title Page
- Contents
- Working with the Avid ISIS Management Console
- Configuring the Management Console
- Managing Avid ISIS Hardware
- Managing Storage Managers
- Storage Manager Column List
- Viewing Storage Manager Details
- Storage Manager Status
- Adding (Binding) Storage Managers to the ISIS File System
- Removing (Unbinding) Storage Managers from the ISIS File System
- Clearing Network Degraded Status Messages
- Upgrading ISIS 7000 Storage Manager
- Adding Storage Elements to the File System
- Removing Storage Elements from the ISIS 7000 Shared Storage Network
- Removing Orphaned Storage Managers
- Managing Storage Elements
- Managing ISIS 7000 Switch Blades
- Managing the Engine
- Managing Storage Managers
- Avid ISIS Control Panels
- ISIS Launch Pad
- Avid ISIS System Director Control Panel
- Opening the System Director Control Panel
- Starting and Stopping the System Director Service
- Changing System Director Virtual Name
- Monitoring System Director Status
- Using the ISIS System Director Memory Log Viewer
- Working with File System Operations
- Monitoring Metadata Status
- Resetting the Administrator Password
- Managing Active Clients
- Managing Storage Groups and Workspaces
- Managing Storage Groups
- Storage Groups List
- Viewing Storage Group Details
- Storage Groups on ISIS 7000
- Storage Groups on ISIS 5000
- Adding Storage Elements to Storage Groups
- Adding New Storage Groups
- Removing ISIS Storage Elements from Storage Groups
- Adding ISIS 7000 Storage Elements from Another Storage Group
- Adding ISIS 7000 Storage Managers Previously Used in Another Environment
- Deleting Storage Groups
- Minimum Storage Space Requirement
- Managing Workspaces
- Workspaces List
- Workspaces Considerations
- Using the Workspace Size Graph
- Viewing Workspace Details
- Adding New Workspaces
- Duplicating Workspaces
- Renaming Workspaces
- Protecting ISIS 7000 Workspaces
- Setting ISIS 7000 Workspace Protection
- Moving ISIS 7000 Workspaces
- Resizing Workspaces
- Setting Event Triggers
- Deleting Workspaces
- Managing Workspace Access Privileges
- Redistributing ISIS 7000 Data
- Redistributing ISIS 5000 Data
- Managing Storage Groups
- Managing Clients
- Managing Connections
- System Monitoring and Diagnostics
- Hardware Monitoring Service (ISISI 5000 Only)
- System Information Page
- System and Administration Log Pages
- ISIS Snapshots Page
- Profiler Page
- System Status History Page
- ISIS Toolbox Page
- Network Utilities Page
- Monitor Tool (ISIS 7000 Only)
- Agent Settings Page
- Monitoring Avid ISIS with SNMP
- Avid ISIS Storage Manager Agent
- Avid ISIS 7000 Switch Blade Agent
- Avid ISIS SNMP MIB Reference
- Avid ISIS E-mail Notification List
- Index
Managing Storage Groups
94
Storage Group and Chunk Sizes
Storage Elements are combined to create Storage Groups in the ISIS file system. When you bind
a Storage Element you must select either 512 KB (default) or 256 KB chunk sizes. Earlier Avid
ISIS releases used 256 KB chunk sizes. These bound Storage Elements must all be of the same
chunk size when you configure your Storage Group.
n
Avid ISIS switch hardware shipped with v1.x (ISS1000 and IXS1000) does not support 512 KB
chunk sizes. If you have Avid ISIS v2.x software running on v1.x switches, you must select the
256 KB chunk size when adding Storage Elements to the file system to create Storage Groups.
You cannot change the chunk size of a Storage Group once the Storage Group has been created.
To change the chunk size of an existing Storage Group, you must delete the Storage Group and
create a new Storage Group with the desired chunk size. The chunk size selection is only
available when adding the Storage Elements.
Storage Blades and Chunk Sizes
There are two drives in all Avid ISIS 7000 ISBs. ISBs are identified by the total amount of
storage in the ISB; for example, an ISB with the two 1 terabyte (TB) drives are referred to as
i2000s. All ISBs (i500, i1000, i2000, and i4000) support the 512 KB chunk size, but only the
i500 and i1000 support the 256k chunk size. The i2000 and i4000 ISBs require 512 KB chunk
size. In addition you must have v2.x switch hardware (ISS2000 and IXS2000) to use the 512 KB
chunk size.
RAID 6 Workspace, Single ISB Failure
When there is a single ISB failure in an ISIS Workspace configured with RAID 6 protection, the
Workspace continues to function normally at a lower bandwidth. For mirrored Workspace, see
“Mirrored Workspace, Single ISB Failure” on page 95.
After confirming the failure of an ISB, it is highly recommended that you initiate the remove
redistribution process of the failed ISB immediately. There are two benefits to doing this:
• First, immediately upon initiation of the remove redistribution, all new writes to the
Workspace have the full benefit of RAID-6 protection (dual-parity protection).
• Second, upon completion of the remove redistribution process, existing data in the
Workspace is once again fully protected. Prior to completion, if another ISB were to fail, the
Workspace would be in an unprotected state (though no data would be lost).