Unsolved
This post is more than 5 years old
5 Posts
0
1636
Index occupying 0 kb
Hello
My enviroment consists of 10 windows 2003 R2 servers which are all backed up.
Networker 7.4 sp5
My problem is that 3 of these clients have problems with their indexes occupying 0 kb even though the backup runs fine without any errors what so ever.
Under Media -> Index it just says 0 kb but each savesets have several cycles listed.
I ran a nsrls and it also says "0 records requiring 0kb"
When i run networker user to try a restore i get a error message saying that no data has been backed up.
/nsr/index shows 2 different folders for the clients in question. One with a regular host name and one folder with a FQDN.
I suspect that networker is confused here about which index it should use for these hosts. I havent worked here that long so im not sure if the former backup guy did something special with these hosts.
Any ideas for fixing this? Would it help deleting the client?
ble1
14.3K Posts
0
July 16th, 2010 04:00
Before you move on, check not to have duplicate clientids too in media database.
Since this is Windows, I assume something like mminfo -avot -r client,clientid will work (I know how to make kind of sort -u using PowerShell, but have no idea if you have that on the system - otherwise you will get long list which you will have sort out somehow differently).
Further, check on OS level what is the usage of this folders (hostname vs FQDN). Also, check for nested inde folders (FQDN\hostname or hostname\FQDN). If one of them is empty it could be easy as moving data and setting up index path in client resource.
Usually this sort of things is caused by DNS or fact that your primary name is not what is returned by name resolution mechanism.
Daniea3
123 Posts
0
July 16th, 2010 08:00
Hi,
I agree with Hrvoje. There could be an issue with client id or Networker is confused with the names. Run mminfo -avot -q client=client_name -r "client,clientid". Try with short name and FQDN and see if its listing the same client id for both the names. If the index backups are successful then for sure it is saved somewhere.
Arun
otern
5 Posts
0
July 19th, 2010 00:00
As you guys suspected there is indeed a clientID mismatch on those 3 servers i mentioned. Running the mminfo command for both shortname and FQDN i found two different instances of clientIDs.
The clients in the configuration menu has both shortname and FQDN listed under aliases.
How should i proceede with this?
Daniea3
123 Posts
0
July 19th, 2010 03:00
Hi Otern,
You need to use any one of the client (Client ID) and need to merge the indexes. You can follow the KB article provided below to merge the indexes.
http://solutions.emc.com/emcsolutionview.asp?id=esg53017
Regards,
Arun