#318 Issue `closed`: Point in Time recover is not working¶

Labels: bug, support / question

nmidc opened issue at 2013-10-23 08:24:¶

Dear all,
i try to Point in Time recover. but it is running into
"ERROR: Could not source '/mnt/local/etc/sysconfig/kernel'.

example: we pach a server from sless sp1 to sp2 and a few days later we have to go back.

gdha commented at 2013-10-23 11:38:¶

Did you do a rear mkbackup before the upgrade? Show me the local.conf file to be sure.
Can you paste the rear.log file when the error occurred (not the complete file, but with relevant info before the error popped up)

nmidc commented at 2013-10-23 11:50:¶

Hi,we did a rear -v mkrescue. rear mkbackup we didn´t but dsmc inc.
This is the rear local.conf

# sample local configuration
# Create Relax-and-Recover rescue media as ISO image
# OUTPUT=ISO
# sample local configuration
# Create Relax-and-Recover rescue media as ISO image
OUTPUT=ISO
OUTPUT_URL=file:///tmp
BACKUP=TSM
COPY_AS_IS_TSM=( /etc/adsm/TSM.PWD /opt/tivoli/tsm/client /usr/local/ibm/gsk8* /SZIR/data/inclexcl2)
COPY_AS_IS_EXCLUDE_TSM=( )
PROGS_TSM=(dsmc)
RESULT_FILES="/var/lib/rear/output/rear-system.iso"
PROGS=( "${PROGS[@]}"
vconfig
vi
vim )
ONLY_INCLUDE_VG=( "vg00" )

gdha commented at 2013-10-25 10:50:¶

It is better to use the syntax in /etc/rear/local.conf file:

COPY_AS_IS_TSM=( "${COPY_AS_IS_TSM[@]}" /SZIR/data/inclexcl2 )

Hopefully, the file system /SZIR is part of VG vg00 (as you only include vg00)?

The error that you got during the recovery Could not source '/mnt/local/etc/sysconfig/kernel' exercise. Where exactly did it happen? Before, during or after the TSM restore?

nmidc commented at 2013-10-25 11:33:¶

Hi,
now i changed the local.conf and SZIR is vg00 of course
But it is not working
I attached the Log File

Dirk Lohmann

Von: gdha [mailto:notifications@github.com]
Gesendet: Freitag, 25. Oktober 2013 12:51
An: rear/rear
Cc: Lohmann, Dirk, NMS-OSV
Betreff: Re: [rear] Point in Time recover is not working (#318)

It is better to use the syntax in /etc/rear/local.conf file:

COPY_AS_IS_TSM=( "${COPY_AS_IS_TSM[@]}" /SZIR/data/inclexcl2 )

Hopefully, the file system /SZIR is part of VG vg00 (as the only include vg00)?

The error that you got during the recovery Could not source '/mnt/local/etc/sysconfig/kernel' exercise. Where exactly did it happen? Before, during or after the TSM restore?

—
Reply to this email directly or view it on GitHubhttps://github.com/rear/rear/issues/318#issuecomment-27081320.

gdha commented at 2013-10-25 13:07:¶

@nmidc could you attach the logfile as a gist?

nmidc commented at 2013-10-28 06:08:¶

Hi
Upload at Gist is done now

Dirk Lohmann
Von: gdha [mailto:notifications@github.com]
Gesendet: Freitag, 25. Oktober 2013 15:08
An: rear/rear
Cc: Lohmann, Dirk, NMS-OSV
Betreff: Re: [rear] Point in Time recover is not working (#318)

@nmidchttps://github.com/nmidc could you attach the logfile as a gist?

—
Reply to this email directly or view it on GitHubhttps://github.com/rear/rear/issues/318#issuecomment-27090099.

gdha commented at 2013-10-28 07:02:¶

Could you paste the gist URL into the issue please?

On Mon, Oct 28, 2013 at 7:08 AM, nmidc notifications@github.com wrote:

Hi
Upload at Gist is done now

Dirk Lohmann

nmidc commented at 2013-10-28 07:04:¶

https://gist.github.com/nmidc/7192064

gdha commented at 2013-10-28 07:48:¶

I believe the problem is with the following:

ANS1036S The option '-PITD' or the value supplied for it is not valid. It was found in options file 'Command Line'
         at line number: 0
         The complete entry: '-pitd=10/20/2013'

TSM did not restore anything as it did not like the option -pitd I'm not a TSM expert, but if I were you I would dig into the TSM manuals and investigate what option is the correct one for your version of TSM? It might have changed in the meantime...

gdha commented at 2013-11-04 15:42:¶

@nmidc did you make any progress with a TSM expert?

nmidc commented at 2013-11-05 06:10:¶

hi,
yes i try someting. It should be the wrong syntax for timestap..dsmc need this one 2013.11.05 rear need this one 2013-11-05. We make a few test.

nmidc commented at 2013-11-05 10:50:¶

Hi
if i am right we have to modify this line in 39_request_point_in_time_restore_parameters.sh

old: TSM_RESTORE_PIT_DATE=$( date -d "$REPLY" +%m/%d/%Y 2>&8 ) ||
new: TSM_RESTORE_PIT_DATE=$( date -d "$REPLY" +%Y.%m.%d 2>&8 ) ||\

gdha commented at 2013-11-05 12:15:¶

Alright, nice, with which version of TSM are you working? Could it be that this value changed between TSM versions? Or, perhaps, it was wrong all the time? I don't know as I didn't integrate TSM into rear.

nmidc commented at 2013-11-05 12:18:¶

In this case we are using Server Version 6 Release 2 Level 3.0

alxgu commented at 2013-12-18 09:18:¶

Hi Gratien D'haese,

could you please correct the commit 884f1b8. There is an issue with the sequence of the date in the variable TSM_RESTORE_PIT_DATE.

Please change it from:
TSM_RESTORE_PIT_DATE=$( date -d "$REPLY" +%m.%d.%Y 2>&8 )
to
TSM_RESTORE_PIT_DATE=$( date -d "$REPLY" +%Y.%m.%d 2>&8 )

Thanks.

[Export of Github issue for rear/rear.]

#318 Issue closed: Point in Time recover is not working¶