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 l
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 T
