SMD Diagnostics Agent Backup Strategy?

Posting this question here as well as the Solution Manager forum since we're running SAP on the iSeries.
My organization has just started deploying SMD agents across our SAP landscape and we're considering how this new component (the agent) fits in our backup strategy. Should the agents even be included in our periods backups? They're small, easy to reinstall if necessary, and don't store any data, but would have to be re-registered. Any other backup consideration? We're interested in how other organizations have dealt with this question, thanks for your input!
Robert Garst
Perrigo SAP Basis Team

Hi Robert,
as you already supposed I wouldn't include SMD agents in the backup strategy since they are little and don't store data. What's important is the central Solution Manager System itself. There the data reported by SMD agents is used and stored.
Best regards,
Christoph

Similar Messages

Diagnostics Agent 711 - SAP Host Agent - Installation on a cluster environm

Dear all,
We have the following architecture in our productive environment :
1. Cluster 01 is composed of 2 nodes.
   On Cluster 01, only "Database" and "Central Services" are running
   for 5 productive SAP systems.
2. Cluster 02 is composed of 6 nodes.
   On Cluster 02, only "Central Instance" and "Application Server"
   are running for 5 productive SAP systems
As read in "Diagnostics Agents installation Strategy", rules #4, slide 12 :
===================================================================
- Do not install a Diagnostics Agent on host that only run Database
or SAP Central Services.
- Install a Agent on EACH host running a Central Instance (CI)
and / or a Dialog Instance
===================================================================
For our productive environment, we do have to install Diagnostics Agents 7.11 on cluster 02 where we have CI + AS running.
Questions :
1. How do we monitor "database" and "central services" data on cluster 01 (DB + CS) as far as no "Diagnostics Agents"
   are installed ?
2. Do we have to install the new "SAP HOST AGENT" in our cluster 01 ?
3. As written in "Downloading and Installing Package SAPHOSTAGENT"
   guide, "you only need to install the host agent host taht not have
   an SAP Component". Does it mean that the new "SAP HOST AGENT"
   will have to be installed on our cluster 01 to monitor "DB+CS" data ?
4. What are for SAP a host that not have SAP Component ... ?
    "Database" and "Central Service" running for a SAP system should be consider as SAP Component or not ... ?
5. What is the difference between the new "SAP HOST AGENT" delivered by SAP today 23.11.2009
    and the "Wily Host-Level Introscope Agent"
   delivered by CA ?
Best regards
PC

Yes, it has to be installed.

SMD Agent 7.00 or Diagnostics Agent 7.11

Hello,
Our managed systems are running on NetWeaver 7.00.
We are currently implementing SAP Solution Manager Diagnostics using SOLMAN_SETUP guided procedure.
In https://service.sap.com/swdc -
Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" Entry by Component" Agents for managed
there are 2 kinds of Diagnostcis Agents :
1. SMD Agent 7.00
2. Diagnostics Agent 7.11
Question :
Can we install a Diagnostic Agent 7.11 on our managed systems running on NetWeaver 7.00 or must we install SMD Agent 7.00 ?
Are Diagnostics Agent 7.11 supported for managed systems running on NW 7.00 ?
Best regards
PC

Hi
To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release
that the SAP systems already installed on the host.
Refer the doc in this [link|https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000526434&_OBJECT=002007974700000409092009E&_SCENARIO=01100035870000000112&] Section 2.3 Managed system page no:8
Hope this helps you
regards
Naveen

Diagnostics Agent 7.11 vs SMD Agent 7.00

Hello,
In our SAP System environment, most of managed systems are running under SAP NW 7.0 platform.
We are currently installing SMD Agent 7.00. The installation is not finished and I was wondering if we can install Diagnostics Agent 7.11 on managed systems running on SAP NW 7.0 ?
In other terms :
SMD Agent 7.00 have to be installed only on SAP NW 7.00
Diagnostics Agents 7.11 have to be installed only on SAP NW 7.11 or also on SAP NW 7.00 ?
Thanks in advance for your feedback
Best regards
P. Cuennet

Yes you can install diagnostics agent 7.11 for a managed system 7.00
It's even possible for a managed system 6.40
Prerequisite is that your Solution Manager stack verison is 20 or higher (EHP1)
You can find the details in the installation guide for diagnostics agent 7.11 on SAP service marketplace:
[https://service.sap.com/diagnostics]

Diagnostics agent config: SMD user

Hello.
I have installed a diagnostics agent, but when I start the agent, it is not able to register in the server.
My question is, how can I check the user and password of Solution Manager that has been entered in the Agent installation (smd_admin, normally)? If this user/password was mistyped during installation, how can I change it afterwards?
I have found some file with info about user and password but it is encrypted.
Thanks for your help.
Fermín.

Hello.
I have installed a diagnostics agent, but when I start the agent, it is not able to register in the server.
My question is, how can I check the user and password of Solution Manager that has been entered in the Agent installation (smd_admin, normally)? If this user/password was mistyped during installation, how can I change it afterwards?
I have found some file with info about user and password but it is encrypted.
Thanks for your help.
Fermín.

Diagnostics Agent 7.11 on iSeries

I"ve gone and got the installation master DVD and the Kernel DVD but cannot find the standalone Diagnostics Agent. Following You can download Diagnostics Agent installation DVDs from SAP Service Marketplace at: http://service.sap.com/swdc Download SAP Support Packages Entry by Application Group SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.0 EHP1 Entry by Component Agents for Managed systems DIAGNOSTICS AGENT 7.11 <choose operating system of managed> gets me to the area but I'm not seeing it for our system.
Am I missing it or has it not been released for the iSeries yet? If not, then how is anyone else getting this installed if no agent is available?
Thanks.

Hi Ryan,
the Diagnostics Agent Installation based on SAP NetWeaver 7.1 EhP1 is supporter for OS400. Unfortunately, the standalone SMD only installation kit was not release for the OS400 platform and therefore is necessary to use the standalone option found in the SAP NetWeaver 7.1 EhP1 installation media. You can follow the 711_Diag_Agent_Setup_Guide.pdf file attached in SAP note 1234387 to find the right components needed for this install.
Best regards,
Luis Gonzalez

Managed System Configuration step Assign Diagnostics Agent

Dear Experts,
We've newly instaled solution manager system 7.0 Ehp1 via latest sp stack 25 on aix 6.1, we've completed initial and basic configuraiton successfully via solman_setup, and instaled wily introscpe on same host with solution manager system,
Now i am trying to managed system configuration for solution manager system via solman_setup step Assign Diagnostics Agent as demo link below
https://service.sap.com/~sapidb/011000358700001735062008E
I opend http://>SOLMANHOST>:<SOLMANPORT>/smd/go/ADMIN_AGENT
>> Agent Candidates Management
>> Connection Parameters
>> Custom SLD Parameters > Aply and the selected the SMD instance then trying to attached via password SMD_ADMIN
But agent registration is waiting, SMD_ADMIN user is creating when i execute intial configuration, after i change the intial password, password is correct, so why the agent state is waitng status, i also push sld Setting for all from SMD view tab,
I've also try to restart SMD agent, /usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log file after restart
Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       ===> Establishing connection to server 'ms://ccisolman:8101/P4
Oct 28, 2010 11:07:28 AM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
Oct 28, 2010 11:07:32 AM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is Thu Oct 28 23:07:32 EEST 2010
Best Regards

hi
pls chk again your sld parameters and check the correct user name, password entered in agent connection management under CUSTOM SLD(in agent candidates management)
jansi

Unicode Kernel Diagnostics Agent install on non_unicode kernel System.

We have some ECC 6.0 ABAP systems that do not have a unicode kernel. The diagnostics agent setup guide for Netweaver 7.0 says you should have a unicode kernel DVD for the diagnostics agent install. I was hesitant about using a unicode kernel for the SMD agent and a non-unicode kernel on the ECC 6.0 instance. I tried installing the agent with the non-unicode kernel DVD and got an error that would not let me continue. Anybody have experience with this?

Carl,
David is Right, SMD is itself an SAP Instance(to be considered a seperate system-SAP Note:1365123) with its own exe. So it shouldn't be a problem.
Regards,
Jagan

Diagnostics Agent Installation in MCOD enabled systems

Hi Experts,
We are connecting MCOD anabled managed systems to Solution Mamager 7.1 SPS10.
But little confused with Dagnostics agent strategy; whether Agent-On-the-fly feature can be used in this case or not?
I am following SAP Note 1365123 - Installation of Diagnostics Agents.
Our MCOD structure is as below:
All Development systems on one physical host
All Quality systems on one physical host and
no MCOD enabled for Productive systems.
Thanks in advance,
Rahul

Hi Alexander,
Thank you for the quick reply. Can you clarify below:
MCOD database host is having 3 DB instances (of development systems) and all the 3 instances are connecting to single solution Manager system.
Does each DB instance require seperate Diag. agent or single Diag. agent will work for all the 3 instance to connect with solution manager?
Thanks in advance,
Regards,
Rahul

Defining a backup strategy

Hello all,
I have to help someone to implement a backup strategy on a database.
Before defining the backup strategy I'm doing a document with some questions that the clients needs to answer, so I can recommend the most adequate backup strategy.
I will leave here the questions that I think are useful to ask. Please help me out with this by correcting or adding or discussing questions:
Questions to the client:
- What type of database do you have (data warehouse, transactional,...)?
- Whats the size of the database and what is the expected growth per month/ year ?
- How much information is inserted/updated into the database per day/month?
- What type of backups do you need? daily? weekly? ...
- What MTTR (mean time to recover/repair) do you need for the database?
- How will the backups be done? to the hard drive? to tape? ....
- Do you have a backup agent? If so, witch one do you have? Does the agent has its own scripts or do we need to create them ourself.
- Does the database works 24x7, or can it have any downtime for backup?
I really apreciate you help.

A good start point is the reading of Best Practices for Oracle Database 10g Backup and Recovery which discuss against three important questions :
• How quickly should recovery complete for a datafile, tablespace, and database?
• What is the tolerance for data loss?
• How far back should backups be kept to satisfy the data retention policy?
Nicolas.

Diagnostics agent not getting registered in Solution Manager

Hello SAP Experts,
I am using Solution Manager 7.1 SP Stack 12. I installed diagnostics agent on one of the managed systems and fired the command below for registering it in Solution manager (since I did not do this during diag agent installation):
/usr/sap/DAA/SMDA<instance no>/script/smdsetup.sh managingconf hostname:"sapms://<FQDN of Solman>" port:"81<instance no of Solman>" user:"smd_admin" pwd:"<password"
This command returned successful message. However, when I login to Solution manager and go to Agent administration, I am unable to see the above managed system diagnostics agent. Please help.
Thanks & Regards,
Kunal.

Hi Adi,
Thanks for the reply. I found the below SMDSystem.7.log at location /usr/sap/DAA/SMDA98/SMDAgent/log
Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main] ] Error Failed to connect to SMD server - user: smd_admin
Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main] ] Warning Connecting to SMD server ms://<hostname>/P4 failed - error counter: 1690 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: there are no access points for service: P4 registered on the message server]
Regards,
Kunal.

Diagnostics Agents upgrade

Hello,
We would like to upgrade our Diagnostics agents to 7.11 based on http://service.sap.com/diagnostics -> Diagnostics Agent Setup Guide information.
It seems that to upgrade the agents means desinstall/reinstall them all ?
Now the queston is: is there a easy way to check the Diagnotics agent version on o.s. level
We have Diagnostics agents installed under hp-ux filesystem:
/usr/sap/DAA/
/usr/sap/DAA/exe contains the (shared) kernel
Using Root Cause analysis -> Agent Administration , wa can see that all agents versions are 7.01.6.1.20100326060452
Thank you and best regards,
Cédric Decreton

Hello Cédric Decreton
Unfortunatelly you'll need uninstall the old agents
To execute a mass installation, check this note, it'll help you a lot to install the new version in all your landscape.
1294713 Mass Deployment of SAP Diagnostics Agent 7.11
Pay attention to two points
1) Using Root Cause analysis -> Agent Administration , wa can see that all agents versions are 7.01.6.1.20100326060452
This is not the version of Diagnostics agent, this is the version of component LM-SERVICE. How it works ?
When you install the Diagnostics Agent, you must execute the authentication with the Diagnostics Server using host, port, user and password parameters. When the authentication is successful, the Diagnostics Server will deploy lots of applications in the managed system where the Diagnostics agent is installed. The LM-SERVICE is the component that store these applications. For this reason is MANDATORY and VERY IMPORTANT always have the latest patch level of your LM-SERVICE. I strongly recommend the upgrade to Solution Manager SP24 that deliver LM-SERVICE 7.01.7.0. Pay attention that yesterday was released patch level 1 of LM-SERVICE 7.01.7, and it delivers 39 important corrections. If you want stay with 7.01.6, apply the latest patch level from here.
http://service.sap.com/patches => Support Packages and Patches - Entry by Application Group => SAP Technology Components => SAP SOLUTION MANAGER => SAP SOLUTION MANAGER 7.0 EHP 1 => Entry by Component => Solution Manager JAVA Stack => # SOLMANDIAG 7.01 => # OS independent => LMSERVICE06P_2-20004805.SCA Patch 2 for SOLMANDIAG 7.01 SP06
2)
Solution manager Diagnostics agent 7.0X => /usr/sap/DAA or SMD/JXX
Solution manager Diagnostics agent 7.11 => /usr/sap/DAA or SMD/SMDAXX
thanks and best regards

Long-term retention backup strategy for Oracle 10g

Hello,
I need design a Archivelog, Level 0 and Level 1 long-term retention backup strategy for Oracle 10g, It must be based in Rman with tapes.
¿Somebody could tell me what it's the best option to configure long-term retention backups in Oracle?, "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1825 DAYS;" It's posibble ?
Regards and thanks in advance

Hello;
RECOVERY WINDOW is an integer so yes its possible. Does it make sense?
Later My bad, this is Oracle 11 only ( the gavinsoorma link ) . Getting harder and harder to think about 10. Don't think I would use RECOVERY WINDOW.
I would let the tape backup system handle the retention of your rman backups.
Using crosscheck and delete expired commands you can keep the catalog current with the available backups on tape.
Oracle 10
Keeping a Long-Term Backup: Example
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmbackp.htm#i1006840
http://web.njit.edu/info/oracle/DOC/backup.102/b14191/advmaint005.htm
Oracle 11
If you want to keep 5 years worth of backups I might just use KEEP specific date using the UNTIL TIME clause :
keep until time 'sysdate+1825'More info :
RMAN KEEP FOREVER, KEEP UNTIL TIME and FORCE commands
http://gavinsoorma.com/2010/04/rman-keep-forever-keep-until-time-and-force-commands/
Best Regards
mseberg
Edited by: mseberg on Dec 4, 2012 7:20 AM

Need Advice on Backup strategy

Hi,
Database version:10.2.0.
Database Size:60GB.
Daily Updation Approximately :2GB.
I need some advice on my backup strategy.
My backup startegy:
Monthly Once, Date: 1 Full backup (Incremental level 0).
Daily Incremental level 2 backup from Date: 2 to 6.
Weekly Once Incremental leve 1 backup on Date:7.
Daily Incremental level 2 backup from Date:8 to 13.
Weekly Incremental level 1 backup on Date:14.
Daily Incremental level 2 backup from Date:15 to 21.
Weekly Incremental level 1 backup on Date:22.
Daily Incremental level 2 backup from Date:23 to 28.
Weekly Incremental level 1 backup on Date:29.
My system requirments are i have only 70GB disk to store the backups, i can store only the full backup in it.So what i am doing is, Am storing the full backup in my disk and am transfering the Incrmental level 1(weekly Once backup) to the Tape and deleting the Daily level 2 backups, after taking that weekly backup.
Is my strategy correct or should i do anything different plz give me some advice.
TIA,

This backup strategy doesn't look bad. However the 70G of free space will be a pain in the neck. I suggest you to increase storage. Have you considered archivelog too? This average 2G daily transaction rate will increase storage requirements, sooner or later, so backup storage requirements.
~ Madrid

Need help with backup strategy

So my 2 TB backup drive failed this morning. I'm using a Seagate drive in an OWC external enclosure. I plugged it in and the drive didn't pop-up on the desktop, nor is it visible in Disk Utility.
I know that all drives eventually fail, but it seems like I've had more than my fair share of problems lately. This is of course making me think hard about my backup strategy. Here's what I'm doing now - I'd appreciate your thoughts on how to make it even more "bulletproof".
> TimeMachine back-up of boot drive and media drive (with photos, documents, movies, etc.)
> External clone of boot drive and media drive (on two partitions) - this is the one that failed
I suppose I could add a third external clone for redundancy, but an offsite backup would probably be even better. Not quite sure what the best option is there, though. Any ideas?

I too love automation. However, an automated backup requires the backup drive to be always connected (and maybe powered) in order to perform the backup. Also, the computer you speak of must remain on (by the sounds of it) 24/7 in order to do a nightly back up at midnight.
First of all, it probably is not the best to leave your puter on 24/7. I won't go into all the OS reasons why. But here are 2 other reasons to think about:
1) Your internal HD will always be powered, bad on drives
2) You are constantly using power to run your system. Not good for your power bill or the greater environment
As for the always connected Backup HD- I only connect, and power on my backup when I go to do a backup. This leaves it disconnected in case of virus infection. And powered down/disconnected removes some of the risk of damage from power surges/spikes (yes I use a UPS, but these can/have failed)
So to sum up: I back up everyday. What I do is after I am done working in LR for the day I shut it down, and than start it back up (ugh) so that I can back up my Library with all the work I just did (wish Adobe would do a back up upon closing!!!)
Than I close down LR AGAIN..... Than I connect my Back up HD. Via usb, once connected it automatically powers up and fires up the back up software. All I do is hit start. Since this is an incremental back up it only takes a short while. I go use the "John" grab a drink, and come back unplug the Back up HD, and turn off the system for the day.

SMD Diagnostics Agent Backup Strategy?

Similar Messages

Maybe you are looking for