会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Asynchronously shadowing record updates in a remote copy session using
track arrays
    • 使用轨道数组异步地在远程复制会话中镜像记录更新
    • US5720029A
    • 1998-02-17
    • US506490
    • 1995-07-25
    • Robert Frederic KernWilliam Frank MickaClaus William MikkelsenRobert Wesley ShomlerWarren Keith StanleyRichard Kent Treiber
    • Robert Frederic KernWilliam Frank MickaClaus William MikkelsenRobert Wesley ShomlerWarren Keith StanleyRichard Kent Treiber
    • G06F11/20G06F11/00
    • G06F11/2074G06F11/2064
    • A disaster recovery system providing asynchronous remote data shadowing between a primary and a secondary site uses a pair of track arrays for each primary data storage device of a remote copy pair to monitor which record updates are in transit between the primary site and the secondary site. A host processor at the primary site of the disaster recovery system transfers a sequentially consistent order of copies of record updates to the secondary site for back-up purposes. The copied record updates are stored on the secondary data storage devices which form remote copy pairs with the primary data storage devices at the primary site. One track array, the active track array, is used to set elements according to which tracks on the primary data storage device receive record updates from the host processor at the primary site. The other track array, the recovery track array, designates which record updates comprise the copied record updates currently transferred from the primary site to the secondary site for data shadowing and is used for recovery should an error interrupt the transfer. The track arrays are toggled once the consistency group transfer completes, the recovery track array becoming the active track array and the active track array becoming the recovery track array.
    • 在主站点和辅助站点之间提供异步远程数据镜像的灾难恢复系统使用远程副本对的每个主数据存储设备的一对轨道阵列来监视主站点和辅助站点之间传输的记录更新。 在灾难恢复系统的主站点处的主机处理器将记录更新的副本顺序传送到辅助站点以进行备份。 复制的记录更新存储在辅助数据存储设备上,其与主站点上的主数据存储设备形成远程副本对。 一个磁道阵列,主动磁道阵列,用于根据主数据存储设备的哪些磁道在主站点处从主机处理器接收记录更新来设置元素。 另一个轨道阵列(恢复轨道阵列)指定哪个记录更新包括当前从主站点传送到次站点的复制记录更新以用于数据阴影,并且如果错误中断传输,则用于恢复。 一旦一致性组传输完成,轨道阵列就会切换,恢复轨道阵列成为主动轨道阵列,而主动轨道阵列成为恢复轨道阵列。
    • 9. 发明授权
    • Data storage subsystem with fairness-driven update blocking
    • 数据存储子系统具有公平驱动的更新阻塞
    • US06487645B1
    • 2002-11-26
    • US09519080
    • 2000-03-06
    • Brian Dow ClarkWilliam Frank MickaWarren Keith Stanley
    • Brian Dow ClarkWilliam Frank MickaWarren Keith Stanley
    • G06F1200
    • G06F3/0656G06F3/0619G06F3/0659G06F3/067G06F11/2066G06F11/2074Y10S707/99953Y10S707/99955
    • When a primary data storage subsystem receives updates for local storage and mirroring at a counterpart secondary storage subsystem, the primary subsystem institutes device-specific, fairness-driven update blocking to avoid overrunning the primary subsystem's update buffer with updates destined for any one device. Broadly, the primary subsystem first receives update requests, then logs the updates in an update buffer, then stores the logged updates in primary storage, and finally copies the updates to the secondary storage subsystem. Each update request includes update data and also identifies a targeted logical device, physical device, or other subpart of primary storage. The primary subsystem maintains a counter or other update activity indicator that represents update activity for each storage subpart, such as the number of updates stored in the buffer. For each update request, the primary subsystem determines whether target subpart's update activity exceeds a prescribed level. If not, the update data is stored in primary storage. Otherwise, if the update activity is excessive, the primary subsystem rejects the update. Optionally, the primary subsystem may selectively override certain rejections to prevent completely blocking updates for that subpart.
    • 当主数据存储子系统接收本地存储的更新并在对应的辅助存储子系统中进行镜像时,主要子系统将进行特定于设备的公平驱动的更新阻止,以避免超过主子系统的更新缓冲区,并更新目的地为任何一个设备。 一般来说,主子系统首先接收更新请求,然后将更新记录在更新缓冲区中,然后将记录的更新存储在主存储中,最后将更新复制到辅助存储子系统。 每个更新请求包括更新数据,并且还标识目标逻辑设备,物理设备或主存储器的其他子部分。 主子系统维护计数器或其他更新活动指示符,表示每个存储子部分的更新活动,例如存储在缓冲区中的更新次数。 对于每个更新请求,主子系统确定目标子部分的更新活动是否超过规定级别。 如果没有,则更新数据存储在主存储器中。 否则,如果更新活动过多,则主子系统将拒绝更新。 可选地,主子系统可以选择性地覆盖某些拒绝以防止完全阻止该子部分的更新。