Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
OnCommand Core 5.0 - perfdata directory setting problem!
2011-09-29
12:14 AM
10,235 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've upgraded the DFM 4.0.2 install to OnCommand Core 5.0.
The Upgrade did not keep the (non default) perfdata directory location and reseted it back to C:\Progr....
I've changed it to our location of F:\perfdata, stopped and started the server process and it was OK.
Now I've found that after a server reboot it is back to C:\Progra....
Any idea how to make this permanent?
Peter
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
The bug mentioned is similar but not the same a new bug is raised for this issue and your case is attached to it. Bug id 560602.
Regards
adai
20 REPLIES 20
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>>I've changed it to our location of F:\perfdata
[In case you have not used 'dfm options set perfArchiveDir="F:\perfdata", then you can use this. If this still doesnot resolve issue, you can try '
dfm datastore setup (with -p perfArchiveDir option)' again].
If there is a open BURT for this issue, i will let you know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've used "dfm options set perfArchiveDir="F:\perfdata"...
Just tried the other command and it is still the same, reset back to C:\Program... after the reboot.
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any more ideas? Please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey there
The server had to be rebooted again (hotfixes) and the setting was back to C:.....
Any news on a fix for this?
Thanks,
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My workaround after every server reboot…..
dfm datastore setup -n -p D:\NetApp\DataFabricManager\perfdata
H:\>dfm backup diag
Sybase Data Directory: D:\NetApp\DataFabricManager\data/
Sybase Log Directory : D:\NetApp\DataFabricManager\data/
Performance Data Directory: C:/Program Files/NetApp/DataFabric Manager/DFM/perfdata
Script-plugins Directory: D:\NetApp\DataFabricManager\script-plugins
Reports Archive Directory: D:\NetApp\DataFabricManager\reports\
Plugins Directory: D:\NetApp\DataFabricManager\plugins
Database Hosting System: localhost
SnapDrive Installed: Yes
SnapDrive Version: 6.3.1.5028
SnapDrive Status: Passed(Data not present on LUN)
Volume Snapshot Status: NA
Backup Destination: D:\NetApp\DataFabricManager\data\
Number of backups possible: 80
Backup Retention Count: 10
Allowed Backup Type: Archive (ndb)
H:\>dfm datastore setup -n -p D:\NetApp\DataFabricManager\perfdata
Stopping all services and jobs...
Starting sql service...
Changed perfArchiveDir to D:\NetApp\DataFabricManager\perfdata.
No database upgrade is necessary.
Updating database cache triggers.
Redefining SQL Views ...
Defining SQL debug procedures ...
Defining metadata accessors ...
Starting services...
Completed data setup.
H:\>dfm backup diag
Sybase Data Directory: D:\NetApp\DataFabricManager\data/
Sybase Log Directory : D:\NetApp\DataFabricManager\data/
Performance Data Directory: D:\NetApp\DataFabricManager\perfdata
Script-plugins Directory: D:\NetApp\DataFabricManager\script-plugins
Reports Archive Directory: D:\NetApp\DataFabricManager\reports\
Plugins Directory: D:\NetApp\DataFabricManager\plugins
Database Hosting System: usgrprena001
Database Location: /vol/usgr_iscsi_prevs721_dfm/data/lun_d
SnapDrive Installed: Yes
SnapDrive Version: 6.3.1.5028
SnapDrive Status: Passed
Volume Snapshot Status: Disabled
Backup Retention Count: 10
Allowed Backup Types: Snapshot (sndb), Archive (ndb)
Database Mirror Status: Disabled
Mirror location:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
Please open up support cases for this. I believe this is BURT498695 and has no single support case attached to it.
If they have no support cases, it's obviously no problem and does not need fixing. I believe otherwise.
Thanks
Christoph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Case (2002771192) is created, lets see how many months it will take to get a reaction from Support/Engineering ...
This is especially annoying, seeing that it was solved in some branch of the code. And then they used another branch to plant the "OnCommand GUI" on top of DFM and re-introduce the issue.
BTW, this BURT is not public accessible and does not match the problem, according to netapp support...
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
The bug mentioned is similar but not the same a new bug is raised for this issue and your case is attached to it. Bug id 560602.
Regards
adai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hmmm...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
impressing...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like the BURT is not public yet. My internal view looks a little different.
regards, Niels
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Niels
there are way too many burts "internal only" these days, I remember the other days just too well.
There is NO real reason to keep such a burt internal only, correct?
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Peter,
I'm not a BURT expert so I don't know all the gory details, but AFAIK for a BURT to appear as public somebody has to look at it and at least provide a description. Looks like this BURT is not as far along the process.
The good thing though - the BURT is there and cannot be ignored. It has to be processed at some point 😉
regards, Niels
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have added a request to the burt to make it public.
- Rick -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
Would this burt perhaps be related to my problem as well? My OnCommand 5 DB backups (snapshot backups)
began failing. In trouble shooting it with an archive backup type , DFM seems to believe my perfdata is located on my D drive where I didn't even have a folder for at the path listed. I can clearly see that it is writing the data on my E still, which is where it should be so that my snapshots work. I restarted the whole server a week ago. How is a service restart going to differ in fixing the problem as opposed to a reboot?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I finally was able to restart my dfm services per the list BURT and now my perfdata path points back to the correct location and I can once again take snapshot backups of my OnCommand DB. Any ideas when this BURT will be fixed?
Thanks
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Michael,
This is being targeted for the GA release of 5.0.1. BTW can you add your case to this burt or share your case # for the same?
Regards
adai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the information. That is good to know. I have not opened a case yet, but I’ll go open one up and have it attached to the BURT.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Adai
Any ETA for 5.0.1?
And will you level the version numbers also for Management Console?
Just makes it unneccessary complicated with OnCommand5, Mgmt-Console3.1 and ProtMgr4 and so on...
thanks, peter