Hi Gonzalo,  It is not possible to change the NDMP default storage pool for check points. The only solution is to go by [URL] That is to ensure the first check is created manually on the desired storage pool.Which will in turn use the selected storage for automatic NDMP check point.  There is no parameters to change the snapsure behaviour.  There is also no way to specify to use anaother storage pool when one pool is full.
The customer has a NX4 with 2 storage pools: one for SATA disks, and the other one for SAS disks. There is a huge filesystem (2.7TB) over the SATA disks, using all the available space from that storage pool, so there is no space left. There is around 400GB of free space in the SAS disks. The NDMP.snapsure parameter is set to 1. The backup server is running CA BrightStor ARC Serve (but the customer also tried with Veritas Backup Exec).  When we run an NDMP job to back up the filesystem over the SATA disks, it would fail saying that it can't create the snapsure filesystem. Taking into account this thread: [URL] , I manually created a checkpoint on the SAS disks storage pool. After that, we ran the NDMP job again, the automatic checkpoint was created on the SAS disks storage pool, and the backup went without problems.  It seems that when an NDMP job is run to back up a filesystem in a given storage pool, the NX4 tries to create the checkpoint in the same storage pool. If there isn't enough free space on that storage pool, the checkpoint creation fails, and the NDMP backup aborts.  The question is: is it possible to change the NDMP automatic checkpoint default storage pool? is there any way to tell NDMP to use another storage pool for the automatic checkpoint? Or maybe globally change the Snapsure storage pool behaviour, in order to try to pick up another storage pool if the default is full?  Thanks!!!   Gonzalo
Is it possible to change the NDMP Snapsure default storage pool for checkpoints?