v7 Error : Full storage not found

[alexkay]

Hello !

I've just made a clean install of my veeambackup server with v7 using exactly the same configuration i had for v6.5.

When i start a backup job, it doesn't process any vm and fails with this error : Full storage not found.

Any idea ?

Thx

[veremin]

We haven’t seen this error so far, so, kindly, open a ticket with support team and let them investigate this issue. Thanks.

[alexkay]

I solved my problem : when creating my new backup jobs in v7, i had mapped the v6.5 backup data in backup repositories.

I've just recreated backup jobs without mapping anything and now it's running fine.

[veremin]

Glad to hear you manged to solve the issue. And thanks for sharing the solution; highly appreciated.

[Bunce]

We haven’t seen this error so far, so, kindly, open a ticket with support team and let them investigate this issue. Thanks.

I logged it a week ago. #431287

[veremin]

Hi, Andrew. We aren’t monitoring the support portal throughout the day – just when there is a need to follow a certain case or someone updates the topic with his/her support ticket number. So, thanks you for letting us know.

May I also assume that the disabling mapping functionality didn’t solve the issue for you? Thanks.

[Bunce]

Yup. Effectively we found no way to reuse the exiting backup chain, either through mapping/unmapping, running a new full, creating new jobs and remapping, removing and re-importing the backup, etc.

However the chain itself didn't appear corrupt as test restores worked fine.

We had to create a new job and start a new chain.

[foggy]

After rescanning the target repository locating previous backups you should be able to map the new jobs to them. Anyway, I'm glad you've worked around this without issues.

[veremin]

For all new-comers: the support team is already aware about this issue and has developed a workaround for it. So, if you you’re experiencing the same issue, kindly, contact our support team and they will share the information regarding steps that need to be taken. Thanks.

[SuperMRSommer]

Hello Everybody

Since the new version of Veeam 7 i had by one server the following problem:

Error: Full storage not found

Can anyone help me?

Cheers

SuperMRSommer

[veremin]

Hi, SuperMRSommer. As mentioned above, our support has already created a workaround for this issue, so, kindly contact them in order to get it. Thanks.

[KeithW]

If there is a simple solution to this, can y'all just post it here? Why make all the people that hit the error go clogging up the support lines? FYI, I got the error on the first job after an in place upgrade from 6.5patch3.

[veremin]

The reason behind this decision is that it is only support team that can surely understand whether or not you experience the similar issue after taking a look at required logs.

Also, certain issues, though having applicable workarounds or fixes, might be still under investigation. In this case, by opening a ticket you help us to collect as much data as possible, which eventually allows us to determine what things, in particular, leads to the said behavior.

Thank you for your understanding.

[foggy]

That said, the fix for this particular issue is scheduled to be included in one of the future updates.

[deduplicat3d]

Is the fix for this in the R2 release?

[deduplicat3d]

Ugh I misread the weekly digest, I thought R2 was already release. Time to call support I guess.

[veremin]

Yep, you're right. The best option to get the said workaround will be to open a ticket with our support team. Thanks.

[foggy]

And no, this particular fix is not included in the v7 R2 release.

[tomreeb]

I am running a Trial version of 7.0.0.690 and just experienced this issue with one of my existing backup jobs. Was it not fixed by now?

[veremin]

Hi, Tom,

There is a hot fix for this issue that can be gotten via opening a ticket with our support team. According to our policy, customers with an evaluation licence are eligible for support. So, it might be worth getting in touch with our support team.

Thanks.

[BeefSupreme]

I just got off with support on this...it's probably not something you can alone fix as there is do documentation or KB on this. Support has to use SQL management Studio to do the fix on the database. So why are you not calling in on support?

[mcvosi]

I would say not. I just did a re-install of my vCenter server and a couple jobs are throwing this error.

[veremin]

Hi, Matthew, if you're still experiencing the said issue, you should contact our support team in order to get assistance in database fixing. Thanks.

[pizzim13]

Run at your own risk!
I created this script to fix these issues when they come up.

Code: Select all

foreach ($JobName in (Get-VBRJob).name)
    {
    $VeeamSQLInfo = Get-ItemProperty 'HKLM:\SOFTWARE\VeeaM\Veeam Backup and Replication'
    $SQLServer = $VeeamSQLInfo.SqlServerName
    $SQLTable = $VeeamSQLInfo.SqlDatabaseName
    $SqlQuery = "SELECT id, file_path, creation_time from [$SQLTable].[dbo].[Backup.Model.Storages] where backup_id in(
    SELECT id FROM [$SQLTable].[dbo].[Backup.Model.Backups] where job_id in (
    SELECT id from [$SQLTable].[dbo].[BJobs] where name  = '$JobName'))
    ORDER BY creation_time"
 
    $SqlConnection = New-Object System.Data.SqlClient.SqlConnection

    $SqlConnection.ConnectionString = "Server = $SQLServer; Integrated Security = True"
 
    $SqlCmd = New-Object System.Data.SqlClient.SqlCommand
    $SqlCmd.CommandText = $SqlQuery
    $SqlCmd.Connection = $SqlConnection
 
    $SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
    $SqlAdapter.SelectCommand = $SqlCmd
 
    $DataSet = New-Object System.Data.DataSet
    $SqlAdapter.Fill($DataSet) | Out-Null
  
 
    $Output = $DataSet.Tables[0]

    $VBKFiles = $Output | Where-Object {$_.file_path -like "*.vbk"}
    $VRBFiles = $Output | Where-Object {$_.file_path -like "*.vrb"}
    
    
    foreach ($VBKFile in $VBKFiles)
        {
         
        $SameDateVRB = $VRBFiles | Where-Object {($_.creation_time).date -eq ($VBKFile.creation_time).Date}

        if ($SameDateVRB.creation_time -gt $VBKFile.creation_time)
            {
            Write-Host $JobName -ForegroundColor Red
            $VBKFile
            $SameDateVRB
            $NewTime = ($VBKFile.creation_time | get-date).AddMinutes(-1) | Get-Date -Format yyyy-MM-dd$([char]32)HH:mm:ss
            $GUID = $SameDateVRB.id.Guid
            $SqlQuery = "UPDATE [$SQLTable].[dbo].[Backup.Model.Storages] set creation_time = '$NewTime' where id = '$GUID'"
            $SqlCmd.CommandText = $SqlQuery
            $SqlCmd.Connection = $SqlConnection
            $SqlConnection.Open()
            $SqlCmd.ExecuteNonQuery()
            }
        }
    
    $SqlConnection.Close() 
    }

[veremin]

For all new comers, before you proceed with the script that includes internal database changes, we highly recommend that you contact support team first to understand whether or not your issue is similar to the one discussed here. Thanks.

[shkap]

Has a patch been released that addresses this? I received this error as well. I found the only solution was to create a new backup. Support hasn't provided me with a solution. I've read the recently released patch (3) and I didn't notice any resolution of this.

Seth

[foggy]

Seth, the fix for that issue was not included in patch 3, but is scheduled for the next product version. However, support is able to perform the required database modification to fix it, so I encourage you to escalate your case to get assistance with it.

[Oka Soh]

This fix includes v8 not v7 patch 4, is it right ?

[foggy]

Yes, this was the plan. However, no need to wait, you can contact support right now for the resolution.

[Oka Soh]

Thank you for notice !
Just I have been curious, currently none of our customers has this error.
I'll wait until v8 release, because it seems easier.