{"id":5732,"date":"2026-10-26T12:00:16","date_gmt":"2026-10-26T11:00:16","guid":{"rendered":"https:\/\/www.archiware.com\/blog\/?p=5732"},"modified":"2026-10-26T13:59:54","modified_gmt":"2026-10-26T12:59:54","slug":"remote-archive-to-lto-tape","status":"publish","type":"post","link":"https:\/\/www.archiware.com\/blog\/de\/remote-archive-to-lto-tape\/","title":{"rendered":"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud"},"content":{"rendered":"<h2 class=\"wp-block-heading\">Why your own remote archive on tape<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ask most IT teams where the offsite copy of their archive should live, and the answer is the cloud. Yet many organisations choose their own offsite copy on LTO tape at a second site as an alternative. The reasons are compelling:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Predictable costs.<\/strong> A one-off investment in a library and licences instead of storage fees that grow every month.<\/li>\n\n\n<li><strong>No egress or retrieval fees.<\/strong> Getting large amounts of data back out of a cloud archive is often the expensive part. With your own tapes, a restore costs nothing extra.<\/li>\n\n\n<li><strong>Data sovereignty.<\/strong> The data stays in your own buildings, in your own country, under your own control.<\/li>\n\n\n<li><strong>A real air gap.<\/strong> Tapes outside the drive are offline and out of reach of ransomware.<\/li>\n\n\n<li><strong>No vendor lock-in.<\/strong> Data written in the open LTFS format can be read by any LTFS-capable software and drive, now and decades from now.<\/li>\n\n\n<li><strong>Use what is already there.<\/strong> A second site, existing storage and existing tape know-how all become part of the solution.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This article shows how to build such a remote tape archive with Archiware P5, even when the link between the sites is far too slow to feed a tape drive directly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A typical scenario<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Take an organisation with 200 TB of cold data at its main site: data that has not been touched for years but has to stay available. For media companies this is on the small side, but the principle is the same at larger volumes. New and changed data keeps arriving, for example whenever more data is moved to the archive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A second site is connected by a WAN link of 400 Mbit\/s, about 50 MB\/s, which is often shared with other traffic such as replication. The second copy has to be on tape at that site, because there is neither the space nor the budget for another 200 TB of disk there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At full utilisation, the initial 200 TB alone take at least six to seven weeks over this link. After that, only the increments have to travel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How large are those increments? That depends on the industry. As a planning assumption, archives grow by 20 to 60 percent a year, with media companies often at the upper end. For 200 TB, the first year looks like this:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Growth per year<\/th><th>Increment<\/th><th>Average per day<\/th><th>LTO-9 tapes per year<\/th><\/tr><\/thead><tbody><tr><td>20 % (mostly structured data)<\/td><td>40 TB<\/td><td>approx. 110 GB<\/td><td>2 to 3<\/td><\/tr><tr><td>40 % (typical)<\/td><td>80 TB<\/td><td>approx. 220 GB<\/td><td>4 to 5<\/td><\/tr><tr><td>60 % (data-intensive, media)<\/td><td>120 TB<\/td><td>approx. 330 GB<\/td><td>approx. 7<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">The technical challenge<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">How do you archive to LTO tape over a WAN link? Technically, it should simply work: there is a network connection between the two sites, so why not treat it like a local setup and write straight to the tape drive at the other end?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is not quite that simple. An LTO drive needs a minimum amount of data per second to keep the tape moving.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Drives can adapt their speed to the incoming data (speed matching). A half-height LTO-9 drive with LTO-9 media can slow down to 177 MB\/s, about 1.4 Gbit\/s (<a href=\"https:\/\/www.ibm.com\/docs\/en\/ts2900tapeautoloader?topic=features-speed-matching\">IBM<\/a>). Every drive writing at the same time needs at least this sustained net throughput. Full-height drives need even more.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If less data arrives, the drive stops, rewinds and restarts over and over. This <a href=\"\/blog\/why-lto-tape-drives-never-reach-their-rated-speed\/\">shoe-shining<\/a> makes throughput collapse and wears out drives and tapes much faster than intended.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In our scenario, the link delivers about 50 MB\/s, less than a third of the lowest speed-matching step. And even a link that is nominally fast enough fails if it is shared or its speed fluctuates. The tape drive therefore has to be decoupled from the WAN: data needs to be buffered at the remote site and written to tape from there at full speed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Two independent archive systems<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The solution uses two servers, one at each site, both running the same product: P5 Archive. Only their configuration differs. One sends the data via S3, the other receives it through the S3 Object Archive feature of P5 Archive and writes it to tape.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Main site: P5 Archive server, sending via S3<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A server with access to the online storage. Scheduled archive plans, for example nightly, pick up new and changed files, record them in a searchable index and send them to the remote site via S3. The data stays on the existing storage and remains available to users. No tape hardware is needed at this site.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Remote site: P5 Archive server, receiving via S3<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A server with staging storage (DAS or NAS) and the LTO tape library attached. Using the S3 Object Archive feature, it presents itself to the main site as an S3 object store. Each bucket is linked to a P5 tape pool and has its own archive index. Incoming objects land in the staging area, and P5 writes them to tape automatically in the open LTFS format. It frees the staging space once the data is safely on tape and notifies you when new media is needed.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram.png\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"408\" src=\"\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-1024x408.png\" alt=\"Offsite archive with two P5 installations: P5 Archive at the main site sends via S3 to P5 S3 Object Archive with staging and LTO-9 tape library at the remote site\" class=\"wp-image-5731\" srcset=\"https:\/\/www.archiware.com\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-1024x408.png 1024w, https:\/\/www.archiware.com\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-300x120.png 300w, https:\/\/www.archiware.com\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-768x306.png 768w, https:\/\/www.archiware.com\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-1536x612.png 1536w, https:\/\/www.archiware.com\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-2048x816.png 2048w, https:\/\/www.archiware.com\/blog\/wp-content\/uploads\/2026\/10\/remote-archive-to-lto-tape-diagram-18x7.png 18w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><figcaption class=\"wp-element-caption\">Offsite archive with two P5 installations<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This setup fully decouples the WAN from the tape drive: data arrives at whatever speed the link provides, and the drive writes from local staging at full speed. There are no separate processes to coordinate, because change detection happens at the main site through the P5 Archive index, while the remote site simply accepts and stores objects. Each site keeps its own index: the main site knows what was archived, and the remote site knows which objects are on which tapes, so it can restore the data on its own. And because the two installations talk standard S3, they are only loosely coupled.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Sizing the staging area<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The staging area is the buffer that makes the decoupling work. It does not need to hold the whole archive. It only has to bridge the time during which tape output is not possible, for example when all tapes in the library are full and nobody is on site to load new ones. If it fills up, the remote site simply pauses. Files not yet transferred go out automatically with the next scheduled archive run.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At a fully used 400 Mbit\/s link, about 4.3 TB arrive per day:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Gap to bridge<\/th><th>Duration<\/th><th>Staging capacity<\/th><\/tr><\/thead><tbody><tr><td>Weekend<\/td><td>approx. 2.5 days<\/td><td>approx. 11 TB<\/td><\/tr><tr><td>Long weekend<\/td><td>approx. 4 days<\/td><td>approx. 17 TB<\/td><\/tr><tr><td>One week<\/td><td>7 days<\/td><td>approx. 30 TB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">One weekend plus some headroom, roughly 12 to 15 TB, is a sensible starting point. The link only runs at full load during the initial transfer. Afterwards, the increments are much smaller, and the same staging area covers much longer gaps.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Restore<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In everyday use, users read the archived data directly from the existing storage at the main site. A restore from tape is only needed when data there has been lost or damaged.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Restores start at the main site: search the P5 Archive index, select what you need and restore it. Because the remote copy is on tape, P5 first reads the data from tape at the remote site and then transfers it over the WAN.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common practice in the cloud<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The principle is well established: cloud archive tiers such as AWS Glacier Flexible Retrieval and Glacier Deep Archive work the same way: data is written through S3, the provider moves it to a slower, cheaper medium, and a restore first recalls the data before it can be read. P5 S3 Object Archive behaves exactly like that towards the main site. The difference is where the tapes are: in your own library, at your own second site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Alternatives<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">P5 S3 Object Archive works with almost any network. If your network meets stricter requirements, or if a second copy on disk is planned anyway, other approaches are possible as well. Each comes with its own prerequisites.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Remote P5 Client<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A P5 Client at the main site sends the data over the WAN directly to the P5 server with the tape library at the remote site.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This requires a sustained net throughput of at least 177 MB\/s, about 1.4 Gbit\/s, for every half-height LTO-9 drive writing at the same time. Latency is less critical: the data travels as a continuous stream over TCP, and the P5 server buffers it before the drive. No additional components are needed, and the P5 Client is included in the P5 Archive base licence. Where a fast, stable link is available, this is the simplest and most cost-effective option.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Remote tape via iSCSI with ATTO XstreamCORE<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The tape library at the remote site is connected through an ATTO XstreamCORE bridge, and the P5 server at the main site addresses it over the network as if it were attached locally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The bandwidth requirement is the same as above, and latency matters a lot as well: the SCSI commands themselves cross the WAN, and tape drives typically process one write command at a time. The maximum throughput is then roughly the block size divided by the round-trip time. With 1 MB blocks and 10 ms, that is about 100 MB\/s, already below 177 MB\/s. Exact limits depend on block size and bridge configuration, and ATTO can advise on both.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The only additional component is the ATTO XstreamCORE bridge at the remote site, and no second P5 installation is needed. This option fits when the sites are close, for example on a campus or within a metro area, with a fast, dedicated, low-latency link, and the library should behave like local hardware.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Disk-to-disk-to-tape (D2D2T)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Data is first replicated to disk at the remote site and then written to tape locally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There is no minimum network requirement: how long the transfer takes depends on the link. In return, the remote site needs disk storage for the full data set and a server, plus a replication solution and an archive system that writes the data to tape. This approach fits when a second copy on disk is wanted anyway, for example for fast restores at the remote site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fazit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An offsite copy on tape needs neither the cloud nor a fast link. With P5 Archive at the main site and P5 S3 Object Archive at the remote site, any organisation with two locations and a tape library can run its own remote archive: independent of WAN speed, with two independent indexes and full control over its data. Where the network is fast enough, a remote P5 Client or iSCSI with ATTO XstreamCORE are good alternatives; where a disk copy is wanted anyway, D2D2T is.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Want to find out which approach fits your environment? Book an <a href=\"\/ask-archiware\">\u201cAsk Archiware\u201d call<\/a> or contact your Archiware reseller.<\/p>","protected":false},"excerpt":{"rendered":"<p>Why your own remote archive on tape Ask most IT teams where the offsite copy of their archive should live, and the answer is the cloud. Yet many organisations choose their own offsite copy on LTO tape at a second<\/p>","protected":false},"author":7,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,43,55],"tags":[388,229,95,341,351,162,151],"class_list":["post-5732","post","type-post","status-publish","format-standard","hentry","category-archive","category-p5","category-storage","tag-archive-to-lto-tape","tag-lto-archive","tag-lto-tape","tag-lto-9","tag-offsite-archive","tag-p5-archive","tag-s3"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Remote Archive to LTO Tape: An Offsite Alternative to the Cloud - Archiware Blog<\/title>\n<meta name=\"description\" content=\"Build your own offsite archive on LTO tape as an alternative to the cloud: P5 Archive and P5 S3 Object Archive decouple a slow WAN link from the tape drive.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.archiware.com\/blog\/de\/remote-archive-to-lto-tape\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud - Archiware Blog\" \/>\n<meta property=\"og:description\" content=\"Build your own offsite archive on LTO tape as an alternative to the cloud: P5 Archive and P5 S3 Object Archive decouple a slow WAN link from the tape drive.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.archiware.com\/blog\/de\/remote-archive-to-lto-tape\/\" \/>\n<meta property=\"og:site_name\" content=\"Archiware Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-26T11:00:16+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-26T12:59:54+00:00\" \/>\n<meta name=\"author\" content=\"Josef Doods\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Josef Doods\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"9\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/\"},\"author\":{\"name\":\"Josef Doods\",\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/#\\\/schema\\\/person\\\/1bcb1ac5602a5577eecb07963dda49bf\"},\"headline\":\"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud\",\"datePublished\":\"2026-10-26T11:00:16+00:00\",\"dateModified\":\"2026-10-26T12:59:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/\"},\"wordCount\":1758,\"keywords\":[\"archive to LTO tape\",\"LTO archive\",\"LTO tape\",\"LTO-9\",\"offsite archive\",\"P5 Archive\",\"S3\"],\"articleSection\":[\"Archive\",\"P5\",\"Storage\"],\"inLanguage\":\"de\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/\",\"url\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/\",\"name\":\"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud - Archiware Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/#website\"},\"datePublished\":\"2026-10-26T11:00:16+00:00\",\"dateModified\":\"2026-10-26T12:59:54+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/#\\\/schema\\\/person\\\/1bcb1ac5602a5577eecb07963dda49bf\"},\"description\":\"Build your own offsite archive on LTO tape as an alternative to the cloud: P5 Archive and P5 S3 Object Archive decouple a slow WAN link from the tape drive.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/remote-archive-to-lto-tape\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/\",\"name\":\"Archiware Blog\",\"description\":\"Archiware P5 and Archiware Pure tech info\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/#\\\/schema\\\/person\\\/1bcb1ac5602a5577eecb07963dda49bf\",\"name\":\"Josef Doods\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f4bf9632ed23044e095f92896096c41c1be1b04bde804e9d98bf99f4f7f097ab?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f4bf9632ed23044e095f92896096c41c1be1b04bde804e9d98bf99f4f7f097ab?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f4bf9632ed23044e095f92896096c41c1be1b04bde804e9d98bf99f4f7f097ab?s=96&d=mm&r=g\",\"caption\":\"Josef Doods\"},\"url\":\"https:\\\/\\\/www.archiware.com\\\/blog\\\/de\\\/author\\\/josef\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud - Archiware Blog","description":"Build your own offsite archive on LTO tape as an alternative to the cloud: P5 Archive and P5 S3 Object Archive decouple a slow WAN link from the tape drive.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.archiware.com\/blog\/de\/remote-archive-to-lto-tape\/","og_locale":"de_DE","og_type":"article","og_title":"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud - Archiware Blog","og_description":"Build your own offsite archive on LTO tape as an alternative to the cloud: P5 Archive and P5 S3 Object Archive decouple a slow WAN link from the tape drive.","og_url":"https:\/\/www.archiware.com\/blog\/de\/remote-archive-to-lto-tape\/","og_site_name":"Archiware Blog","article_published_time":"2026-10-26T11:00:16+00:00","article_modified_time":"2026-10-26T12:59:54+00:00","author":"Josef Doods","twitter_misc":{"Verfasst von":"Josef Doods","Gesch\u00e4tzte Lesezeit":"9\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/#article","isPartOf":{"@id":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/"},"author":{"name":"Josef Doods","@id":"https:\/\/www.archiware.com\/blog\/#\/schema\/person\/1bcb1ac5602a5577eecb07963dda49bf"},"headline":"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud","datePublished":"2026-10-26T11:00:16+00:00","dateModified":"2026-10-26T12:59:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/"},"wordCount":1758,"keywords":["archive to LTO tape","LTO archive","LTO tape","LTO-9","offsite archive","P5 Archive","S3"],"articleSection":["Archive","P5","Storage"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/","url":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/","name":"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud - Archiware Blog","isPartOf":{"@id":"https:\/\/www.archiware.com\/blog\/#website"},"datePublished":"2026-10-26T11:00:16+00:00","dateModified":"2026-10-26T12:59:54+00:00","author":{"@id":"https:\/\/www.archiware.com\/blog\/#\/schema\/person\/1bcb1ac5602a5577eecb07963dda49bf"},"description":"Build your own offsite archive on LTO tape as an alternative to the cloud: P5 Archive and P5 S3 Object Archive decouple a slow WAN link from the tape drive.","breadcrumb":{"@id":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.archiware.com\/blog\/remote-archive-to-lto-tape\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.archiware.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Remote Archive to LTO Tape: An Offsite Alternative to the Cloud"}]},{"@type":"WebSite","@id":"https:\/\/www.archiware.com\/blog\/#website","url":"https:\/\/www.archiware.com\/blog\/","name":"Archiware Blog","description":"Archiware P5 and Archiware Pure tech info","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.archiware.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Person","@id":"https:\/\/www.archiware.com\/blog\/#\/schema\/person\/1bcb1ac5602a5577eecb07963dda49bf","name":"Josef Doods","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/f4bf9632ed23044e095f92896096c41c1be1b04bde804e9d98bf99f4f7f097ab?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f4bf9632ed23044e095f92896096c41c1be1b04bde804e9d98bf99f4f7f097ab?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f4bf9632ed23044e095f92896096c41c1be1b04bde804e9d98bf99f4f7f097ab?s=96&d=mm&r=g","caption":"Josef Doods"},"url":"https:\/\/www.archiware.com\/blog\/de\/author\/josef\/"}]}},"_links":{"self":[{"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/posts\/5732","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/comments?post=5732"}],"version-history":[{"count":9,"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/posts\/5732\/revisions"}],"predecessor-version":[{"id":5742,"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/posts\/5732\/revisions\/5742"}],"wp:attachment":[{"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/media?parent=5732"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/categories?post=5732"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.archiware.com\/blog\/de\/wp-json\/wp\/v2\/tags?post=5732"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}