Hi,

I don't think it is crucial to import the same client, but you can do that of course. And yes, the next step would be to create the device and have it point to the existing store. You can select the store in the GUI after entering the correct hostname or IP for the StoreOnce device. That should give you access to the store, but the problem left is the store objects are not known on the DP side yet. For that you need to find a way to create slots based on the store object list and import those slots. You can try the scripts from the "old" post. Or if you're elevating a support case, support can help with a perl script too.

Koen

Thanks. I imported most of slots from StoreOnce but many of them ended with error. I suppose that in my StoreOnce is plenty of files where is no relation to database. Is there some way how to clean up StoreOnce from unused files ?

I'm so sorry for not replying earlier. I'm assuming this has been resolved now?! If not then I would recommend opening a support case so a support engineer can take a closer look. If you want more comments here then please be more specific on the errors you have seen and any subsequent troubleshooting steps.

I just found this thread after having a very similar problem: "Migrating" a File Jukebox and a StoreOnce instance to a new CM.

For the Jukebox, I simply added the files to the repository, then first scanned the slots, then imported them. Took some time with hight CPU load, but succeeded without a problem. Only disadvantage was that the media pool assignments got lost, and the media names did not match (it seems the name given when formatting is written to the media, but when changing the name later (specifically when having mass-formatted media) the name is only in the local database). So some extra work to do.

For StoreOnce I created the device and reused the Store, but I see no repository and no slots, so I found no way to "Scan" the media present.

Seems kind of pointless to be able to re-use a store when the media inside aren't found. I could understand if StoreOnce were the first release of a new product, but that's no longer the case.

See also serverfault.com/.../407952

Have you checked this? Assuming this a software store...

https://support.microfocus.com/kb/kmdoc.php?id=KM00622309

Regards

Juanjo

So hardware or software store, either way, as you are saying that you were re-using the store, it means it is either a hardware device OR you have already moved the store_root and reconfigured it on the new system with --force option to make sure the store content is being re-used again.

So I'm assuming you now have a store full of objects (can be listed with "omnib2dinfo -list_objects -b2ddevice libraryname") and a device on the DP side using this store, but from the IDB viewpoint this store i still empty. Is that indeed the situation you are in now? If so then you basically need to create a slot for each object on the store and import that slot. To understand the concept, please read: Support Tip: Import an object from a B2D store. If you have lots of objects to import like this then scripting may be needed. If you elevate a support case then support can assist you with this. Feel free to refer to this post.

Ulrich Windl 

I just wrote another Support Tip which hopefully clarifies things.

Support Tip: How to move a StoreOnceSoftware store root to another client or cell

The additional step of creating and importing slots as described in my earlier Support Tip will only be required if the store root move was done to an alternate DP cell. In that case the IDB does not have that information yet.

Thanks, your assumptions were correct: StoreOnce was on a separate machine that wasn't changed, so there was no need to copy any files. Actually I adjusted the script found in the other support article and I was able to "import the slots" to the IDB. From the on things went rather smoothly (a few media were empty (maybe expired meanwhile), and some were missing ("Cannot open device (Unknown internal error.)"))

At a moment I'm sunning a job that verifies all backup objects (out of paranoia); about 1TB done, still busy...

I'm not moving StoreOnce "pyhsically" to another machine in the same CM, but I'm logically moving the StoreOnce from an old CM to a new CM (name it export/import if you like) as the hardware has to be retired (so the article does not apply). Also during transition both CMs will be active and doing backups.