- This topic has 7 replies, 6 voices, and was last updated 18 years, 1 month ago by .
-
Topic
-
Ofter when working with smat files I find it neccessary to keep more then one copy. In production I find it neccessary to keep 90 days worth of smat files. I have written scripts to cycle them every night. But in test it is not a set thing. I tend to cycle them when testing and we have serveral people testing so they get over written.
What are other poeple doing to avoid this ?
Could we get Quovdax to add some netconfig paramater to say keep X copies of the smat files.
Viewing 6 reply threads
Viewing 6 reply threads
- The forum ‘Cloverleaf’ is closed to new topics and replies.