VMware Cloud Community
olof_christenss
Contributor
Contributor
Jump to solution

VDR 1.0.2 - error message during recatalog error -2241 destination index invalid/damaged

Hi, We are getting this error message during recatalog. -2241 destination index invalid/damaged

Is it possible to recover from and if so - what should i do?

Reply
0 Kudos
1 Solution

Accepted Solutions
abbasi
Enthusiast
Enthusiast
Jump to solution

Hello,

the solution for me was to go into the VDR server, login as root and remove the lock file. Then I was able to start the integrity check

Repeat this for all datastores

-# cd /SCSI-0\:1/

# ls

lost+found

VMwareDataRecovery

# cd

VMwareDataRecovery/

# ls

BackupStore BackupStore.cat BackupStore.cat.bak

# cd

BackupStore

# ls

000 bmap-index-03.dat index-00.dat index-05.dat store.lck

999

bmap-index-04.dat index-01.dat index-06.dat

bmap-index-00.dat

bmap-index-05.dat index-02.dat index-07.dat

bmap-index-01.dat

bmap-index-06.dat index-03.dat journal.dat

bmap-index-02.dat

bmap-index-07.dat index-04.dat map.dat

[root@VS71

BackupStore]#

# rm -rf store.lck/

Message was edited by: abbasi

View solution in original post

Reply
0 Kudos
12 Replies
kdc
Contributor
Contributor
Jump to solution

Hey,

Have you tried running a integrity check on the destination?

Reply
0 Kudos
olof_christenss
Contributor
Contributor
Jump to solution

Yes integrity check has been done.

Reply
0 Kudos
olof_christenss
Contributor
Contributor
Jump to solution

Hi again - i am sorry but i responded incorrect - integrity check is not done properly - we get this error message when i trigger a integrity check!

Destination "/192.168.0.2/vDR_1/" will be locked until the restore point with errors are deleted and integrity check succeeds.Execution Event

Trouble reading from destination volume, error -2241 ( Destination index invalid/damaged)Execution Event0

Reply
0 Kudos
abbasi
Enthusiast
Enthusiast
Jump to solution

Were you able to recover? I am also getting this error

Reply
0 Kudos
olof_christenss
Contributor
Contributor
Jump to solution

m,

Reply
0 Kudos
abbasi
Enthusiast
Enthusiast
Jump to solution

Hi,

Could you translate that please

Reply
0 Kudos
abbasi
Enthusiast
Enthusiast
Jump to solution

Hello,

the solution for me was to go into the VDR server, login as root and remove the lock file. Then I was able to start the integrity check

Repeat this for all datastores

-# cd /SCSI-0\:1/

# ls

lost+found

VMwareDataRecovery

# cd

VMwareDataRecovery/

# ls

BackupStore BackupStore.cat BackupStore.cat.bak

# cd

BackupStore

# ls

000 bmap-index-03.dat index-00.dat index-05.dat store.lck

999

bmap-index-04.dat index-01.dat index-06.dat

bmap-index-00.dat

bmap-index-05.dat index-02.dat index-07.dat

bmap-index-01.dat

bmap-index-06.dat index-03.dat journal.dat

bmap-index-02.dat

bmap-index-07.dat index-04.dat map.dat

[root@VS71

BackupStore]#

# rm -rf store.lck/

Message was edited by: abbasi

Reply
0 Kudos
olof_christenss
Contributor
Contributor
Jump to solution

Hi,

I was also able to get the store working again by removing the lock file.

I apologize for not responding before now but i have been on a vacation and not been able to read my emails.

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot
Jump to solution

I've been getting this, since Sat/Sun, logged with VMware Support and they told me VDR was shit, and stop using it, and try Veeam or Vizioncore, I'm keep to try this tomorrow am!

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot
Jump to solution

this fixed it for me, manyn thanks, it's a shame that the Support Engineer didn't know how to fix this! When we are paying for Gold Support!

just have to work out why one vm now stops backup at 73%

e

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

VDR 1.1 is available for download and highly recommend downloading this release - more information here

http://communities.vmware.com/thread/243436?tstart=0

Also, some additional suggestions post VDR 1.1 upgrade

Check the backup appliance for the store.lck folder, which is found in

/VMwareDataRecovery/BackupStore/store.lck.

If this folder exists and you are certain there are no other instances of Data Recovery using this deduplication store, delete the store.lck folder and its contents.

Once upgraded to VDR 1.1, delete the /VMwareDataRecovery/BackupStore.cat.bak files and start a manual integrity check. This will cause the VDR engine to rebuild the catalog.

Reply
0 Kudos
cintiadg
Contributor
Contributor
Jump to solution

Hi,I am having some issues with my VDR (version 1.1)

In the beggining I tried to run the Integrity Check and got this error:

  • Integrity check failed for the restore point created on (date) (time) for (VM name)

  • Backup Set (destination name) will be locked until the restore point with errors are deleted and integrity check succeeds.

I had marked for delete the damaged restore point and tried to run the

integrity check again, but I had the same issue (and the damaged

restore point was still there)

So, I oppened the VDR console, stopped the DataRecovery service,

deleted the configuration file, started the service, mounted the

datastore, recreated the backup job and tried to run the integrity

check again. It failed again.

The message below also appears in the VDR log:

  • Trouble reading from destination volume, error -2241 ( Destination index invalid/damaged)

  • Backup Set (destination name) will be locked until the restore point with errors are deleted and integrity check succeeds.

After some researches, I read in the KB that I had to power off VDR in order to delete the BackupStore.cat and BackupStore.cat.bak

files and start an integrity check again, so the engine would rebuild

the catalog and I would be able to run the Integrity Check.

I did it, as they were saying, but the problem persisted.

Looking in the KB again, I´ve found that I had to remove the lock

file(_store.lck_), but there isn´t any lock file inside the BackupStore

directory.

*Conclusion: I can´t backup the VMs because I can´t run neither the

Integrity Check (even when I mark the damaged restore point for delete)

not the Recatalog.*

Reply
0 Kudos