Unsolved
This post is more than 5 years old
2 Intern
•
63 Posts
0
7214
October 8th, 2009 02:00
NDMP backup of NetApp vFiler
Hello all,
We are setting up an NDMP backup of our NetApp storage box to our NetWorker backup environment.
I was able to do ndmp backups of the storage box, by creating a networker client instance and the following backup command:
nsrndmp_save -M -T dump -J storage_node -s backup_server -P backup_server
Now, if we do this for all our data on that NetApp filer, a user who is doing a restore can see all the data of the entire NetApp filer.
Therefor, I would like to create a NetWorker client instance of a vFiler on that NetApp storage box, and take it's data the same way into backup.
This way, a user doing a restore, only see's the data of that vFiler, not of the entire box.
I have used the exact same command, and made sure the remote user and password are correct (the root user of the vFiler).
But I get the following error:
1 retry attempted
42597:nsrndmp_save: connect auth: connection has not been authorized
42610:nsrndmp_save: The NDMP connection is not successfully authorized on host 'vfiler'.
42884:nsrndmp_save: Not able to connect or authorize the client 'vfiler'
Anyone knows what the problem might be?
Some checks I've already done:
- storage_node and backup_server are put in the Filer's and vfilers hosts file
- vfiler is put in the hosts-file of the storage node and the backup server
- ping is possible from vfiler to backup server and storage node and visa versa
- ssh is possible from backup server and storage node to vfiler
What I did see, was when I did a help command on the filer, I saw that there was the 'dump' command. When I did this on the vfiler, there was no 'dump' command.
Kind regards
We are setting up an NDMP backup of our NetApp storage box to our NetWorker backup environment.
I was able to do ndmp backups of the storage box, by creating a networker client instance and the following backup command:
nsrndmp_save -M -T dump -J storage_node -s backup_server -P backup_server
Now, if we do this for all our data on that NetApp filer, a user who is doing a restore can see all the data of the entire NetApp filer.
Therefor, I would like to create a NetWorker client instance of a vFiler on that NetApp storage box, and take it's data the same way into backup.
This way, a user doing a restore, only see's the data of that vFiler, not of the entire box.
I have used the exact same command, and made sure the remote user and password are correct (the root user of the vFiler).
But I get the following error:
1 retry attempted
42597:nsrndmp_save: connect auth: connection has not been authorized
42610:nsrndmp_save: The NDMP connection is not successfully authorized on host 'vfiler'.
42884:nsrndmp_save: Not able to connect or authorize the client 'vfiler'
Anyone knows what the problem might be?
Some checks I've already done:
- storage_node and backup_server are put in the Filer's and vfilers hosts file
- vfiler is put in the hosts-file of the storage node and the backup server
- ping is possible from vfiler to backup server and storage node and visa versa
- ssh is possible from backup server and storage node to vfiler
What I did see, was when I did a help command on the filer, I saw that there was the 'dump' command. When I did this on the vfiler, there was no 'dump' command.
Kind regards
0 events found
No Events found!


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
October 8th, 2009 03:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
October 8th, 2009 03:00
I'm also confused with point where you claim you put servers file on filer and vfiler - if those are ndmp appliances then you don't have that. Can you explain this a little bit more?
TimTh
2 Intern
•
63 Posts
0
October 8th, 2009 03:00
A vFiler is a virtual Filer.
You can create multiple vFiler on a physical NetApp Filer. You use this to separate data into different domains, and to separate data (security) from each other.
I have not put a servers file on the Filer and vFiler, because there is no NetWorker installed (which is impossible).
I have put the IP-addresses and names into the hosts-files
TimTh
2 Intern
•
63 Posts
0
October 8th, 2009 05:00
What I think is wrong, is that the dump command (which is used, by the -T dump in the backup command) only exist on the physical filer, and not on the vFiler.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
October 8th, 2009 05:00
TimTh
2 Intern
•
63 Posts
0
October 8th, 2009 06:00
The -I parameter.
From what I understand in the man pages, does the -I parameter let you specify a different host to which the backup should belong, correct?
So I tried the following as a backup command for client instance of the physical filer:
nsrndmp_save -M -T dump -J storage_node -s backup_server -P backup_server -I vfiler
So, why did I do this:
This would let me be able to backup the data through the physical server, which works.
And this would put the backup as a backup for the vFiler.
Therefor the users of the vFiler, who can only see the vfiler in the networker user, only can see their data.
The backup ran successfully, but under the index of the vfiler is still get "No savesets for this client", and the backup is listed in the indexes of the physical filer.
I added *@vfiler in the remote access list of the physical filer
And also added *@vfiler in the operators groups (in the man pages it said they need operate networker privileges)
TimTh
2 Intern
•
63 Posts
0
October 9th, 2009 01:00
But the -c would.
But still, even with the backup command:
nsrndmp_save -M -T dump -c vfiler -J storage_node -s backup_server -P backup_server
The backup still shows under the physical filer, and not the virtual filer.