Forum Discussion

thomascouno's avatar
thomascouno
Level 3
9 years ago

Unable to set attributes on the .sv2i file

Hi,

We are running Windows Server 2011 and backing up to a buffalo NAS drive and have two jobs configured one does our "H" drive, the other does the "C, D, E, G and I" drives.  The backup backs up via a network share \\nasname\sbs-bkup, we have recently been getting the below errors

 

This error reports twice once for each backup job.

 

Error EC8F17B6: Cannot update the system index (.sv2i) file.
    Error E7D10016: Unable to set attributes on '//nasshare/sbs-bkup/servername.sv2i'.
        Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Access is denied.'
        Success.
Details: 
Source: Symantec System Recovery

 

These errors appear on the backup job success report in the event log and also on our SMTP logs

 

Info 6C8F1F7E: A scheduled incremental recovery point of drive H:\ was created successfully.
    Error E7D10016: Unable to set attributes on '//nasshare/sbs-bkup/servername.sv2i'.
        Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Access is denied.'
        Success.
Details: 
Source: Symantec System Recovery

 

Info 6C8F1F7E: A scheduled incremental recovery point of drive G:\ was created successfully.
    Error E7D10016: Unable to set attributes on '//nasshare/sbs-bkup/servername.sv2i'.

        Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Access is denied.'
        Success.
Details: 
Source: Symantec System Recovery

 

I found this page "http://www.veritas.com/community/forums/error-ec8f17b6-cannot-update-system-index-sv2i-file” which drew me to this site, unfortunately copying the file onto the server desktop and then back again did not fix the error. 

 

Any help would be much appreciated.

Thanks in advance

Thomas

Backup and Recovery
Not Applicable
SSR 2013
System Recovery

19 Replies

Sort By
Show More
  • thomascouno's avatar
    thomascouno
    Level 3
    9 years ago

    Hi,

     

    Yes i attempted to create the job again to the IP\sharename, but got the same error as i attached above.

     

    Thanks,

  • thomascouno's avatar
    thomascouno
    Level 3
    9 years ago

    Hi,

     

    Sorry for my delayed response, i have been away.

     

    Please could you go into more deatil on your above update?  I dont understand.

     

    Thanks,

     

     

  • Markus_Koestler's avatar
    Markus_Koestler
    Moderator
    9 years ago

    I assume that the SSR service runs as SYSTEM. So my idea is to disconnect all network drives that SYSTEM has mapped to get rid of the error you posted on the 17th.

  • thomascouno's avatar
    thomascouno
    Level 3
    9 years ago

    Thanks,

     

    Im still not 100% on how to do the above.

    Please advise what other effects this will have on the server.

     

     

  • thomascouno's avatar
    thomascouno
    Level 3
    9 years ago

    Great thanks for the confirmation.

     

    Please advise how/where i need to run the command.

  • Markus_Koestler's avatar
    Markus_Koestler
    Moderator
    9 years ago

    1.) get psexec from live.sysinternals.com

    2.) run psexec -s cmd

    3.) In this console enter: net use * /d /y

  • thomascouno's avatar
    thomascouno
    Level 3
    9 years ago

    Hi Markus,

     

    Applogies i did not get any notification to say the post had been updated.

     

    The client has decided to move to a hosted server environment, so will be will decomisioning the server and NAS box.

     

    Thanks for you help anyway.

     

    Kind Regards,