Atom feed of this document
 
 
 

 12.1. Bulk Importing of Data

If you have a large amount of data to import into Cloud Files, bulk importing of data is available. With bulk importing, you send a physical device that contains your data to Rackspace, and Rackspace loads it directly into Cloud Files. By doing this, you avoid the time and cost of uploading large amounts of data over the Internet. After the transfer is complete, Rackspace either ships your device back to you, or destroys it after degaussing, whichever you prefer.

[Note]Note

Bulk import is available in U.S. data centers and in the Sydney data center only. However, if you have a need for bulk importing in another data center outside of the U.S., contact Rackspace support to see what other options you might have. They will be interested in specifics like the amount of data you need to work with.

Rackspace accepts USB, SATA, and eSATA devices. Your file system can be NTFS, ext2, ext3, ext4, or FAT32. Because Cloud Files does not use hierarchical directory structures, nested subdirectories in your data are converted to object names. Your top-level folders become containers, and nested directory names become part of the object names. For example, Chapter28/Ahab/ivoryleg results in a container named Chapter28 with an object named Ahab/ivoryleg inside of it. For more information about simulating directory structures in Cloud Files, see Chapter 6, Pseudo Hierarchical Folders and Directories.

To begin the bulk import process, contact Rackspace support technicians. You will be assigned a migration specialist who can answer any questions you might have during the process. You are notified when Rackspace receives your device, begins the data import, completes the data import, and ships back or destroys the device.



loading table of contents...