FSA 7.0 SP1, NetAPP and Visio
Hello all,
I've been trying to find the answer to some strange issues I've seen at a client site.
We currently have the following:
1) Single EV 7.0 SP1 server with PlaceHolder service (same version).
2) NetAPP FAS940 DataONTap 7.0.5 which we are FSA archiving two test directories from.
3) Added the EV Service account to local admins on the Netapp.
I added the Placeholder service, created the FSA archiving task, added the NAS, the volume, the archive points, and started running the task. I am using regular placeholders (not internet shortcuts). The archiving task works just fine, and all the placeholders show up on the NAS CIFS share.
I have a couple of issues though:
1) The placeholder icons always show 0KB regardless of the FileSizeEmulation Registry key on the Ev7 server. I have set it to both 0 and 1, restarted the placeholder service, re-ran the tasks, re-created the placeholders with the FSAutility, and still always they are 0KB.
2) Archived Visio files cannot be opened properly from the full Visio client. The viewer is always able to open the Visio files without issue, but when the full program tries, it pulls up 7,9,11,or 16KB (which the placeholder changes to) and doesn't show me anything. It almost seems like the full archived file is not available, but if I "restore" a previous version, the full file returns.
Additionally, I have torn down the entire FSA set of tasks, policies, and started "from scratch" after restoring the directory from backup. I have also tried excluding Visio's from Content Conversion using the registry key.
I have also added McShield.exe (they use McAfee version 8.0.0) to the "excludedexes" on EV7.
So far nothing has fixed this. Has anyone seen this issue? The only caveat is that the server is running on Windows 2003 SP2, which apparently is not fully supported for EV7.0 Sp1. I plan to launch a DTrace session for retrieval tomorrow morning and see if any other programs are trying to access the files.
Any advice would be very much appreciated before I proceed to open a support call with Symantec.
Regards and thanks,
10e
I've been trying to find the answer to some strange issues I've seen at a client site.
We currently have the following:
1) Single EV 7.0 SP1 server with PlaceHolder service (same version).
2) NetAPP FAS940 DataONTap 7.0.5 which we are FSA archiving two test directories from.
3) Added the EV Service account to local admins on the Netapp.
I added the Placeholder service, created the FSA archiving task, added the NAS, the volume, the archive points, and started running the task. I am using regular placeholders (not internet shortcuts). The archiving task works just fine, and all the placeholders show up on the NAS CIFS share.
I have a couple of issues though:
1) The placeholder icons always show 0KB regardless of the FileSizeEmulation Registry key on the Ev7 server. I have set it to both 0 and 1, restarted the placeholder service, re-ran the tasks, re-created the placeholders with the FSAutility, and still always they are 0KB.
2) Archived Visio files cannot be opened properly from the full Visio client. The viewer is always able to open the Visio files without issue, but when the full program tries, it pulls up 7,9,11,or 16KB (which the placeholder changes to) and doesn't show me anything. It almost seems like the full archived file is not available, but if I "restore" a previous version, the full file returns.
Additionally, I have torn down the entire FSA set of tasks, policies, and started "from scratch" after restoring the directory from backup. I have also tried excluding Visio's from Content Conversion using the registry key.
I have also added McShield.exe (they use McAfee version 8.0.0) to the "excludedexes" on EV7.
So far nothing has fixed this. Has anyone seen this issue? The only caveat is that the server is running on Windows 2003 SP2, which apparently is not fully supported for EV7.0 Sp1. I plan to launch a DTrace session for retrieval tomorrow morning and see if any other programs are trying to access the files.
Any advice would be very much appreciated before I proceed to open a support call with Symantec.
Regards and thanks,
10e
