Hp Storage Mirroring V5 Software Bedienungsanleitung PDF herunterladen (Seite 85)

13 - 2

 If you rename the root folder of a connected replication set, Storage Mirroring interprets this operation as a move

from inside the replication set to outside the replication set. Therefore, since all of the files under that directory have

been moved outside the replication set and are no longer a part of the replication set, those files will be deleted from

the target copy of the replication set. This, in essence, will delete all of your replicated data from the target. If you

have to rename the root directory of your replication set, make sure that the replication set is not connected.

 When creating replication sets, keep in mind that when recursive rules have the same type (include or exclude) and

have the same root path, the top level recursive rule will take precedence over lower level non-recursive rules. For

example, if you have c:\data included recursively and c:\data\logs included nonrecursively, the top level rule, c:\data,

will take precedence and the rule c:\data\logs will be discarded. If the rules are different types (for example, c:\data

is included and c:\data\logs is excluded), both rules will be applied as specified.

 Including and excluding files

 Do not exclude Microsoft Office temporary files from your replication set. When a user opens a Microsoft Office

file, a temporary copy of the file is opened. When the user closes the file, the temporary file is renamed to the original

file and the original file is deleted. Storage Mirroring needs to replicate both the rename and the delete. If you have

excluded the temporary files from your replication set, the rename operation will not be replicated, but the delete

operation will be replicated. Therefore, you will have missing files on your target.

 When Microsoft SQL Server databases are being replicated, you should always include the tempdb files, unless you

can determine that they are not being used by any application. Some applications, including Prophecy, PeopleSoft, and

BizTalk

, write data to the tempdb file. You can, most likely, exclude temporary databases for other database

applications, but you should consult the product documentation or other support resources before doing so.

 Some applications create temporary files that are used to store information that may not be necessary to replicate.

If user profiles and home directories are stored on a server and replicated, this could result in a significant amount

of unnecessary data replication on large file servers. Additionally, the \Local Settings\Temporary Internet Files

directory can easily reach a few thousand files and dozens of megabytes. When this is multiplied by a hundred users

it can quickly add up to several gigabytes of data that do not need to be replicated.

 Creating replication sets that only contain one file may cause unexpected results. If you need to replicate just one

file, add a second file to the replication set to ensure the data is replicated to the correct location. (The second file

can be a zero byte file if desired.)

 Backups

 Storage Mirroring does not replicate the last access time if it is the only thing that has changed. Therefore, if you are

performing incremental or differential backups on your target machine, you need to make sure that your backup

software is using an appropriate flag to identify what files have been updated since the last backup. You may want to

use the last modified date on the file rather than the date of the last backup.

 Virus protection

 Virus protection software on the target should not scan replicated data. If the data is protected on the source,

operations that clean, delete, or quarantine infected files will be replicated to the target by Storage Mirroring. If the

replicated data on the target must be scanned for viruses, configure the virus protection software on both the source

and target to delete or quarantine infected files to a different directory that is not in the replication set. If the virus

software denies access to the file because it is infected, Storage Mirroring will continually attempt to commit

operations to that file until it is successful, and will not commit any other data until it can write to that file.

Replication capabilities

Storage Mirroring replicates file and directory data stored on any Windows file system (FAT, FAT32, NTFS4, and NTFS5).

Replicated items also include Macintosh

files, compressed files, NTFS attributes and ACLs (access control list), dynamic

volumes, files with alternate data streams, sparse files, and encrypted files. Files can be replicated across mount points, even

though mount points are not created on the target. Some reparse points are replicated, including CommVault

Data Migrator

and BridgeHead Software HT FileStore.

Storage Mirroring does not replicate items that are not stored on the file system, such as physical volume data and registry

based data. Addtionally, Storage Mirroring does not replicate NTFS extended attributes, registry hive files, Windows or any

system or driver pagefile, system metadata files ($LogFile, $Mft, $BitMap, $Extend\\$UsnJrnl, $Extend\\$Quota,

$Extend\\$ObjId, and $Extend\\$Reparse), hard links, junction points, or the Storage Mirroring disk-based queue logs. The

only exception to these exclusions is for the Server Recovery Option and Full-Server Failover. If you are protecting your

system state and data, Storage Mirroring will automatically gather and replicate all necessary system state data, including files

for the operating system and applications.

Note the following replication caveat.

1. If you have mixed file systems, keep in the mind the following.

a. If, on your source, you have a FAT volume mounted on a directory which resides on an NTFS volume, these files will

not be mirrored, regardless of the target file system. Replication will work correctly. To work around this issue,

make sure both volumes are NTFS.

1 2 ... 80 81 82 83 84 85 86 87 88 89 90 ... 211 212

Kommentare zu diesen Handbüchern

Keine Kommentare

Hp Storage Mirroring V5 Software Bedienungsanleitung Seite 85

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Lager Hp Storage Mirroring V5 Software