ignite taking long time

[Lisa Dingman]

Could you tell me what would be normal for the ignite process, on an rp5470 hpux 11.11, DAT tape drive, on a quiet system with make_tape_recovery _A(about 2.45 hours), with -x incentire vg00 and vg01 took almost 6 hours, not on quiet system. I was told you didn't have to do on quiet system, would someone please verfiy this, do we have a problem?

[Torsten.]

This always depends on the amount of data and the tape model.

Based on experience this could take from some (~5) minutes up to several hours ...

[Tim Nelson · Accepted solution]

The 2.5 hours for a standard vg00 ( just the OS ) to a DAT drive sounds about right to me.

What is the combined capacity on the second system of vg00 and vg01 ? How busy is this system ? What DAT flavor ?

6 hours for a really busy system to a DDS2 may not be out of the question.

IMHO there are two performance factors with Ignite.
1) The speed of the tape drive.
2) The speed/business of the system. Ignite uses tar/pax and compresses the archive. CPU is required for the compression so a really busy server is going to slow down the archive build.

I send all my images to an Ignite server. On average my images complete in 30-45 minutes depending on their config.

[Fabio Ettore]

Hi,

the time spent in Ignite-UX backup depends on the amount of data.
I suggest taking a make_tape_recovery -x inc_entire=vg00 (only vg00) and taking backup of vg01 by other tools.

Anyway if you want to check for problems during backup phase see log file

/var/opt/ignite/recovery/latest/recovery.log

where ./latest/recovery.log is last backup session.

HTH.

Best regards,
Fabio

[Lisa Dingman]

Thank you all very much, is very helpful, esp,. the log file.

[Lisa Dingman]

Can you please tell me the significance of the following:(in the log file)
NOTE: File: /var/opt/ignite/recovery/2008-06-13,11:26/system_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.

[Lisa Dingman]

I should have put all of this in a single post. Actually there are multiple files notes, about them not being world readable. I guess a question I mainly have, is why would you make these files world readable, as root can't they all be accessed by root, why is the world readable important?

[James R. Ferguson]

Hi Lisa:

> File: /var/opt/ignite/recovery/2008-06-13,11:26/system_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.

You can simply ignore these (annoying) messages for the reason you stated. Your 'umask' must have been set to '027' or '077' when you made the Ignite recovery tape.

Regards!

...JRF...

[Steven E. Protter]

Shalom,

I've worked with Ignite and similar systems.

Depending on amount of data, the times are not unreasonable. Also tape drive write speed is important.

vg00 on most systems boot only should be able to be written to an Ultrium tape drive in 20 minutes.

But when you start backing up big file systems you run itno these issues.

System not being quiet is a factor.

I don't think you have a really serious problem.

SEP

[OldSchool]

bear in mind that a dds-2 will normally transfer less than 3GB/hr, so if you've got about 20Gig of storage in vg00 / vg01 it looks about normal.

As noted, ignite is typically used for vg00 only.