Data Storage and Management
Data Storage and Management |
|
Remote Storage is integrated closely with Windows 2000. Table 2.12 provides details of this integration and describes the interfaces between Remote Storage and Windows 2000.
Table 2.12 Remote Storage and Windows 2000 Integration
| Interface | Description |
|---|---|
| Placeholder format and reparse points | A placeholder has the system-defined $REPARSE_POINT attribute set with information that can identify and retrieve the unnamed data attribute from remote storage. The unnamed data attribute is in remote storage and its length is zero bytes. The reparse point type is Remote Storage.
The recall mechanism is based on the reparse point being identified by NTFS and is an efficient mechanism that uses this information when recalling a file. |
| File size of a placeholder | The logical file size of the unnamed data attribute of a placeholder is the size of the unnamed data attribute as it was before it was truncated. The physical size of the unnamed data attribute of a placeholder is zero bytes. |
| Disk quotas and remote storage | Disk quotas do not change. Disk quotas are based on the logical file size which is not changed by Remote Storage, therefore the amount of space in use on a volume is not reduced or changed by having data in remote storage. |
| Remote Storage stage change | Remote Storage supports a Distributed Component Object Model (DCOM) interface–based mechanism that can change the system status. |
| Event Log usage | Major Remote Storage system events are logged in the Windows 2000 Event Log. The Windows 2000 Event Viewer is used to see the logged events.
The following events are optionally logged in the Windows 2000 Event Log:
|
| Windows 2000 Job Scheduler | Remote Storage uses the Windows 2000 Job Scheduler to schedule Remote Storage jobs. Job status can be monitored from within the Remote Storage snap-in.
Depending on the Job Scheduler, a job window can be specified that limits the amount of time spent in a single scan. This is useful because the system might have a large amount of data to manage and the scan might initially take too much time. A bookmark is kept where the scan stopped so the scan can continue from that point the next time it is run. |
| Windows 2000 registry usage | Remote Storage uses the registry to keep persistent information about startup, including the programs needed to initialize setup. |
| Windows 2000 client time-out on recall | The registry entry HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services\LanmanWorkstation\parameters \OfflineFileTimeOutIntervalInSeconds controls the time-out period that the client uses when sending requests to a server. The default is value is 900 (or 15 minutes). You can increase this value on all Windows 2000 clients that open files on the volumes managed by Remote Storage. |