IFS Cloud - Transfer Documents vs Cloud File Storage Migration Tool

How many documents do you have per doc class?

I recently moved 30k documents in one doc class with transfer doc function.

You should always test in uat.

After move to file storage it is no longer enough to just do a database copy to get everything to uat/cfg. You also need to request a file storage clone (create a normal issue/case for this)

*BEFORE* doing any File Storage activities, please double check that your IFSAPP user is connected to an actual Person (e.g. IFSAPP and not ‘ * ‘ ). The File Storage flows do not work with * and there’s no automatic check for this.

R&D recommends doing the move with the Transfer Documents wizard in batches of about 5000 files at a time. However, we do have customers who have moved over 100,000 files successfully in a single initiation. Your mileage may vary.

Please note that the space is not reclaimed automatically when you move the files, it needs the tablespace to be rebuilt manually under a downtime after the move.

Alternatively, the fsmigtool may be used - it does not require IFS as such, any customer user with access to both the source DB and the Cloud installation can do it. IFS personnel such as me can be employed to help with that of course where required, guidance can also be given under Success.
The benefit of fsmigtool is that the files don’t need to fit into the managed cloud allowance in the first place, and there’s no downtime as the files were never in the Cloud DB.
You do however get to change the pointers for example with a migration job to get everything working.

Hi,

I have done this for a customer for one document class at time with 175,000 records and it took close to 3 days.

whether document transfer or file migration  is used depends on how much data you have currently.

its best to do this during upgrade phase anyway instead doing it after go live.

Best Regards,
Wasana

Oh, the test envs. So how File Storage works is it separates the documents (and media if you choose so) from the database.

That is, it’s not a must to do anything for the test envs, but then when you clone PROD to UAT,CFG the target envs will not have any files residing in File Storage (as only PROD can access those).
Maybe that’s fine if you don’t need files in test - that’s how it was originally thought.
If you however do need files in test, in addition to the clone ticket you’ll have to make a second ticket asking File Storage to be cloned as well.

If you are not cloning it is of course possible to do test envs separately as required but I guess cloning from PROD is usually the most common scenario.

Is File Storage clone, manual or part of the automated process??

As far as I know, its not yet in the automated process and you need to request it separately if need.

BR,
Wasana

Correct. There are thoughts of making it automatic, but there’s no delivery date.

Currently you can only get File Storage cloned (or cleared) if you request it with a separate ticket.

Thank you all for your responses!  I really appreciate the feedback.  The customer is using IFS Cloud Services, and they are assisting the customer for this effort.