The clone_activate operation is not a valid operation on this operating sys

All of this information is intersting, however, it is unrelated to my problem. Does anyone have any suggestions for me?

Thanks

Don't even get me started on that. We are still backing up to tape, and the time windows are enormous. We are talking about switching to B2D2T to reduce the primary backup windows, bat that is going to require a few more arrays. {GAHHHHHHHHHHHHH}

Out of curiosity are you considering dedup and/or DLs with tape hanging off that

I heard that one as well.

When we were moving our DMX3 from the dock to it's "final resting place" on our Data Center floor we had to have the engineers reinforce floor tiles all the way along, as well as the ramp up to the Data Center. Even still the ramp was sagging... which makes it even harder to get the beast to the top without a really good run on

Yes, we are looking seriously at the D3D solution, but no decision have been made yet. And whatever we do for the disk piece of it will still have tape behind it to get a copy off site for long term retention.

Sarah,

if you run fdisk -l ..you do not see native Linux devices ? If they are in powermt display dev=all ...they have to be there.

The ramp sagged with us as well.
About 2 and a half years ago we got the DMX3's in and the ramp had to be repaired afterwards

I see devices, just not the 3 luns that I'm looking for.

Sarah ..i am sorry for so many questions but i am might be missing some configuration details. So you have source LUNs presented to RH box, now you are trying to clone these LUNs, are the target LUNs presented to the same host as well ?

Thanks

How about...

1. Unload the HBA driver module. Type modprobe -r module_name, where module_name is qla2300, lpfc or another value, depending on the HBA used.
2. Reload the HBA driver module. Type modprobe module_name, where module_name is qla2300, lpfc or another value, depending on the HBA used.
3. Re-examine the contents of /proc/scsi/scsi to verify the host can see its storage devices: cat /proc/scsi/scsi

Ok, I've updated to FLARE 26. The luns are visible from the o/s, admsnap, and powermt, however, I am still receiving the same error. Has anyone experienced this before? I'm not getting any help from my SR either. I'm not sure where to go for additional assistance.

Thanks for your suggestions so far.

I finally was able to speak to someone in Mass. He provided the latest version of the Snapview CLI Reference.

"Linux: The clone_activate command is not supported. You must either reboot the server or unload and load the HBA driver."

The clone_activate command is not required for Linux. Once the LUN is administratively fractured, and consistent, all I need to do is mount the LUN on the target host.

Thank you all for your input.

So your first post to this forum is to flame someone?

Nice Threadjack.