In order to perform Sharepoint Backups you need to follow few steps
1> Avamar Backup Agent should be running with Sharepoint Administrator priviledge Account
2> You need a share directory on network or on the local computer and following users should have full permissions on that share
• SQL service • MOSS service • System • Network services
3>After initial selections for backups, click on Backup Now-> More Options ->In the Backup Command Line Option specify the path of the share directory which we created in step 2
I assigned rights to this to the account that has access to SQL, Sharepoint Farm, etc.
I used this same account as the service account for the Backup service running on the local machine. I restarted the service.
I did "backup now", "more options" and put in \\x.x.x.x\SharePoint2007
I submitted the backup, and it failed, with this error:
"Cannot find a shared folder that would belong to the given path '\\x.x.x.x\sharepoint2007'"
Of course, I used the real IP address of the machine, not x.x.x.x in all of the above. I also verified that, on the sharepoint front-end server, and using the service account credentials used in all the above, I can open and read/write on the share being used.
2) The local folder you assign has to have a share configured for itself
In other words... you cannot use "\\server\sharename" when you configure the backup options... you have to use c:\foldername.
However, this will not work if there is not a share configured for c:\foldername.
I was trying to use c:\foldername (without a share configured for that folder) and then I tried \\differentserver\sharename (without trying to use a local directory)... but both of these failed.
However, now I'm getting a different error (two, in fact). It appears to backup all the SQL databases, but then it seems to have problems accessing the files it already created on the local temporary backup area (the location I specified when I ran the backup job):
Error: Object Shared Search Index failed in event OnBackup. For more information, see the error log located in the backup directory.
InvalidOperationException: System.UnauthorizedAccessException: Access to the path '\\servername\sharename\MOD-1268071384998#1\spbr0000\05b712ef-b039-46c0-a2ab-7291d00a10c7' is denied.
Error: Object aea9585b-77c7-4c80-8845-3b052d1a3289 failed in event OnBackup. For more information, see the error log located in the backup directory.
InvalidOperationException: System.UnauthorizedAccessException: Access to the path '\\servername\sharename\MOD-1268071384998#1\spbr0000\aea9585b-77c7-4c80-8845-3b052d1a3289' is denied.
So I still have some kind of rights problem... just not sure what it is.
There are two servers involved here....
1) Front-end web server, Windows 2008 R2 x64, with avamar Backup Agent service on it, and SharePoint plugin installed. Backup Agent is using the same service account as SharePoint, SQL, etc.
2) SQL server, Windows 2008 R2 x64, with avamar Backup Agent service on it, and SQL plugin installed. Backup Agent is using the same service account as SharePoint, SQL, etc.
Also, the share I used on Server #1 had read-write rights for the service account used in all the above stuff, as well as "system" and "network service".
* Creates a folder called MOD-1268071384998#1\spbr0000
* Creates a lot of hex-numbered files beginning with MOD-1268071384998#1\spbr0000\00000000.bak, basically sticking the contents of all the sql databases into these files, as well as some other things from sharepoint
* Tries to access MOD-1268071384998#1\spbr0000\05b712ef-b039-46c0-a2ab-7291d00a10c7 and gets an "access denied" error; however, this folder/file does not exist at all; there is no log entry of the backup ever even attempting to create it prior to it's failed attempt to access it.
* Tries to access MOD-1268071384998#1\spbr0000\aea9585b-77c7-4c80-8845-3b052d1a3289 and gets an "access denied" error; however, this folder/file does not exist at all. there is no log entry of the backup ever even attempting to create it prior to it's failed attempt to access it.
So, something is not quite right here.
Either the log is never showing a failure during the attempt to create these files prior to it's attempting to access them,
OR
There is no attempt to create these files prior to accessing them,
OR
The backup is attempting to create them in the process of accessing them.
I would guess it's the latter, since I see nothing previously in the log file, but why is it unable to create these files/folders, when it already created all the other ones?
The temporary shared folder has two types of permissions. Share permission and the file folder permission. The following are required to have all access as a file and as a share to the folder shared:
- the user running the MOSS service
- the user running the SQL service
- Network services user
- Local System
The difference in how the files are read and written to is that the MOSS and SQL service are writing to the folder as a share, when the backup is connecting to it as a mapped file.
Thought I'd share with the community something I just learned while attempting to get the SharePoint plug-in working:
I set up the temporary folder, shared it, and applied all the permissions (both share & NTFS level) that the documentation specifies. The Backup Agent service was running as my SharePoint farm services account, and I could successfully browse the farm hierarchy from the Backup interface in Avamar Administrator. However, when actually running a backup I received the following errors:
2010-06-07 17:18:25 avmoss Info <8237>: NetShareEnum failed. ERROR = 5 2010-06-07 17:18:25 avmoss Error <8221>: Cannot find a shared folder that would belong to the given path 'e:\backuptemp'.
Double-checked the share and all permissions, even opened an SR and the support engineer triple-checked them. Turns out that the Avamar plugin is assuming/requiring that the service account is a member of the local Administrators group on the SharePoint server, in order to enumerate the share for the temporary folder. Mine was not...per least-privilege best practice from Microsoft, the farm services account should NOT be a local Admin on any of your farm servers.
Engineer said he'd raise this to the product group as a potential fix/enhancement.
Amol
2 Intern
•
207 Posts
0
March 5th, 2010 12:00
In order to perform Sharepoint Backups you need to follow few steps
1> Avamar Backup Agent should be running with Sharepoint Administrator priviledge Account
2> You need a share directory on network or on the local computer and following users should have full permissions on that share
• SQL service • MOSS service • System • Network services
3>After initial selections for backups, click on Backup Now-> More Options ->In the Backup Command Line Option specify the path of the share directory which we created in step 2
4> Perform the Backups
Regards
Amol Powar
caii-marcosa
8 Posts
0
March 8th, 2010 09:00
Ok, I created a share at \\x.x.x.x\SharePoint2007
I assigned rights to this to the account that has access to SQL, Sharepoint Farm, etc.
I used this same account as the service account for the Backup service running on the local machine. I restarted the service.
I did "backup now", "more options" and put in \\x.x.x.x\SharePoint2007
I submitted the backup, and it failed, with this error:
"Cannot find a shared folder that would belong to the given path '\\x.x.x.x\sharepoint2007'"
Of course, I used the real IP address of the machine, not x.x.x.x in all of the above. I also verified that, on the sharepoint front-end server, and using the service account credentials used in all the above, I can open and read/write on the share being used.
Any other ideas here ?
caii-marcosa
8 Posts
0
March 8th, 2010 10:00
Ok, I figured out the problem...
1) You have to assign a local folder
2) The local folder you assign has to have a share configured for itself
In other words... you cannot use "\\server\sharename" when you configure the backup options... you have to use c:\foldername.
However, this will not work if there is not a share configured for c:\foldername.
I was trying to use c:\foldername (without a share configured for that folder) and then I tried \\differentserver\sharename (without trying to use a local directory)... but both of these failed.
However, now I'm getting a different error (two, in fact). It appears to backup all the SQL databases, but then it seems to have problems accessing the files it already created on the local temporary backup area (the location I specified when I ran the backup job):
Error: Object Shared Search Index failed in event OnBackup. For more information, see the error log located in the backup directory.
InvalidOperationException: System.UnauthorizedAccessException: Access to the path '\\servername\sharename\MOD-1268071384998#1\spbr0000\05b712ef-b039-46c0-a2ab-7291d00a10c7' is denied.
Error: Object aea9585b-77c7-4c80-8845-3b052d1a3289 failed in event OnBackup. For more information, see the error log located in the backup directory.
InvalidOperationException: System.UnauthorizedAccessException: Access to the path '\\servername\sharename\MOD-1268071384998#1\spbr0000\aea9585b-77c7-4c80-8845-3b052d1a3289' is denied.
So I still have some kind of rights problem... just not sure what it is.
There are two servers involved here....
1) Front-end web server, Windows 2008 R2 x64, with avamar Backup Agent service on it, and SharePoint plugin installed. Backup Agent is using the same service account as SharePoint, SQL, etc.
2) SQL server, Windows 2008 R2 x64, with avamar Backup Agent service on it, and SQL plugin installed. Backup Agent is using the same service account as SharePoint, SQL, etc.
Also, the share I used on Server #1 had read-write rights for the service account used in all the above stuff, as well as "system" and "network service".
caii-marcosa
8 Posts
0
March 8th, 2010 10:00
Ok, now I see that it does the following:
* Creates a folder called MOD-1268071384998#1
* Creates a folder called MOD-1268071384998#1\spbr0000
* Creates a lot of hex-numbered files beginning with MOD-1268071384998#1\spbr0000\00000000.bak, basically sticking the contents of all the sql databases into these files, as well as some other things from sharepoint
* Tries to access MOD-1268071384998#1\spbr0000\05b712ef-b039-46c0-a2ab-7291d00a10c7 and gets an "access denied" error; however, this folder/file does not exist at all; there is no log entry of the backup ever even attempting to create it prior to it's failed attempt to access it.
* Tries to access MOD-1268071384998#1\spbr0000\aea9585b-77c7-4c80-8845-3b052d1a3289 and gets an "access denied" error; however, this folder/file does not exist at all. there is no log entry of the backup ever even attempting to create it prior to it's failed attempt to access it.
So, something is not quite right here.
Either the log is never showing a failure during the attempt to create these files prior to it's attempting to access them,
OR
There is no attempt to create these files prior to accessing them,
OR
The backup is attempting to create them in the process of accessing them.
I would guess it's the latter, since I see nothing previously in the log file, but why is it unable to create these files/folders, when it already created all the other ones?
eromanow1
13 Posts
0
March 31st, 2010 11:00
The temporary shared folder has two types of permissions. Share permission and the file folder permission. The following are required to have all access as a file and as a share to the folder shared:
- the user running the MOSS service
- the user running the SQL service
- Network services user
- Local System
The difference in how the files are read and written to is that the MOSS and SQL service are writing to the folder as a share, when the backup is connecting to it as a mapped file.
HiH
Ewa
dbarr1
3 Posts
0
June 9th, 2010 11:00
Thought I'd share with the community something I just learned while attempting to get the SharePoint plug-in working:
I set up the temporary folder, shared it, and applied all the permissions (both share & NTFS level) that the documentation specifies. The Backup Agent service was running as my SharePoint farm services account, and I could successfully browse the farm hierarchy from the Backup interface in Avamar Administrator. However, when actually running a backup I received the following errors:
2010-06-07 17:18:25 avmoss Info <8237>: NetShareEnum failed. ERROR = 5
2010-06-07 17:18:25 avmoss Error <8221>: Cannot find a shared folder that would belong to the given path 'e:\backuptemp'.
Double-checked the share and all permissions, even opened an SR and the support engineer triple-checked them. Turns out that the Avamar plugin is assuming/requiring that the service account is a member of the local Administrators group on the SharePoint server, in order to enumerate the share for the temporary folder. Mine was not...per least-privilege best practice from Microsoft, the farm services account should NOT be a local Admin on any of your farm servers.
Engineer said he'd raise this to the product group as a potential fix/enhancement.
Dan