OpsCenter 7.6.0.4 Report based on Retention Level
Hi, So I got this 5 pictures.Basicaly I want to create a report with no time bassis on retention level. I want it to show me Client Name, Policy name, Job protected size, Retention Level, Retention Period of the jobs only wiht a retention of >45 days. Simple right? see how I got retention level setted up in host properties(the interval, see picture 1) and add condition in the report. If the retention level is low than 45 days which in term of Opscenter mean Retention Level = interval(0,3) in my case (picture 1 + picture 2) with some simple columns like in picture 3 but I got no results. If I remove the condition Retention Level, and add time bassis like: 45 day before(picture 4+picture 5), I got data, but if I want to add Retention Level condition and play with it I get nothig, why? what i`ve done wrong? Any info you need to figure this out? And what the heck mens retention level -1, No retention? :))) expired? or can I set up a schedule without retention period? //George
Opscenter: Report to retrive old policy configuration
Hi, is it possible to pull out old policies information(Policy type, storage unit(what i need)) just to make comparison between the current configuration with the old configuration? i tried using the policy comparison function on the opscenter but it didnt show what i want which is the previous storage target. Please advise.
Saving Opscenter log to different disk
Opscenter version : 7.6.0.1 Hardware: WIN server 2008 R2 Question: Am trying to move/save opscenter logs to different disk on the same system using vxlogcfg.bat. But some how getting below errors. Please help: D:\Program Files\Symantec\OpsCenter\server\bin>vxlogcfg.bat -a -p 58330 -o 148 -s D:\Program Files\Symantec\OpsCenter\server\log V-1-8-5 An unknown argument Files\Symantec\OpsCenter\server\logs=E:\ was passed. Where E:\ is the new log directory am try to move to.
OpsCenter 7.6 Upgrade Purge Setting Changes - Important for Analytics Users - Please Read!
In OpsCenter 7.6, purge settings will change from 420 to 220 days. For fresh 7.6 installations, there should be no cause for concern. However, upgrades from previous versions of OpsCenter, could cause a large amount of historical job information to be purged from OpsCenter. Symantec NetBackup OpsCenter 7.6 Administrator's Guide PDF http://www.symantec.com/docs/DOC5042 pg. 254 Note: Before OpsCenter 7.6,the default data purge period for the backup jobs data was 420 days. In case of OpsCenter 7.6 upgrade, the default data purge period that is displayed for backup jobs data depends on what you had in the previous OpsCenter version. If you retained the default data purge period in the previous OpsCenter version (that is 420 days), in OpsCenter 7.6, it is set to 220 days. If you changed the default data purge period in the previous OpsCenter version, the same period is displayed in OpsCenter 7.6. For example: If you changed the default period in OpsCenter 7.5 from 420 to 500 days, in OpsCenter 7.6, it is set to 500 days In short, if you have never changed your default purge settings from 420 days (default) in OpsCenter 7.0, 7.1, or 7.5, and upgrade to 7.6, your default will become 220 days. When OpsCenter triggers its purge cycle, 200 days of historical information will be lost. Please Note: This is only for users that have never modified the default purge setting of 420 days, in previous releases.Where is my space? (Opscenter Reporting)
OK, so long story short the past week my 5220 appliance has been close to useless. While things hummed along nicely for the initial months (4), as expected space usage slowly began creeping up. First 60% and then 80%, but it sat in the 80's for a number of weeks, so it seemed this is where we would sort of plan to be. Well, no, within roughly 1-2 weeks, we went from this acceptable capacity to 100%. Yes, 100%, someone set highwater to 100% and in the end our appliance was cooked, Status 129 all the way, restores were not possible either, so we turned to support. After several days of cleaning things out, we managed to get to a point we could at least get the appliance online again. However, by no means did this mean we could use it. The appliance functioned as a media server, reading VM's, sending them to a data domain appliance and it seemed we were in the clear while we cleaned up more space on the 5220. But, as luck would have it, the DD also filled and we resorted to using advanced disk to stage data and then SLPs to send it to tape. Long story short, we are just getting by as things are made useful again and the only way to make the 5220 useful is to free up lots of space, so the plan is to get the largest systems off of it. I guess I would rather have several systems use the appliance and one write to tape as opposed to several to tape so that one can use the appliance. My goal is to get a report out of opscenter that tells me what is using all of my space. I expired image after image, but each time I did I did not gain any space. In talking with support this is normal with deduplicated data and the images as each can be really small. Therefore, I need to find the ones that are really big and get them off of there until we can manage to get more appliances to increase capacity. I hunted around in opscenter, but nothing appeared to be the report I am looking for. All I want is a list of sort that says, these 5 machines use 10TB while these 300+ use 50TB and then just show me what each system is using so I can dupe those to tape and expire the images off disk. Is such a report possible? Be it SQL or with the Wizard this report would help me in a huge way. ThanksOpscenter reports
We have a report configured in Opscenter that sends out everyday to report failed jobs. For the most part it works quite well, however, recently we began using NBU for vmware and not instead of a specific server being listed as a failure, all that is reported is the media server. Obviously this is not helpful as what we want to see is the individual VMs that might have failed for whatever reason. Is there any way to modify to report to display the individual VMs that failed backup or is this a short coming of the report and I must instead rely on the activity monitor to see specific servers? Thanks.
