It should be one of two solutions, make a copy to a copypool or (highly
discouraged) set the deduprequiresbackup option to no.
In my book, the risk of mass data loss is too high in a dedupe storage
pool without a copy. In a non-dedupe pool, if you lost a volume and
didn't have a copy, you might lose data for a few nodes, but it's fairly
contained. In a dedupe pool, you could lose a volume that had a common
block for many, many files. The scale of the data loss could be huge.
-Kevin
On 4/11/2014 6:07, Stefan Folkerts wrote:
I am willing to be you don't have this option set to no in your dsmserv.opt
file and have a copypool that isn't 100% in sync with your primary filepool.
https://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.srv.ref.doc%2Fr_opt_server_deduprequiresbackup.html
On Thu, Apr 10, 2014 at 6:11 PM, Dhammika Rathnayake1
<dhrat...@lk.ibm.com>wrote:
Hi,
When I run the migrate command I am getting below massage.
ANR1534I Process 1067 skipped 28406 deduplicated files on
volume /diskpool/daily/000004DA.BFS because copies of the files were not
found. (SESSION: 49470, PROCESS: 1067)
Any idea?
