This entirely depends on baseline. For example, we use standard system baseline which includes system tools like backup (NetWorker) and this uses C drive. Application (including database) which uses the box (owns it in other words), has its own D drive (along with any other non system based app) and they might use some other drives depending on role and scope. Some folks (minority from what I have seen), use C drive just for basic install and everything else ends up elsewhere. Majority doesn't have (yet) clear baseline, but they have enough space so they never or rarely end up in any trouble. I intend to keep using C drive for sure (this also helps against all those cases where issue is caused by bad coding when NW resides outside default installation path ).
Nowadays you can easily expand volumes in Windows or even change paths for NW afterwards. gstd (being NMC) was something that always had to live on separated and dedicated volume. You can't compare Windows and UNIX since they follow different approach and workings at so many levels - but even there is all comes to sysadmin and how it does distribution and baseline (meaning you can also end up with one major partition in some cases). So, it is all about baseline. Nothing wrong with your one, but I do not agree with with your words of "worst approach" as that is highly subjective.
By default the NW server will be backed up once a day.
As the media db, along with the resource db, is essential for NW it will be backed up automatically when the NW server will be backed up - at least once a day. The resulting save set is called the 'bootstrap'.
In the case of a disaster I hope that you already have a backup.
bingo.1
1 Rookie
•
2430 Posts
1392
0
Posted October 3rd, 2015 02:00
Outch - obviously another installation on the system drive. This is worst practice and you should change this asap.
The NW directory path starts with ...\nsr\...
The media db resides in ..\nsr\mm\
Be careful what you do here - the media db has the key information to all your save sets.