I was thinking about doing that but that would make the backup so much less efficient and slow...EV uses millions of tiny little files and backing those up through a UNC would probably be painfully slow. I guess I can try it and see how much worse it is.
There's got to be a way of doing this and still using NDMP though no?
The other way you could do is keep the NDMP client in a separate group. Once you at the end of you pre-script add a command to initiate the group containing this NDMP client. For saveset add a file with negligible size.
crazyrov
4 Operator
•
1.3K Posts
0
June 25th, 2014 04:00
Why not map the NAS share as an CIFS on the windows machine and take a backup. This way the control will be on the same client machine.
mradchenk0
3 Posts
0
June 25th, 2014 06:00
I was thinking about doing that but that would make the backup so much less efficient and slow...EV uses millions of tiny little files and backing those up through a UNC would probably be painfully slow. I guess I can try it and see how much worse it is.
There's got to be a way of doing this and still using NDMP though no?
crazyrov
4 Operator
•
1.3K Posts
0
June 25th, 2014 07:00
The other way you could do is keep the NDMP client in a separate group. Once you at the end of you pre-script add a command to initiate the group containing this NDMP client. For saveset add a file with negligible size.
coganb
736 Posts
0
June 25th, 2014 07:00
Hi,
Further to crazyrov's suggestion, you can use nsradmin to start the group from the client:
# cat nsradmin_start
. type : NSR group; name : Ender
update autostart : Start Now
# nsradmin -s vm-lego-121 -i nsradmin_start
Then check back regularly to see if it's finished and run your post-script when it is:
# cat nsradmin_check
. type : NSR Group; name : Ender
show status
p
# nsradmin -s vm-lego-121 -i nsradmin_check | grep status
status: running;
-Bobby