08-13-2014 03:21 PM
Hi All,
Due to we have no longer NDMP Backups on place, we are trying to back it up a CIFS (NTFS on NetApp) on our RHEL NBU Server, but we are receiving a lot of warning/errors.
Here what I did:
1. Mount CIFS Share
mount -t cifs -o username=netbackup,password=12345678,dir_mode=0755,file_mode=0775,defaults,directio,rsize=65536,wsize=57344 //filer-serv/C_SHARES$ /netbackup_cifs/
2. Create policy
Policy Type: Standard
Allow multiple data streams: yes
Backup Selection: /netbackup_cifs/
3. Run the backup
The "backup" complete and all files are backed up, but with errors. I have attached the job log file. Can someone help me
Thanks!
Solved! Go to Solution.
08-14-2014 01:19 PM
I believe you will find that even though the job details indicate a status 0 that you do not have a valid image (restorable). You will note that after all the warning messages you see this entry:
08/11/2014 17:13:40 - Info bpbkar (pid=7875) bpbkar waited 0 times for empty buffer, delayed 0 times
No data was transferred by bpbkar
The problem is that you are attempting to mount the NetApp Filer as a CIFS share in a Linux Environment. CIFS is for Windows Environments and NFS is for Linux. Please see the following documentation which describes how to backup CIFS shares in a Windows environment.
http://www.symantec.com/docs/TECH198175
08-14-2014 12:07 PM
Who is the client?
Sounds like you are using a media server as the client with a mount point to the fileserver using the cross mount points feature.
I am curious about using policy type "MS-Windows" for this backup. It might not work at all. If you had a Windows server near the NDMP device that you could map the network drive. Then you could certainly use the Windows policy type.
It seems odd to use an MS protocol between a bunch of Linux servers...
Could you share the folder from Netapp using NFS and then mount that natively in the RHEL system?
EDIT:
Information about the error you are getting:
http://www.symantec.com/business/support/index?page=content&id=TECH38434
08-14-2014 01:19 PM
I believe you will find that even though the job details indicate a status 0 that you do not have a valid image (restorable). You will note that after all the warning messages you see this entry:
08/11/2014 17:13:40 - Info bpbkar (pid=7875) bpbkar waited 0 times for empty buffer, delayed 0 times
No data was transferred by bpbkar
The problem is that you are attempting to mount the NetApp Filer as a CIFS share in a Linux Environment. CIFS is for Windows Environments and NFS is for Linux. Please see the following documentation which describes how to backup CIFS shares in a Windows environment.
http://www.symantec.com/docs/TECH198175
08-15-2014 09:48 AM
Hi INT_RND,
Yes, we are using the Media/Master Server (RHEL) as the client with a mount point to the filer.
We can't share the folder from NetApp using NFS due to NTFS permissions. That is the reazon for what we can't mount the share as NFS on RHEL
08-15-2014 12:23 PM
There was another suggestion to use a Windows Media server or client where CIFS share can be backed up from.
See TN in above post.
Have you tried this yet?
08-17-2014 09:23 PM
You don't need to mount the volume, also for backing up NTFS permissions correctly, you need to back it up from a Windows client. Even then, you may find some metadata skipped, the correct way to backup NAS volumes with all metadata is a volume dump (using NDMP). Other option is to use a Windows proxy client.
Symantec have a technote for this problem, and also one mentioned above http://www.symantec.com/docs/HOWTO34483
08-18-2014 12:39 AM
Hi ,
Try to change the credentials in the master server client and legacy client services for the account which is having acces to the NDMP filesystem monuted in the server , try triggering backup it will work.
If it works plan accrdingly for the further backups.
08-19-2014 04:32 PM
If possible, please consider to mount via NFS. If user mapping from unix user to ntfs user is well configured(like YOUR_DOMAIN¥administrator <= root) on NetApp, you can access files under ntfs security style path via NFS.