Solved

VDR: Trouble writing to destination, error -2241 ( Destination index invalid/damaged)

Posted on 2014-07-29
4
629 Views
Last Modified: 2014-08-31
Hi a run down on what we experience:

we run a manual integrity check , it shows Ready
It starts the backup then in the reports
:Trouble writing to destination, error -2241 ( Destination index invalid/damaged)"
there are no damaged restore points

Have restarted the device have check through and tried to find Locked files > non  found checked with below
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018060

please help
0
Comment
Question by:JakesC
  • 2
  • 2
4 Comments
 
LVL 120
ID: 40227836
I would immediately refer you to VMware Support, for them to investigate and look through your logs.

The repository, could be damaged beyond repair.

What is the current size, and how long have you been using the repository ?


In the past we have created a new repository, restored any backups we needed (e.g. archived), destoyed and created a new repository.

(and it's common when reaching it's limit, or older repos)
0
 

Author Comment

by:JakesC
ID: 40230159
Hi there fairly new to VDR but what I know is on the particular SCSCI it has a capacity of 1023GB and in the Gui it shows  125GB free , I believe the repository is about a year or so old

What are the steps in re creating the repository ?
Just a format of the whole SCSI mounted DISK ?  

Thanks for the answers thus far
0
 
LVL 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40230204
1 one year old VDR repo is old!

Add a new disk, format and mount.

and then start backing up to this new repo.
0
 

Author Comment

by:JakesC
ID: 40295988
We have re-assesed and we are in process of using Veaam and a new Storage system

thanks for all comments
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question