Yes, quite easily.
> >>>>>>>>>>> I do not know if your problem is the same (you need a human
not
> >>>>>> paying
> >>>>>>>>>> much
> >>>>>>>>>>>
;>>>>>> On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
> >>>>>>>>>> rafaelweingart...@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Yes, quite easily.
> >>>>&
ch
>>>>>>>>>>> attention to cause this type of problem), but basically, you can
>>>>>> check
>>>>>>>>> in
>>>>>>>>>>> the database what is the data store with id = 3, and then the
>>>
> >>>>>>> of
> >>>>>>>>> snapshots that are allocated in this data store, and then you can
> >>>>>>> remove
> >>>>>>>>> them manually setting the flags.
> >>>>>>>>>
> >>>&
ata store, and then you can
>>>>>>> remove
>>>>>>>>> them manually setting the flags.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Aug 24, 2017 at 2:09 PM, Asai
>>>
gt;>>>>>
> >>>>>>>> Do you recall if it was able to be fixed?
> >>>>>>>> Asai
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Aug 24, 2017, at 11:03 AM, Rafael
t; Do you recall if it was able to be fixed?
>>>>>>>> Asai
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
>>>>>>>> rafaelweingart...@gmail.com
;>
> >>>>>>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
> >>>>>> rafaelweingart...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> I have seen this issue before. In the environment I noticed it, it
> >>> wa
his issue before. In the environment I noticed it, it
>>> was
>>>>>>> caused by someone that manually deleted a volume in the database in
>>>> order
>>>>>>> to remove a data store, but the snapshot that was using that volume
>>> wa
t;>>>> to remove a data store, but the snapshot that was using that volume
>> was
>>>>> not
>>>>>> removed. Then, the data store was removed. By delete here I mean
>>> setting
>>>>>> the flag "removed" in the da
moved. Then, the data store was removed. By delete here I mean
> > setting
> > >>> the flag "removed" in the database to some data and the "state" to
> > >>> destroyed.
> > >>>
> > >>> On Thu, Aug 24, 2017 at 1:45 PM, As
By delete here I mean
> setting
> >>> the flag "removed" in the database to some data and the "state" to
> >>> destroyed.
> >>>
> >>> On Thu, Aug 24, 2017 at 1:45 PM, Asai
> >> wrote:
> >>>
> >>>&
in the database to some data and the "state" to
>>> destroyed.
>>>
>>> On Thu, Aug 24, 2017 at 1:45 PM, Asai
>> wrote:
>>>
>>>> Greetings,
>>>>
>>>> I was browsing to the Snapshots section under “Storage” toda
By delete here I mean setting
> > the flag "removed" in the database to some data and the "state" to
> > destroyed.
> >
> > On Thu, Aug 24, 2017 at 1:45 PM, Asai
> wrote:
> >
> >> Greetings,
> >>
> >> I was browsing to t
wrote:
>
>> Greetings,
>>
>> I was browsing to the Snapshots section under “Storage” today and came up
>> with this error:
>>
>> Unable to locate datastore with id 3
>>
>> I am unable to figure this out. I went to the Secondary Storage server
>
flag "removed" in the database to some data and the "state" to
destroyed.
On Thu, Aug 24, 2017 at 1:45 PM, Asai wrote:
> Greetings,
>
> I was browsing to the Snapshots section under “Storage” today and came up
> with this error:
>
> Unable to locate datasto
Greetings,
I was browsing to the Snapshots section under “Storage” today and came up with
this error:
Unable to locate datastore with id 3
I am unable to figure this out. I went to the Secondary Storage server and it
looks like all the snapshots are there from 2 days ago. Can someone please
ore with id 1
cserrorcode = 4250
errorcode = 530
errortext = Unable to locate datastore with id 1
uuidList:
Could someone please shed some light where and how this could be
solved? We don't necesserily need every previously done snapshot, but I
don't think purging the respective tables
18 matches
Mail list logo
