1833780 Members
2259 Online
110063 Solutions
New Discussion

frecover -V output

 
SOLVED
Go to solution
Jeff Picton
Regular Advisor

frecover -V output

Hello

Can anyone tell me why when I do the following :-

/etc/frecover -V /tmp/index -f /dev/rmt/0m

I get different output for two successive frecovers and the second output is always
correct ?

Is there a command I must do before running this ?

Thank you
12 REPLIES 12
Vitek Pepas
Valued Contributor

Re: frecover -V output

What command do you use to create the backup ?
Darren Prior
Honored Contributor
Solution

Re: frecover -V output

Hi Jeff,

Can you post the 2 different files so that we can see the differences. The only time I've seen anything like this was when someone piped the output from dd into frecover.

regards,

Darren.
Calm down. It's only ones and zeros...
Jeff Picton
Regular Advisor

Re: frecover -V output

Hi

I use SAM to do automated backups :-

/usr/sam/lbin/br_backup DAT PART Y /dev/rmt/0m /var/sam/graphTCAa27753 root Y 1 N > /var/sam/SAM_br_msgs 2>&1

Jeff
Jeff Picton
Regular Advisor

Re: frecover -V output

The attached file gives the results os running the script twice.
Darren Prior
Honored Contributor

Re: frecover -V output

Hi Jeff,

It's certainly interesting. You 'll need to find out what script has to be run to produce that output as it isn't something frecover would do. The fact that it's got the "it may need to be run twice" bit suggests that it's a script someone else has written.

Feel free to post the script so people can work out what's happening. It'd also be really useful to post the file /tmp/index that's created - both the 1st and 2nd times the script is run so we can compare.

regards,

Darren.

Calm down. It's only ones and zeros...
Patrick Wallek
Honored Contributor

Re: frecover -V output

My guess would be that someone has changed /etc/frecover from merely being a link to /usr/sbin/frecover, to being some sort of custom written script.

Do an 'll /etc/frecover' and see what it shows. My systems show:

lrwxr-xr-t 1 root sys 18 Jun 9 2002 /etc/frecover@ -> /usr/sbin/frecover

You might also try invoking:

# /usr/bin/frecover -V /tmp/index -f /dev/rmt/0m

And see what happens.
Jeff Picton
Regular Advisor

Re: frecover -V output

Darren

I wrote the script. Here are my /tmp/index entries for two attempts :-

Today's date is: Fri Oct 3 13:14:07 GMT 2003
Finding out the backup date of the tape in the machine .....
The tape in the machine is incremental backup tape B last backed up on Tue Sep 16 21:00:02 2003
Leave the incremental tape in the machine and replace with full backup B next Wednesday

cat /tmp/index
Magic Field:FBACKUP_LABEL
Machine Identification:9000/800
System Identification:HP-UX
Release Identification:B.11.11
Node Identification:telesto
User Identification:root
Record Size:32768
Time:Thu Oct 2 21:00:03 2003
Media Use:82
Volume Number:1
Checkpoint Frequency:32
Fast Search Mark Frequency:200
Index Size:134836
Backup Identification Tag:15649 1065128403
Language:

Today's date is: Fri Oct 3 13:15:37 GMT 2003
Finding out the backup date of the tape in the machine .....
The tape in the machine is incremental backup tape C last backed up on Thu Oct 2 21:00:03 2003
Leave the incremental tape in the machine and replace with full backup C next Wednesday

cat /tmp/index
Magic Field:FBACKUP_LABEL
Machine Identification:9000/800
System Identification:HP-UX
Release Identification:B.11.11
Node Identification:telesto
User Identification:root
Record Size:32768
Time:Thu Oct 2 21:00:03 2003
Media Use:82
Volume Number:1
Checkpoint Frequency:32
Fast Search Mark Frequency:200
Index Size:134836
Backup Identification Tag:15649 1065128403
Language:

I don't think there is a difference in /tmp/index each time the script is run

Jeff
Darren Prior
Honored Contributor

Re: frecover -V output

Yup - those 2 files look the same to me too. Are you using /tmp/index for something else in your script? If so it might be better to do the frecover -V to a file called /tmp/volheader. Can you post your script; I think we may be getting close to solving this one!

regards,

Darren.
Calm down. It's only ones and zeros...
Jeff Picton
Regular Advisor

Re: frecover -V output

Hi

I've changed the tmp file name as you suggested and I'll try and recreate the problem tomorrow. If the problem recurs, I'll let you know.

Cheers

Jeff
Jeff Picton
Regular Advisor

Re: frecover -V output

Hi

I realised today that the variables in the script are a function of the file /tmp/index so I cannot rename the /tmp file. Please find the script attached

Jeff
Darren Prior
Honored Contributor

Re: frecover -V output

Hi Jeff,

What is in the file /tmp/index the first time you run your script? Your 3 statements that read from /tmp/index to calculate days and dates do so before you've actually run the frecover, so they are using the old contents of the file from the last time it was run. Hence if you run it 2 times in succession you'll get the result you are expecting.

regards,

Darren.
Calm down. It's only ones and zeros...
Jeff Picton
Regular Advisor

Re: frecover -V output

Hi Darren

I see what you mean so i have elevated the frecover command to the start of the do loop and it appears to work now.

Cheers

Jeff