where the file path is the media database in networker?

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.

Hi bingo,

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 ).

Hello Hrvoje,

i just follow these major arguments:

  - Novices/beginners do not know about the sizing and the growth of the NW data. They just use the default proposal.

  - EMC also does not know about this fact - but instead of leaving the default pathname empty and make the admin think,

    they just use what must be available - the system drive.

  - You can not easily expand the system volume if NW needs to remain active.

  - If installed on any non-system volume, a problem on the system volume will never affect the application data.

  - If not separated, a problem with the application could easily end up creating a Windows problem.

    I agree that the disk capacities today are usually big enough. On the other hand I just had situations where the NW log

    files dramatically increased to some GB within minutes. And I currently have a similar situation with gstd.raw, which grew

    to about 200 GB over 2 days.

    The bad thing is: the servers today can easily handle that - and if you do not watch your disk space carefully, you will

    not even become aware of such a 'runaway' situation ... until your system disk has filled up.

Finally, there must be a reason why the system volume on a UNIX/Linux system is kept rather small by default.

Hi bingo,

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.

Hi bingo.

If there is a disaster, I must take backup of these files?

Networker that files should be backed up weekly?

Regards.

Fernando Huaman

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.