06-23-2014 12:29 AM
Folks,
i want to implement the Accelerator for NDMP.
NBU Master : 7.6.0.2 and Media server : Appliance 5320
I have gone through many documents and came to know we should have a mount server so that all NFS/CIFS are mount in that and take backup.
I have all CIFS mounts and have a physical windows server to mount. Now please let me know how do i mount the CIFS from NDMP to my win physical server. And what would be the Policy type and other required settings in Attributes in policy.
i tried simply mapping the CIFS as Y drive in mount server and tries taking backup policy type Windows, Enabled backup Network Drives.
But failed with SC 71
Could somebody assist me how to implement that.
6/23/2014 11:17:38 AM - connecting
6/23/2014 11:17:39 AM - Info bpbrm(pid=18301) starting bpbkar on client
6/23/2014 11:17:39 AM - connected; connect time: 0:00:01
6/23/2014 11:17:40 AM - Info bpbkar(pid=8872) Backup started
6/23/2014 11:17:40 AM - Info bpbrm(pid=18301) bptm pid: 18302
6/23/2014 11:17:40 AM - Info bpbkar(pid=8872) change time comparison:<enabled>
6/23/2014 11:17:40 AM - Info bpbkar(pid=8872) accelerator enabled backup, archive bit processing:<disabled>
6/23/2014 11:17:40 AM - Info bpbkar(pid=8872) not using change journal data for <Y:\>: not supported for non-local volumes / file systems
6/23/2014 11:17:40 AM - Info bptm(pid=18302) start
6/23/2014 11:17:41 AM - Info bptm(pid=18302) using 1048576 data buffer size
6/23/2014 11:17:41 AM - Info bptm(pid=18302) setting receive network buffer to 262144 bytes
6/23/2014 11:17:41 AM - Info bptm(pid=18302) using 32 data buffers
6/23/2014 11:17:43 AM - Info bptm(pid=18302) start backup
6/23/2014 11:17:45 AM - Info bptm(pid=18302) backup child process is pid 18315
6/23/2014 11:17:45 AM - begin writing
6/23/2014 11:17:50 AM - Info bpbrm(pid=18301) from client dcabak02.dca.com: TRV - object not found for file system backup: Y:
6/23/2014 11:17:50 AM - Error bptm(pid=18315) system call failed - Connection reset by peer (at child.c.1306)
6/23/2014 11:17:50 AM - Info bpbkar(pid=8872) accelerator sent 0 bytes out of 0 bytes to server, optimization 0.0%
6/23/2014 11:17:50 AM - Error bptm(pid=18315) unable to perform read from client socket, connection may have been broken
6/23/2014 11:17:50 AM - Error bptm(pid=18302) media manager terminated by parent process
6/23/2014 11:17:54 AM - Info srt3symapl02(pid=18302) StorageServer=PureDisk:srt3symapl02; Report=PDDO Stats for (srt3symapl02): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
6/23/2014 11:17:54 AM - Error bpbrm(pid=18301) could not send server status message
6/23/2014 11:17:55 AM - Info bpbkar(pid=8872) done. status: 71: None of the files mentioned in the file list exist or may not be accessible
6/23/2014 11:17:55 AM - end writing; write time: 0:00:10
None of the files mentioned in the file list exist or may not be accessible(71)
Solved! Go to Solution.
06-23-2014 12:49 AM
You need to use UNC path for CIFS shares, not drive letters. Also change NBU logon account on Windows server to a domain user with sufficient rights on the share and select 'Backup Network drives' in policy attributes.
TNs:
http://www.symantec.com/docs/HOWTO85828
http://www.symantec.com/docs/TECH198175
http://www.symantec.com/docs/HOWTO87080
Excellent blog:
06-23-2014 12:49 AM
You need to use UNC path for CIFS shares, not drive letters. Also change NBU logon account on Windows server to a domain user with sufficient rights on the share and select 'Backup Network drives' in policy attributes.
TNs:
http://www.symantec.com/docs/HOWTO85828
http://www.symantec.com/docs/TECH198175
http://www.symantec.com/docs/HOWTO87080
Excellent blog:
06-23-2014 08:01 AM
Dont map the drive, just add //ndmpdevice/sharename to the file list (as per Marianne's post.)
06-23-2014 08:13 AM
Using mount points is also a very good way to map to remote data and helps VSS to get a proper hold on the disk for an efficient backup and deal with open files.
The accelerator information i have is that it does NOT recognise UNC paths - so you cannot do it that way - it needs to be a mapped drive or preferably a mount point.
The backup selection is very easy then .. just something like d:\NDMPfolder\
06-23-2014 09:31 PM
Seems we have conflicting experiences. A Mapped Drive of a UNC path has always failed and I had to enter it as \\xxxx\xxxxxx. Think Marianne would say the same.
Any tricks Mark?
I also didn't know that you can VSS to work with remote file systems. Seems its possible in 2012 and SMB 3.0. http://technet.microsoft.com/en-us/library/jj612865.aspx
Interesting.
06-23-2014 10:16 PM
I do not have 1st-hand experience, but if I read Abdul Rasheed's blog, it seems to me if it is supported.
All NBU documentation says to backup CIFS shares as UNC path.
06-23-2014 10:37 PM
Accelerator will support for UNC paths, All backup selections should be UNC paths, Also Mapped NTFS drives are compatible.
Specify filesystems path in backup selection this is applicable for systemstate & VSS as well
06-23-2014 10:43 PM
If you use accelerator you should use seperate policy to bakup VSS & Sytemstate and different policy for filesystem backups as like vm backups.
Test it and share results.
06-24-2014 02:16 AM
OK - I was going on a Symantec partner supplied Accelerator doc but it appears that the UNC matter was actually resolved in 7.5.0.1 - apologies!!
The VSS comment was in relation to using mount points as the O/S then sees it as a local folder and seems to get a handle on it better - UNC paths will invariably not get a lock on open files - not just a 2012 thing - i dont have any microsoft statement to support that it is just from my experience and what i have seen and I have a customer who uses it a lot in flashbackup-windows which i assume need VSS to do the snapshots?
06-24-2014 03:02 AM
I have enabled the mount host NBu services on Domain account that have access to the NDMP share.
Created policy with Ms-Windows type and selection as \\dxbfiler\test$\.
But backup failied with below error
Do i need to do anything else in teh mount host ?
6/24/2014 1:56:54 PM - Info nbjm(pid=6200) starting backup job (jobid=99279) for client srt3dms03, policy Test_NDMP, schedule Full
6/24/2014 1:56:54 PM - estimated 0 Kbytes needed
6/24/2014 1:56:54 PM - Info nbjm(pid=6200) started backup (backupid=srt3dms03_1403603814) job for client srt3dms03, policy Test_NDMP, schedule Full on storage unit srt3symapl02-msdp-1
6/24/2014 1:56:56 PM - started process bpbrm (20699)
6/24/2014 1:56:57 PM - Info bpbrm(pid=20699) srt3dms03 is the host to backup data from
6/24/2014 1:56:57 PM - Info bpbrm(pid=20699) reading file list for client
6/24/2014 1:56:58 PM - Info bpbrm(pid=20699) accelerator enabled
6/24/2014 1:56:58 PM - Info bpbrm(pid=20699) There is no complete backup image match with track journal, a regular full backup will be performed.
6/24/2014 1:56:58 PM - connecting
6/24/2014 1:56:59 PM - Info bpbrm(pid=20699) starting bpbkar on client
6/24/2014 1:56:59 PM - connected; connect time: 0:00:01
6/24/2014 1:57:03 PM - Info bpbkar(pid=6484) Backup started
6/24/2014 1:57:03 PM - Info bpbrm(pid=20699) bptm pid: 20728
6/24/2014 1:57:04 PM - Info bptm(pid=20728) start
6/24/2014 1:57:05 PM - Info bptm(pid=20728) using 1048576 data buffer size
6/24/2014 1:57:05 PM - Info bptm(pid=20728) setting receive network buffer to 524288 bytes
6/24/2014 1:57:05 PM - Info bptm(pid=20728) using 32 data buffers
6/24/2014 1:57:06 PM - Info bptm(pid=20728) start backup
6/24/2014 1:57:08 PM - Info bptm(pid=20728) backup child process is pid 20741
6/24/2014 1:57:08 PM - begin writing
6/24/2014 1:57:20 PM - Info bpbrm(pid=20699) from client srt3dms03: TRV - object not found for file system backup: \\dxbfiler\test$\
6/24/2014 1:57:20 PM - Info bpbkar(pid=6484) accelerator sent 0 bytes out of 0 bytes to server, optimization 0.0%
6/24/2014 1:57:20 PM - Error bptm(pid=20741) system call failed - Connection reset by peer (at child.c.1306)
6/24/2014 1:57:21 PM - Error bptm(pid=20741) unable to perform read from client socket, connection may have been broken
6/24/2014 1:57:21 PM - Error bptm(pid=20728) media manager terminated by parent process
6/24/2014 1:57:26 PM - Info srt3symapl02(pid=20728) StorageServer=PureDisk:srt3symapl02; Report=PDDO Stats for (srt3symapl02): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
6/24/2014 1:57:26 PM - Error bpbrm(pid=20699) could not send server status message
6/24/2014 1:57:26 PM - Info bpbkar(pid=6484) done. status: 71: None of the files mentioned in the file list exist or may not be accessible
6/24/2014 1:57:26 PM - end writing; write time: 0:00:18
None of the files mentioned in the file list exist or may not be accessible(71)
06-24-2014 03:11 AM
06-24-2014 03:35 AM
I agree with Mark. Don't use $ in the path.
Please ensure that you follow ALL steps in the posts above:
Check NBU Client service on the Windows server that is selected in Clients tab - ensure that Domain account is specified with sufficient permissions. do the same for Legacy Client service as well.
Check that 'Backup Network drives' is selected in attributes.
Test if share can be accessed by logging on to Windows client with same user specified in Client and Legacy services, then Start, type, \\FILER-name\Path and see if Explorer Window opens with Folders and files visible.
Have you had a look at the TNs that I have listed above?
Another TN: http://www.symantec.com/docs/HOWTO34955
06-25-2014 07:42 AM
There was some issue with the domain user account. Tried with other domain user that NAS admin using.
Now accelerator is working with the path \\dxbfiler\test$
From mount host and from any other host,without $ we are not able to access any shares. Hence tried the policy selection with \\dxbfiler\test$ and it is working fine. Accelerator is giving expected good result.
But now the challenge is we have more than 350-400 shares in the NAS, all these shares has to be mentioned in the policy which is a challenging task and have to add new shares in the policy everytime when a new share created.
is that possible to add like NDMP policy selection /root_vdm_1/GROUP_SERVICES ?
07-02-2014 08:11 AM
No.
You cannot specify a path to a share like you do with NDMP policy.
NDMP path is only possible when you backup directly from the filer.
When you backup via a Windows server, you can only backup using UNC path as explained in previous posts.
07-14-2014 10:47 AM
I have implemented this but th problem is the domain account that used doesnot have the access to all shares, for such shares backupis failing with SC 71. There are few shares that vip users data that no one hav the access except those users.
I dont think so accelerator for NDMP is not a good chaoice for me. I rasied a symantec case for this but got response that Accelerator with NDMP is not 100% accurate as it have permission issues.
07-14-2014 11:02 AM
You do not have a Symantec or NetBackup problem, rather with Windows access rights.
There should always be a Domain Admin account that has full access to anything and everything in the environment. How else can permissions be set if there is not a Domain Admin account with full rights to everything?
You need to start Client Service with this account name.
There is nothing that Symantec Support can do to change this requirement for automated backups started from the NBU scheduler.
The only possible workaround is if the users perform their own manual backups by either using the GUI or from cmd with bpbackup, or bpbackup in a script.
07-15-2014 03:35 PM
If your domain admin account doesn't have permissions to backup the data - then should you really be attempting to read it with backups? You may, in effect, be attempting to breach your employers data security policy - and access restricted data that you are not authorised to access. Is the data officially "restricted"?
I wouldn't worry about it - if a VIP has protected the data - then bump the issue upwards to someone with the latitude to deal with it.