Unsolved
This post is more than 5 years old
2 Posts
0
948
July 25th, 2012 07:00
Indexes not aging after 7.6.3 upgrade.
I upgraded from 7.6.2 to 7.6.3 about 2 weeks ago.
I've noticed that the indexes are not aging off and
if you try to remove oldest cycle nothing happens.
Ideas?
Lois
No Events found!
DaveHenry1
121 Posts
0
July 25th, 2012 07:00
Lois,
Can you help us out a little bit and give us more context? Which product did you upgrade? Can you tell us a little more about the environment it's installed in?
Lois1
2 Posts
0
July 25th, 2012 08:00
I upgraded the following:
MC from EMC Networker 7.6.2 to 7.6.3 this is a Windows 2007 Server.
NW Server from EMC Networker 7.6.2 to 7.6.3 this is a Suse Linux 11 sp2
# uname -a
Linux ***nwst01 2.6.32.59-0.3-default #1 SMP 2012-04-27 11:14:44 +0200 x86_64 x86_64 x86_64 GNU/Linux
4 NW Storage Nodes from EMC Networker 7.6.2 to 7.6.3 this is a Suse Linux 11 sp2
(Same as NW Server)
Fairly large enviroment:
**dd880-1-85-1:/backup/***dd880-1
125385205248 123240489984 2144715264 99% /backup/***dd880-1
(123 TB of data stored)
***ndm3n:/cfi3/****lnwst01_nfs
929318400 747195936 182122464 81% /backup/nsr_indexes
(747 GB stored indexes)
Backing up all different favors of Unix & Windows including NDMP configurations.
Running a 7x24 environment.
DaveHenry1
121 Posts
0
July 25th, 2012 09:00
Lois,
I'm not a NetWorker expert, but they are several of them on the EMC Community Network.
Your best bet for getting the correct answer to this quickly would be to post your question, including all the details you listed above, in the NetWorker Support Forum.
-Dave
Mabro1
2 Intern
•
666 Posts
0
July 31st, 2012 06:00
Lois,
It looks like you also created this as a Private discussion. was this your intention? I am going to rey an move this post to the Networker Support Forum. If you have the ability ot uncheck this as a priviate discussion please do so. That way the Networker Support Community can see your question and respond.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
August 2nd, 2012 04:00
Funny enough, I have see some strange things like that with some C:\ save sets at one remote location where they run small server with mostly NFS based AFTDs. I confirmed I do not have issue with any dependent save sets and similar. I only see it for clients which do use DISASTER_RECOVERY save sets too, but I would need to double check. Atm, I deleted save sets I knew I do not need and staged what is left to tape so I will be able to see what is going after summer vacation. It would be fair to say that in my case issue would be there before 7.6SP3 as due to when save sets were supposed to expire that would be even before this small server was updated (so 7.6.SP2p6 would be the one to blame).