Support advise that /Storage/history/segments and /Storage/history/dataobjects can be safely archived and reinitialised. I have done so with /Storage/history/segments ( taking care to keep its permissions) and had no problems.
The netbackup failure codes here were 84 and 27. The Puredisk GUI termination messages are somewhat misleading since they record job terminations requested by the client or watchdog after an hour of inactivity. It is necessry to check earlier events for a space error.
Hopefully Symantec people read this forum so I have a few thoughts. In a 3-partition PDDO installation, release 6.5, the sizing for /Storage and /Storage/databases looks wildly inaccurate. /Storage guideline is 5% of data, However, because the history area is never weeded it will grow indefinitely and always fill this. Furthermore the free space usage for /Storage is not documented . The datastore threshholds , say 10% and 5%, are irrelevant and completely superseded by a workarea reservation , formula
4 * crdb_objects_table_size + 6 * queue_metadata_size.
Thus the GUI space error message
Partition containing queue at /Storage/queue: 399.98 GiB, 212.24 GiB free (53.06%) of which 192.65 GiB is required as margin for temporary files (48.16%) (low space threshold exceeded).
Previous state: 399.98 GiB, 212.24 GiB free (53.06%) of which 192.65 GiB is required as margin for temporary files (48.16%) (warning threshold exceeded).
The Content Router has insufficient disk space to accept new data. No new data will be accepted until more disk space becomes available. Rerouting, data removal and/or garbage collection is needed urgently.
is incomprehensible. From observation of DF output in PDOS this margin for temporary files is harldy used and should be reduced or configurable..
The guidline for /Storage./databases in 10% of data. This looks far too much. We have an 8TB store on the CR and the /Storage/databases partition is only 11% occupied.
