Votos - 0, Puntuación media: 0
(
)
)
|
Otros manuales para este modelo:
datos de dispositivos de procesamiento - HP 600 All-in-One 1.5TB Ultrium 920 Promo Bundle (195.48 kb)
Resumen del manual
All-in-One Storage Manager
When a single iSCSI LUN is presented to a SQL or Exchange server, the database
file and database transaction log file are both created on the volume contained
in the iSCSI LUN. If the iSCSI LUN was created on the AiO as a user-defined
application, ASM will discover that the database files are now in the volume and it
will promote the user-defined application to a SQL Server or Exchange application
instance. If the SQL Server or Exchange application instance is replicated to
another system, the iSCSI LUN is replicated to the target system twice: once for the
database file and again for the log file.
In general, the amount of space used on the replication target is equal to the size
Description
of each iSCSI LUN that contains multiple components multiplied by the number
of components in that iSCSI LUN. If multiple components exist in multiple iSCSCI
LUNs, the sum of the product of the sizes is the total consumed space. Snapshot
space usage is similar.
For example, a single iSCSI LUN of 200MB that contains a volume that has
both the database file and the log file would consume 400 MB of space on the
replication target (200MB x 2 = 400MB). Likewise, an Exchange server with one
storage group of three mail stores on one iSCSI LUN of 500MB and the log and
public store on a separate iSCSI LUN of 250 MB would consume 2000MB of
space on the replication target (500MB x 3 + 250MB x 2).
As a best practice, when configuring storage for SQL Server and Exchange
databases, create the database files on one iSCSI LUN and create the associated
Workaround log and system files on a separate iSCSI LUN. This way, when storage areas are
replicated, there wil be one component per iSCSI LUN and space will be utilized
on the replication target more efficiently.
Issue:
Data volumes are not remounted after Quick Restore
Mounted data volumes are not remounted after performing an AiO Quick Restore.
Description
These data volumes are not damaged or destroyed but they are not visible in the
ASM user interface after a Quick Restore operation.
In order to restore the mount points to their original locations, you must record
them prior to running Quick Restore.
1. Using Windows Disk Manager, record the mount points of the volumes within
the root directory of each volume.
Workaround 2. After running Quick Restore, scan the system to find data volumes that are not
assigned drive letters.
3. Temporarily mount the volumes that are not assigned drive letters.
4. Locate the recorded list of mount points and remount the temporarily mounted
volumes to the correct locations according to the record.
Data Protector Express
This section describes issues related to HP StorageWorks Data Protector Express running on All-in-One
Storage Systems.
NOTE:
Changes made using Data Protector Express are not always reflected in Al -in-One Storage Manager.
Data Protector Express
Issue:
Changes made to a backup using Data Protector Express are not always reflected in All-in-One
Storage Manager
If you use Data Protector Express to change the rotation type associated with a
Description
backup to Custom rotation, the change is not reflected in All-in-One Storage
Manager.
8
...Otros modelos de este manual:
datos de dispositivos de procesamiento - HP 600 All-in-One 876GB SAS plus Ultrium 920 Promo Bundle (136.15 kb)
datos de dispositivos de procesamiento - HP AiO400r Storage System (136.15 kb)
datos de dispositivos de procesamiento - HP AiO400t Storage System (136.15 kb)
datos de dispositivos de procesamiento - HP AiO600 1.8TB SAS Smart Buy Storage System (136.15 kb)