Search results for query: *

I don't really understand what you mean. NW has a bunch of built-in authentication and firewall mechanisms to check and protect data transfers. But if you ask whether NetWorker code will be protected against malware the answer would be: of course not. NW itself is not an 'anti-virus software'...

I am not a db expert. However, the information you need can be found in the appropriate NMDBA Admin Guide, available from the product specific download page. To receive the backup (NW: save set) indexes, you need to use the NW Admin GUI or the appropriate command directly. The general syntax is...

This is the general guideline: 1. You should not make your config more complicated than necessary. you better name the groups Daily Weekly Monthly But this is also confusing as each group will be started daily. May I suggest you simply name them after their start time...

The other method is to - search your resource file tree (..\nsr\res\nsrdb) for a resource file which contains the string - delete or rename the file - restart the services This will only not be the final solution if something would be taken from the media db.

It is important that you use the FQDN when you do that - the short name will indeed not find the entry. So the correct nsradmin command will be . type: nsr peer information; name: <fqdn_of_peer>

There is no issue running the commands at any time. These will help to 99,9%. If not, the server restart is the most appropriate solution. Missing entries in the recover window might point to the fact that there was no successful backup in the current backup cycle. Try to browse an earlier one...

Now the story makes sense - C: will not be backed up due to VSS errors. However, AFAIR this was already stated in the error messages with the NW 7 software. So it is worth to state all error message details next time. Repairing VSS errors on Windows 2008+ is pretty easy - simply follow this...

This could have a bunch of reasons - the most obvious will be that the drive will be excluded using a 'directive'. But let me ask first whether the backup attempt will be result in a backup error or is it just excluded? If there is no error reported, verify the behavior as follows: - Add a...

Actually I have no good idea how to solve that as 'administrator' is already listed by default. You might want to add '*@*' to the server's 'administrator' to verify whether this will help. However, I do not really recommend to permanently use this potential 'fix'.

I am pretty sure that renaming the client from serverold to servernew caused the problems. You are using the same clientid for both. You could have easily left the old configuration for recoveries and just use servernew for backups. Now you do not even have issues with the resource database but...

I hope I do - and if you look carefully you should recognize the issue yourself. I think that in your mminfo report I can recognize something like '*L5' for the volume name. In this case, "nf-backup.nativeflow.ent" is definitively not the device name. As the OS is Windows it should read...

- The output to a file makes sense - you can read text much better than from an image. - I just set the savetime parameter to ensure that the query even will show very old backups. - The save sets have passed their browse period. You see that because of the 'r' flag under 'sumflags' This...

Right now you do not know anything - it could also well be that your old backups just expired. And because the file index would have been deleted at this point in time, these index subdirectories do not exist any longer. So the first step would be to check which save sets still exist at all...

Actually there is no trick. The only way is to open the file in an editor and to find the keyword you are looking for. What version do you run, btw? Since a while (NW 7.3, AFAIR), the daemon.log file has been renamed to daemon.raw. It contains a lot of information but also a bunch of...

On Windows NW uses the 'system' account On UNIX/Linux NW uses the 'root' account This ensures that the sowftware has all rights to backup whatever is necessary.

Maybe the appropriate package (lgtoman) is not installed. From the NW 8.1 Command Line Reference, "save" command – e expiration Set the date (in nsr_getdate(3) format) when the saved data will expire. When a save set has an explicit expiration date, the save set remains both browsable and...

It is pretty easy to add the totalsize values using a (powershell) script, for example. This way you can easily create statistics for the whole list of clients over a certain period.

The issue is that the period specified by the relative policies must be converted to an absolute timestamp in the NW media index. The "save" manpage explains this pretty clear.

Unfortunately, you can not specify the size's unit - NW will use the 'best choice'. That's why i recommend that you list the size down to the byte and then covert the number in an Excel sheet. Assuming a weekly backup cycle, use mminfo like this: mminfo -q "level=full,savetime>-7days" -r...

I don't think so. However, once NMC is up, you can of course stop your browser as you don't need it any longer.