• Hmmm that's crappy. The two files are suppose to be addressed as one sequential topology, but evidently are not.

    Often times, with constrained customer SAN's containing multiple vendor databases, it can be problematic to grow volumes sufficiently to prevent disaster scenarios involving single log files. We actually configure failover volumes on slower disks (cheaper, used for archiving) to accommodate this issue on purpose, as most large data volume products do, as we have many databases in our topology, each one of which could experience problems from different failable backup strategies. Banking and Healthcare data doesn't care if you don't have a backup plan for backup or notification systems failures.

    So I'll set the secondary log file maximum growth size to some number that buys me a few hours of client throughput and yell at microsoft for not considering this issue (Oracle has no problem dealing with log files in this way).

    Thanks.