DB2 Naming Standards - Similar to OFA
Since this is easier to elaborate on in an answer than in a comment.....

We tended to install our instances to /inst/&lt;instance-name&gt;. I leave the instance naming scheme up to you. If you make it too similar than technically you have introduced a security risk as the instance names are eaiser to guess.

Then you could so something like the following:

/inst/&lt;instance-name&gt;/bkp
/inst/&lt;instance-name&gt;/offline
/inst/&lt;instance-name&gt;/online
/inst/&lt;instance-name&gt;/data
/inst/&lt;instance-name&gt;/dbdir
/inst/&lt;instance-name&gt;/logs
/inst/&lt;instance-name&gt;/archlogs


You can work with your server admins or your SAN admins or do the work yourself to decide which of these mounts is physically separate disk, LUNs, etc.

This is just something we did. We did it to provide separation of concerns of where the instance was installed, vs where the system tables vs the data tables, vs the logs, vs the archive logs, vs the backups. Whether or not it works for your organization, you will have to discuss.

Whatever you do, be consistent as much as is possible.