Forum Discussion

Mike_Lawler's avatar
Mike_Lawler
Level 4
15 years ago

FSA placeholders not being created

We recently upgraded our EV server, our file server and our sql server (versions, names everything...)

So, we're running EV8.3 on a W2k8x64 sp2 enterprise server, our file server is W2k8x64 sp2 standard, and our SQL is 2005.

Disk is all netapp disk, attached to the servers as (ev and file) as mount points.

I run the Task to archive the file server and it chugs along creating archives (can see them in archive explorer), but on the file server no placeholders are created.  Has anyone run into anything like this?

If anyone requires more info please let me know and I'll do my best to fill you in.

Thanks alot all.
Enterprise Vault
Information Governance
  • Mike_Lawler's avatar
    Mike_Lawler
    15 years ago
    OK, for the error above, that was me...I'll admit to it!

    We have our server setup for DFS, and the DFS shares are in the same place as the actual folders (OK, not my brightest moment, but its done now and we're not changing it).  So, I setup EV to archive \\Server\Share\Folder and the archive works, however, the placeholder service, which runs local on the file server, creates placeholders at d:\Folder\Folder....and tries to navigate into a DFS folder, which of course it can't.

    So, change the targets, create new shares (non-dfs) and archive gets a little further...heres my new error!

    Task run: 1
    Time File Size (bytes) Policy name Rule name Rule type Archive status Shortcut type Shortcut status
    --------------------------------------------------------------------------------------------------------------------------------------------------
    3/31/2010 1:19:33 PM \\Server\Share\FIle 11776 Default FSA Volume Policy Office Files ARCHIVE  *** Error *** - Error making file: \\?\UNC\Server\share\filea placeholder file. The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)

    Back to Tech support for me....*sigh*
     
  • TonySterling's avatar
    TonySterling
    Moderator
    15 years ago
    Have your Vault Store Partitions been backed up?   Normally the placeholders will be created on the next FSA task run after the vault store parition is backed up.
  • Mike_Lawler's avatar
    Mike_Lawler
    Level 4
    15 years ago
    Backups are running, I'll verify that NBU is actually capturing this data and let you know.  we do have nbu set to take the services offline while it does the backups, so it SHOULD be hitting it....but you never know.

    Edit:

    Confirmed, vault stores are being backed up.
  • Mike_Lawler's avatar
    Mike_Lawler
    Level 4
    15 years ago
    Here's what I'm getting:

     *** Error *** - Error checking if file: \\?\UNC\*******\uncpaths\Users\*****\UserName_LastName\My Documents\****\My Music\Shania Twain\Come on Over [International]\AlbumArt_{58D1A2D8-FC30-46AA-9DC1-52084203A351}_Large.jpg is a placeholder file. The network location cannot be reached. For information about network troubleshooting, see Windows Help. (Exception from HRESULT: 0x800704D0)

    However, both servers have good access to each other, Symantec had me run the SAS tool on each of them and communication comes back as excellent, so I'm fairly confident it's not a matter of being unable to reach the remote server.
  • Mike_Lawler's avatar
    Mike_Lawler
    Level 4
    15 years ago
    Ok, here is what I've found so far....

    If I create a test volume on my file and print server on the c:\ drive (local disk) I can archive it and it creates placeholders....

    If I create a test volume on my file and print server on the d:\ drive (san disk) I can archie it, but not create placeholders...

    If I create a test volume on my file and print server, on the d:\ drive under a mount point I can archive it, but not create placeholders...

    Seems to me that EV is having a problem with NetApp at this point.  I've checked the KB articles and there is listings out there for EV7 and Netapp  Data ONTap 7 and below, but we are running 7.3 and EV8.3, so I would think those issues would be resolved, but I'll leave it to Symantec and NetApp to decide if they are or not...I'll keep you informed on what they find out in case anyone else runs into this problem.  Once it's all solved I'll post my case number so it can be refereced for any issues in the future as well.
  • Mike_Lawler's avatar
    Mike_Lawler
    Level 4
    15 years ago

    For those interested:

     

    It appears that our issue was not Netapp (dataOnTap) related.  When I disable Symantec Endpoint I'm able to create pointers, I'm currently searching for the client side exclusions that need to be made for me to be allowed to make placeholders on my file server (I've found the document for the EV server side exclusions and have those in place).

  • TonySterling's avatar
    TonySterling
    Moderator
    15 years ago

    oh wow!

     

    Is this the doc you need?


    http://support.veritas.com/docs/327346

    Placeholders are not getting created and Symantec Antivirus is installed on the file server
    Details:
    When running file archiving task, the placeholders get created but immediately recall.
    Cause:
    Symantec Antivirus is set to scan files opened for backup which is the same as "Offline" files.
     
    Resolution:
    Configure "File System Auto-Protect" within the properties of Symantec Antivirus and uncheck "Opened for backup" option.
  • Mike_Lawler's avatar
    Mike_Lawler
    Level 4
    15 years ago

    Unfortunatly no, that is for SAV, SEP has that set by default, but it appears that we are still having the same issue as described.  I verified that our policy is setup for this, but something else is getting in the way.

     Checking the REgsitry shows that I've already got the ExculdedExes reg key set to not allow rtvscan or smc to unarchive items.  Frustrating, very frustrating.  I'll leave it to the experts at symantec to figure it out.

  • Mike_Lawler's avatar
    Mike_Lawler
    Level 4
    15 years ago
    Update:

    OK, so I've turned off the Endpoint Protection on the server and ran the archive task, and I'm still having issues, so it's not an Endpoint problem, it's something in EV that is causing the errors.  I'm trying to work with Tech support to get it resolved now...