7 Replies Latest reply: Dec 3, 2013 12:36 PM by Ian Anderson RSS

Sharepoint VSS Plug-in

Efren

Anyone know which is the most updated version of the Sharepoint Vss plug-in and where I could download it

not find it anywhere

  • 1. Re: Sharepoint VSS Plug-in
    Leo Zhenjun Li

    Hey Efren,

     

    All Avamar plugin embedded on Avamar server. And in order to ensure compatibility, you need to install the plugin which is same with Avamar server versions.

     

    Example,

    If your Avamar server is 7.0, you just need to install the plugin from Avamar server 7.0.

    If your Avamar server is 6.1, you just need to install the plugin from Avamar server 6.1. You don't need to upgrade Avamar plugin to 7.0 separately.

     

    You can open a browser to http://Avamar_server and click Documents and Downloads. Then you can select and install "AvamarMossVSS-windows-x86_x64-version.msi" which is the Avamar Sharepoint VSS Plug-in.

     

    Please refer to Downloading the software section of Avamar 7.0 for SharePoint VSS User Guide on page 44.

     

     

    Hope this helps.

  • 2. Re: Sharepoint VSS Plug-in
    Efren

    Hi Leo,

     

    I understand that, but wanted to know if there is an updated plugin that I can use with my version of Avamar (6.1.1.-87) I have problems to backup Sharepoint.

     

    the database is located on a different server to the application

    shows me this error

     

    error11.PNG.png

  • 3. Re: Sharepoint VSS Plug-in
    Ian Anderson

    You should review the Avamar logs from the system STSPCN06. The message you've shown only indicates there was a problem on this back-end client.

  • 4. Re: Sharepoint VSS Plug-in
    Efren

    I think it will be a network problem between STSPCN06 and sharepointserver

     

    2013-12-03 08:12:07 avagent Info <6686>: Process 3912 (C:\Program Files\avs\bin\avtar) for workorder progress-GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923 started

    2013-12-03 08:12:08 avagent Info <10684>: Setting ctl message version to 3 (from 1)

    2013-12-03 08:12:08 avagent Info <16136>: Setting ctl max message size to 268435456

    2013-12-03 08:12:54 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923"

    2013-12-03 08:12:55 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923"

    2013-12-03 08:13:36 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923"

    2013-12-03 08:13:39 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923"

    2013-12-03 08:14:16 avagent Info <6688>: Process 3912 (C:\Program Files\avs\bin\avtar) finished (code 0: success)

    2013-12-03 08:14:16 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var" * (timeout:30 seconds)

    2013-12-03 08:14:16 avagent Info <6985>: Directory "C:\Program Files\avs\var" returned 49 files complete?yes

    2013-12-03 08:14:17 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var\clientlogs" * (timeout:30 seconds)

    2013-12-03 08:14:17 avagent Info <6985>: Directory "C:\Program Files\avs\var\clientlogs" returned 3 files complete?yes

    2013-12-03 08:14:21 avagent Info <6688>: Process 5292 (C:\Program Files\avs\bin\avsql) finished (code 0: success)

    2013-12-03 08:14:21 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var" * (timeout:30 seconds)

    2013-12-03 08:14:22 avagent Info <6985>: Directory "C:\Program Files\avs\var" returned 49 files complete?yes

    2013-12-03 08:14:22 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var\clientlogs" * (timeout:30 seconds)

    2013-12-03 08:14:22 avagent Info <6985>: Directory "C:\Program Files\avs\var\clientlogs" returned 3 files complete?yes

    2013-12-03 08:18:14 avagent Info <6624>: Attempted connection from non-localhost IP address - SHAREPOINTIP:50594 != '127.0.0.1'

    2013-12-03 08:18:14 avagent Info <10684>: Setting ctl message version to 3 (from 1)

    2013-12-03 08:18:15 avagent Info <16136>: Setting ctl max message size to 268435456

    2013-12-03 08:18:15 avagent Info <6686>: Process 4108 (C:\Program Files\avs\bin\avmossvss) for workorder GRP_CRITICIDAD_5_SHAREPOINT-1386080201461 started

    2013-12-03 08:18:16 avagent Info <10684>: Setting ctl message version to 3 (from 1)

    2013-12-03 08:18:16 avagent Info <16136>: Setting ctl max message size to 268435456

    2013-12-03 08:18:30 avagent Info <8636>: Starting CTL cancel of workorder "GRP_CRITICIDAD_5_SHAREPOINT-1386080201461".

    2013-12-03 08:18:41 avagent Warning <14836>: Unable to find manager for (3001-Windows-progress-GRP_CRITICIDAD_5_SHAREPOINT-1386080201461) while processing stop

    2013-12-03 08:18:41 avagent Warning <15188>: failed to process message type 35 stop_progress_avtar

    2013-12-03 08:18:41 avagent Error <6677>: Error processing CTL message "<stop_progress_avtar pid="SharePoint VSS" pidnum="3026" mid="4108/5724/33" wid="GRP_CRITICIDAD_5_SHAREPOINT-1386080201461" />

    "

    2013-12-03 08:18:44 avagent Info <8636>: Starting CTL cancel of workorder "GRP_CRITICIDAD_5_SHAREPOINT-1386080201461".

    2013-12-03 08:18:47 avagent Info <6688>: Process 4108 (C:\Program Files\avs\bin\avmossvss) finished (code 536870925: externally cancelled)

    2013-12-03 08:18:47 avagent Warning <6690>: CTL workorder "GRP_CRITICIDAD_5_SHAREPOINT-1386080201461" non-zero exit status 'code 536870925: externally cancelled'

    2013-12-03 08:18:47 avagent Info <9919>: Sending wrapup message to initiator agent

    2013-12-03 08:18:47 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var" * (timeout:30 seconds)

    2013-12-03 08:18:47 avagent Info <6985>: Directory "C:\Program Files\avs\var" returned 53 files complete?yes

    2013-12-03 08:18:47 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var\clientlogs" * (timeout:30 seconds)

    2013-12-03 08:18:47 avagent Info <6985>: Directory "C:\Program Files\avs\var\clientlogs" returned 3 files complete?yes

    2013-12-03 08:20:02 avagent Info <10684>: Setting ctl message version to 3 (from 1)

    2013-12-03 08:20:02 avagent Info <16136>: Setting ctl max message size to 268435456

    2013-12-03 08:20:02 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var" * (timeout:30 seconds)

    2013-12-03 08:20:02 avagent Info <6985>: Directory "C:\Program Files\avs\var" returned 53 files complete?yes

    2013-12-03 08:20:02 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var\clientlogs" * (timeout:30 seconds)

    2013-12-03 08:20:02 avagent Info <6985>: Directory "C:\Program Files\avs\var\clientlogs" returned 3 files complete?yes

    2013-12-03 08:20:11 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var" * (timeout:30 seconds)

    2013-12-03 08:20:11 avagent Info <6985>: Directory "C:\Program Files\avs\var" returned 53 files complete?yes

    2013-12-03 08:20:11 avagent Info <6984>: Browsing directory "C:\Program Files\avs\var\clientlogs" * (timeout:30 seconds)

    2013-12-03 08:20:11 avagent Info <6985>: Directory "C:\Program Files\avs\var\clientlogs" returned 3 files complete?yes

    2013-12-03 08:20:15 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SHAREPOINT-1386080201461"

    2013-12-03 08:58:40 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923"

    2013-12-03 08:58:43 avagent Info <5958>: Browsing logs for workorder "GRP_CRITICIDAD_5_SQL_STSPCN06-1386079847923"

  • 5. Re: Re: Sharepoint VSS Plug-in
    Ian Anderson

    I ran a search on the messages you pasted above and found two known causes of this issue.

     

    There is an issue in Avamar client version 6.0.100-592 that can cause this problem. I believe you mentioned that these clients are running version 6.1.101-87 so this is probably not the cause of the problem. Please double check to make sure all the clients in the MOSS farm have the same Avamar client version installed and that they are running 6.1.101-87 or newer.

     

    Another possible cause of this problem is that the clients in the MOSS farm have multiple network cards and are trying to communicate using the wrong networks. You can force the Avamar client agent to bind to a specific IP address by creating a file called "avagent.cmd" in the Avamar var directory (C:\Program Files\avs\var by default) and adding the following line (replace 192.168.x.x with the correct IP address for your environment):

    --netbind=192.168.x.x

     

    Once the file has been created, you will have to restart the Avamar backup agent (at an elevated command prompt, run "net stop avbackup" then "net start avbackup" or use the Services snap-in).

     

    Normally the back-end client is where this change needs to be made.

     

    If this does not resolve the issue, I would recommend opening a service request. If you open an SR, please provide zip files of the logs from each of the clients in the farm. Make a note of which set of logs is from which client and the role of each client (front-end or back-end).

     

    Hope this helps.

  • 6. Re: Re: Sharepoint VSS Plug-in
    Efren

    Hi  Ian

     

    was necessary to apply hotfixe 6.1.101-87_HF48600 to avagent and avmossvss , now its working fine

     

    thanks a lot

  • 7. Re: Sharepoint VSS Plug-in
    Ian Anderson

    I'm glad to hear that the problem has been resolved.

     

    Thanks for following up!