Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Reroute with Clone in a Multi-Node Deduplication System

IP.com Disclosure Number: IPCOM000227385D
Publication Date: 2013-May-06
Document File: 4 page(s) / 247K

Publishing Venue

The IP.com Prior Art Database

Related People

Lei Hu Zhang: INVENTOR

Abstract

Multi-nodes with global deduplication solutions provide more capacity for deduplication data and good extensibility and deduplication rate. But, if new nodes are added, rerouting jobs are always scheduled to transfer deduplication data across nodes to ensure that deduplication data with the same fingerprint range is stored on the same node. This solution provides an efficient way to move deduplication data across multi-nodes by means of clone technology provided by modern storage.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 4

Reroute with Clone in a Multi-Node Deduplication System

Lei Hu Zhang

Symantec Corporation

Abstract

Multi-nodes with global deduplication solutions provide more capacity for deduplication data and good extensibility and deduplication rate. But, if new nodes are added, rerouting jobs are always scheduled to transfer deduplication data across nodes to ensure that deduplication data with the same fingerprint range is stored on the same node. This solution provides an efficient way to move deduplication data across multi-nodes by means of clone technology provided by modern storage. Copyright © 2013 Symantec Corporation. All rights reserved.

1


Page 02 of 4

Copyright © 2013 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. For a full list of Symantec trademarks, please visit http://www.symantec.com/about/profile/policies/trademarks/currentlist.jsp

Any Symantec products described in this document are distributed under licenses restricting their use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 United States

http://www.symantec.com

Copyright © 2013 Symantec Corporation. All rights reserved. 2


Page 03 of 4

Reroute with Clone in a Multi-Node Deduplication System

Problem Statement

     Normally, in certain data backup and storage systems, a node stores deduplication data within the same fingerprint range on the same node. But, if new nodes are added, a new fingerprint layout will be created, then each node will only save deduplication data within its new fingerprint range. Other deduplication data out of that range has to be moved to newly added nodes. This process is often called reroute.

     According to the current reroute process, each source node has to scan its entire data file and send related fingerprint and related data segments to new nodes one by one across the network. The target node receiving this information will save data segments into local data files and rebuild its local deduplication data index. After that, the source nodes will delete the index of deduplication dat...