This has been done with a NW 8.2.0.0 server/SN on a DD880 running DDOS 5.5.0.4 (as mentioned).
Command was "nsrclone -m -b -S ssid/cloneid"
As we do not have a remote SN in this environment, i could not make any mistake by specifying the wrong source and/or dest. storage node. Network traffic is 0.
I assume that your sources reside on another clone media.
If so, do not forget to specify the ssid along with the cloneid (ssid/cloneid) - otherwise you will end up with only one instance.
For the speed, I am afraid that nobody can help you as we do not know your environment like device/media types and whether you stage locally (on one storage node) or remotely (if the data has to travel between different nodes).
However, you could split your save set file and run multiple save set commands at the same time. It would be great ifyou clone from multiple media at the same time.
Of course, the reason could also be a software bug.
Hi it is a dd860 the volume fsoff.001 resides on this dd860 and i want to stage it to the volume fsclone alos on the dd860.
The reason for staging is i want to do away with the fsoff which is a pool that was used in the past and no longer is functioning.
I was hoping that as this was all on the same ddomain it would be fast we have sata drives in the archive where this volume resides due to it all being old data.
bingo.1
1 Rookie
•
2430 Posts
489
0
Posted August 14th, 2014 02:00
Look at this example ...
This has been done with a NW 8.2.0.0 server/SN on a DD880 running DDOS 5.5.0.4 (as mentioned).
Command was "nsrclone -m -b -S ssid/cloneid"
As we do not have a remote SN in this environment, i could not make any mistake by specifying the wrong source and/or dest. storage node. Network traffic is 0.