Highlighted
2 Bronze

Error 10020

Jump to solution

Hi all,

I have an avamar server version 6.0.1.65, I'm using the parameter x18=256  to backup windows xp sp3 to avoid error 10020, in the laptops that I have installed the client version 5.0.106-28, I don´t have the error 10020, but other laptops which I have installed the client version 6.0.101.65, I have this error.

I have tried with --x18=256 and x18=256

Thanks in advance.

Reply
1 Solution

Accepted Solutions
1 Copper

Re: Error 10020

Jump to solution

Hi,

You can try to downgrade the Error <0000> to Warning.  The switch to do that will be:

--downgrade-error-codes="0000"

The catch, however, is that if there is an actual issue that the volume that we want to backed up is not there, it will not be reported as an error and it might be showing a false positive.  This might be affecting both the whole drive backup as well as individual files or folers.

For example in case the VSS snapshot fails during the backup, you might receive an error 'Specified source path "C:\I\need\to\backup\this\folder\at\all\times" does not exist; ignored' which causes exception.  If we surpress the error code, any files and folders who's path is not found due to VSS issue will not be backed up, but the backup will show successful.  The extreme situation would be that the backup succeeds with 0B backed up.

Hope it helps

View solution in original post

Reply
4 Replies
Highlighted
3 Argentium

Re: Error 10020

Jump to solution

Hello,

Can you please paste the exact error message from the backup log as 10020 is a generic error.

Thanks.

Reply
Highlighted

Re: Error 10020

Jump to solution

Why would you want to avoid error 10020 on other laptops as well, unless you know the error reported is not harmfull?

This could be an actual error reported which might go unnotticed if ignored, before reducing the severity from error to info make sure all the laptop reported with error or not errors which are harmfull.

Make sure you are following the steps for adding the --x18=256

To add the --x18=256 flag to the dataset, perform the following steps:

Log in to the Avamar Administrator GUI using an account with appropriate permissions.

Select Tools => Manage Datasets.

Select the affected dataset from the list and click Edit.

Select the Options tab and choose the Windows File System plugin from the Select Plug-In Type dropdown.

Click the More button.

Type --x18 into the Enter Attribute field.

Type 256 into the Enter Attribute Value field.

Click the + sign to add the attribute to the dataset.

Click OK to dismiss the Edit dialog.

Click OK to dismiss the dataset editor.

Reply
Highlighted
2 Bronze

Re: Error 10020

Jump to solution

Hi all,

I'm sorry for the delay in replying.

I have a dataset to backup windows´s laptops and I have defined two directories "C:/datos" and "D:/datos" in this dataset, the problem is that some laptops don't have "D:/datos" and avamar´s client shows this picture to the users 

capture1.gif

Avamar Enterprise Manager (Activtiy) show me error 10020 and I would like to avoid both errors

capture1.bmp

On the other hand,

If I don´t use parameter x18=256 the error in the log is:

avtar Error <0000>: Specified source path "D:\datos" does not exist; ignored

If I use parameter x18=256 the error in the log is:

avtar Error <0000>: Volume path "D:\" not found -- No files from this volume will be saved

in both cases the log show me:

avtar Info <5314>: Command completed (1 error, exit code 10020: Completed with errors, client log should be examined)

Version of Avamar server 6.0.1.65

Version of Avamar client 6.0.101-65

Thanks in advanced

Best regards

Reply
1 Copper

Re: Error 10020

Jump to solution

Hi,

You can try to downgrade the Error <0000> to Warning.  The switch to do that will be:

--downgrade-error-codes="0000"

The catch, however, is that if there is an actual issue that the volume that we want to backed up is not there, it will not be reported as an error and it might be showing a false positive.  This might be affecting both the whole drive backup as well as individual files or folers.

For example in case the VSS snapshot fails during the backup, you might receive an error 'Specified source path "C:\I\need\to\backup\this\folder\at\all\times" does not exist; ignored' which causes exception.  If we surpress the error code, any files and folders who's path is not found due to VSS issue will not be backed up, but the backup will show successful.  The extreme situation would be that the backup succeeds with 0B backed up.

Hope it helps

View solution in original post

Reply