Ah ok... so I assume this is similar to vdm as in Celerra. Usually, you define vfiler in that case and from master console you define user you would use. That should work. Can you check if you do telnet vfiler_IP 10000 if that works? If that does not work you can't have NW communicating with vfiler for the same reason.
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?
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
Yeah, a telnet to port 10000 works both to the physical filer and to the vfiler. So that should be OK.
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.
If that's the case that might indicate you can't do backup of vfiler which I doubt. Can you check if you have tar? I believe you can use either dump or tar (at least with Celerra, but I suspect very much the same to be with NetApp).
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)
ble1
4 Operator
•
14.4K Posts
0
October 8th, 2009 03:00
ble1
4 Operator
•
14.4K Posts
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
1 Rookie
•
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
1 Rookie
•
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
4 Operator
•
14.4K Posts
0
October 8th, 2009 05:00
TimTh
1 Rookie
•
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
1 Rookie
•
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.