I was under the impression that the maximum size of a file
that can be backed up would be either 2^63 or 2^64 bytes, but
I can't seem to find anything in the manuals or via google-fu
that confirms this.
Does anyone have any positive information regarding the
maximum file size limit?
Devin
-
Dimitri Maziuk wrote (2015/05/20):
> Quoting quantum lto-6 sales blurb
> (http://www.quantum.com/products/tapedrives/ltoultrium/lto-6/index.aspx)
>
> Fast backup and restore performance ?at speeds up to 400MB/s (1.4TB/hr)*
>
> * Assumes 2.5:1 compression for LTO-6, 2:1 for other LTO
>
> Assu
Bryn Hughes wrote (2015/05/19):
> Yes, there is definitely a minimum throughput for LTO drives. If you
> aren't writing from local storage then you almost certainly won't be
> able to meet it for anything at all modern. LTO-3 was the last
> generation that could be fed by a gigabit ethernet li
Florian Rist wrote (2015/05/18):
> The question is probably, what happens if a tape change is forgotten.
> Say I have scheduled backup job for the night and the tape is not change
> in the evening. Will this mess up everything or will the job
> automatically be run as soon as the needed tape bec
Florian Rist wrote (2015/05/18):
> Thanks for the numbers and pointing me to the spool/unspool problem.
> This can be fixed by using two hard drives, right?
In RAID-0? Let's hope so :o) However, I would rather use "better" instead
of "fixed". Another solution would be to allow just one parallel j
Quoting quantum lto-6 sales blurb
(http://www.quantum.com/products/tapedrives/ltoultrium/lto-6/index.aspx)
Fast backup and restore performance –at speeds up to 400MB/s (1.4TB/hr)*
* Assumes 2.5:1 compression for LTO-6, 2:1 for other LTO
Assuming no compression = 400/2.5 = 160.
> Seagate NAS
On 2015-05-20 12:16 PM, Dimitri Maziuk wrote:
> On 05/20/2015 01:09 PM, Bryn Hughes wrote:
>
>> What do you call it when multiple backup jobs are writing to disk
>> storage while at the same time a copy job is reading from that same disk
>> subsystem and writing to tape?
> I call the comparison FUD
On 05/20/2015 01:09 PM, Bryn Hughes wrote:
> What do you call it when multiple backup jobs are writing to disk
> storage while at the same time a copy job is reading from that same disk
> subsystem and writing to tape?
I call the comparison FUD because compare that to multiple backup jobs
writi
On 2015-05-20 10:10 AM, Dimitri Maziuk wrote:
> Then why TF are you quoting lto sustained write to hdd random i/o? "Disk
> subsystem can't keep up with modern tape" in the same way apples can't
> keep up with oranges. Compare optimized sustained writes to optimized
> sustained writes or random seek
On 05/20/2015 10:48 AM, Bryn Hughes wrote:
> On 2015-05-19 10:43 AM, Dimitri Maziuk wrote:
>> On 05/19/2015 11:42 AM, Bryn Hughes wrote:
>>> drive - most consumer hard drives top out at about 120MB/sec for
>>> sequential reads and much less than that for random I/O
>> Wow these seagate nas drives
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 20 May 2015 10:59:37 +0200
Denis Witt wrote:
> > When you say "On Saturday there are some of the missing jobs stored
> > in the catalog (with status T). On Sunday some of them are gone.
> > ", are you talking about incremental jobs?
>
On 2015-05-19 10:43 AM, Dimitri Maziuk wrote:
> On 05/19/2015 11:42 AM, Bryn Hughes wrote:
> ...
>> recent LTO versions (5/6) you really need to make sure your disk setup
>> on your backup storage server is capable of keeping up with the tape
>> drive - most consumer hard drives top out at about 12
> On Wed, 13 May 2015 08:40:18 +0200, Radosław Korzeniewski said:
>
> Hello,
>
> 2015-03-23 13:58 GMT+01:00 Pavel Bychikhin :
>
> > Hello Everyone,
> > I apologize for repeating my question but I've searched a lot and didn't
> > find any clarification and, unfortunately, didn't get any answe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 19 May 2015 18:21:19 -0400
Dan Langille wrote:
> With bconsole, because everyone has that, can you tell us exactly
> what you did to confirm the job was gone?
Hi Dan,
I received a job E-Mail stating that the Full-Backup-Job was run with
j
You said it yourself: RAID. Not magic, it is only writing on multiple disks in
parallel.
The disks I have in my NAS are WD Reds, rated at 112 MB/s and performance
tested (by Tom's Hardware) to write at speeds from about 70 MB/s (center of the
disk) to about 150 MB/s (outside).
I've seen much h
15 matches
Mail list logo
