Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2275eaf3f6a79f3

Jump to content

Disk staging

From Wikipedia, the free encyclopedia
(Redirected from D2D2T)

Disk staging is using disks as an additional, temporary stage of backup process before finally storing backup to tape.[1] Backups stay on disk typically for a day or a week, before being copied to tape in a background process and deleted afterwards.

The process of disk staging is controlled by the same software that performs actual backups, which is different from virtual tape library where intermediate disk usage is hidden from main backup software. Both techniques are known as D2D2T (disk-to-disk-to-tape).

Restoring data

[edit]

Data is restored from disk if possible. But if the data exists only on tape it is restored directly (no backward-staging on restore).

Reasons

[edit]

Reasons behind using D2D2T:

  • increase performance of small, random-access restores: disk has much faster random access than tape
  • increase overall backup/restore performance: although disk and a tape have similar streaming throughput, you can easily scale disk throughput by the means of striping (and tape-striping is a much less established technique)[2]
  • increase utilization of tape drives: tape shoe-shining effect is eliminated when staging (note that it may still happen on tape restores)

See also

[edit]

References

[edit]
  1. Preston, W.C. (2007). Backup & Recovery: Inexpensive Backup Solutions for Open Systems. O'Reilly Media, Inc. pp. 219–220. ISBN 978-0-596-55504-7. Retrieved 8 May 2018.
  2. "How Backup to Disk to Tape Works". documentation.arcserve.com. Retrieved 2026-01-10.