cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hi Team ,

While try to restore the a backup to HANA DB  to a Tenat DB  I am gettting  below error

just after I start recovery.

"

RECOVER DATA finished with error:

recovery could not be completed, volume 0, reached log position 0,

Invalid value <2> for BackupSrc_Topology::Version

"

I suspect  it could related to file structure as when I was install the  HANA DB , I had to change the path for

the hana directory  of  /hana/shared  to /hana/shared1 due to space issue.

But now i can't  make changes here.

Could you please help here.

Regards,

Abhinav

0 Likes
View Entire Topic
Former Member
0 Likes

Dear All ,

Above error is gone & now .getting below .

RECOVER DATA finished with error:

recovery could not be completed, volume 0, reached log position 0,

Cannot open file ""<root>/SRD2016-03-28223005_databackup_0_1" ((mode= R, access= rw-r-----, flags= DIRECT|MUST_EXIST|MULTI_WRITERS|UNALIGNED_SIZE), factory= (root= "/dev/shm/" (access= rw-r-----, flags= <none>, usage= DATA_BACKUP, fs= UNSUPPORTED (tm, config= (async_write_submit_active=auto,async_write_submit_blocks=new,async_read_submit=off,num_submit_queues=1,num_completion_queues=1,size_kernel_io_queue=512,max_parallel_io_requests=64))", rc=22: Invalid argument

Former Member
0 Likes

I have already set permission to all files to 777.

yet getting this error

AtulKumarJain
Active Contributor
0 Likes

Hi Abhinav,

It seems while giving the input to hana stdio in recovery ,path of backup .

Please share that screenshot .Do not select the datafile name only

"SRD2016-03-28223005"

BR

Atul

Former Member
0 Likes

Now I am into another error saying

FAIL: process hdbindexserver indexserver-SRD not running

Regards ,

Abhinav

AtulKumarJain
Active Contributor
0 Likes

Hi Abhinav,

Recovery completed?And your HANA sysetm is not starting?

For starting recovery your system should be down.

BR

Atul

Former Member
0 Likes

No this is after recovery failure.

Regards ,

Abhinav

AtulKumarJain
Active Contributor
0 Likes

Please check indexserver trace and name serevr trace.

BR

Atul

Former Member
0 Likes

Hi  Atul ,

I later realized that its issue with the DB version , so i updated the DB to SP10 , but post that

I have getting below error.

RECOVER DATA finished with error:

recovery could not be completed, volume 0, reached log position 0,

Cannot open file ""<root>/GWD2016-04-01213209_databackup_0_1" ((closed, mode= R, access= rw-r-----, flags= DIRECT|MUST_EXIST|MULTI_WRITERS|UNALIGNED_SIZE), factory= (root= "/dev/shm/" (access= rw-r-----, flags= AUTOCREATE_PATH|DISKFULL_ERROR, usage= DATA_BACKUP, fs= UNSUPPORTED (tmpfs), config= (async_write_submit_active=auto,async_write_submit_blocks=new,async_read_submit=off,num_submit_queues=1,num_completion_queues=1,size_kernel_io_queue=512,max_parallel_io_requests=64,min_submit_batch_size=16,max_submit_batch_size=64))", rc=22: Invalid argument

I am looking forward to clear some space from my system , but snot sure which directory to be cleaned

Former Member
0 Likes

This is resolved as this turned out to be a issue with the removing un-necessary - files from the backup directory.

Regards,

Abhinav