Isnin, 24 Januari 2011

SAP Administrator Daily Activities

1. Check that all the application servers are up:
sm51 SAP Servers
sm04/al08 Logon Users


2. Check that daily backup are executed without errors
db12 Backup logs: overview

3. SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.

4. Operating system Monitoring
st06

5. Extents monitoring
db02 Database monitoring--Check for max-extents reached

6. Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.

7. Check system log
sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events.

8. Review workload statistics
st03 Workload analysis of
sto2 tune summary instance


9. Look for any failed updates
sm13 update records

10. check for old locks
sm12 lock entry list

11. Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.

12. Review and resolve dumps
st22 ABAP Dump analysis

13. Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace

14. Archive backup
brarchive -f force -cds -c
Insert the archive backup tape

15. Review Win system logs for problem
-> Win system log- look 4 errors or failures
-> Win security log- failed logon 2 sap servers
-> Win Application log -look 4 errors or failures

Rabu, 19 Januari 2011

Remove Squid footer completely

Removing the version number from the footer is very easy.

In squid.conf enable
httpd_suppress_version_string

But what if you want to remove the whole message.
Generated Thu, 08 Jun 2000 06:58:30 GMT by proxy1.proxy.com (Squid/2.6.STABLE1)

There is no configuration available to remove it but you can always edit the source file for that and recompile it. Don't worry its very easy. Easy because its really easy.

Just follow the following steps:
Go to squid source. /usr/src/squid/src
Backup the existing file errorpage.c cp ./errorpage.c ./errorpage.c.bkp
Remove errorpage.o rm errorpage.o
Edit the file errorpage.c vim errorpage.c
{
ERR_SQUID_SIGNATURE,
"\n<\BR clear=\"all\">\n"
"<\HR noshade size=\"1px\">\n"
"
\n"
"Generated %T by %h (%s)\n"
"
\n"
"<\/BODY><\/HTML>\n"
}
Remove the line "Generated %T by %h (%s)\n"
Save and exit :wq
Reconfigure squid with old options ./configure .........
Make clean make clean
Make make
Make all make all
Make install make install
Stop squid /usr/local/squid/sbin/squid -k shutdown
Start squid /usr/local/squid/sbin

Isnin, 17 Januari 2011

Configuring a Standalone NtpServer

For the purposes of this exercise, we can think of the time service as being composed of two parts: The 'client piece' and the 'server piece'. The client piece is responsible for locating another time source and keeping the local clock synchronized. When the 'client piece' makes a request for a time sample, the sample that is returned will be used to improve the accuracy of the local clock, assuming that the sample passes all validation steps. The server is responsible for answering requests from other NTP clients. When another computer or device makes a request for a time sample, the 'server piece' will formulate a response based on the clock of the local computer, which is (hopefully) being made more accurate by the 'client piece'. The point here is to show that although the 'client piece' and the 'server piece' are encapsulated into the same service, they can be seen as two separate entires linked together by the clock on the local machine.

By default, the 'server piece' is turned off, but in some cases the w32time service may already be configured to act as a time source (having the 'server piece' turned on). Specifically, if the machine is acting as a domain controller, then the 'server piece' is already turned on. When a machine is promoted to a domain controller, part of the dcpromo process it to enable the 'server piece' time service. You can verify if the server is turned on by running the following command:

w32tm /query /configuration

Keep in mind that you will need to be elevated to run this command. When you execute this, you will get back a laundry list of configuration settings. We are specifically interested in the NtpServer section:

NtpServer (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)

The third line will specify whether or not the NtpServer (aka the 'server piece') is turned on. If Enabled is 1, then it's on. If you see that Enabled is 0, then it is off. If you aren't running Vista or Server 2008, you can query the registry directly:

reg query HKLM\system\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer

You should see an entry that looks something like the following:

Enabled REG_DWORD 0x1

As before, 1 is on, 0 is off. You can turn on the NtpServer at any time by running the following commands:

reg add HKLM\system\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer /v Enabled /t REG_DWORD /d 0x1 /f

w32tm /config /update

The first command will change the Enabled flag in the registry to 1 (turning on the NtpServer), then the second command will tell the w32time service that the configuration in the registry need to be re-read, to make the changes active. You can confirm that the NtpServer is in fact running by calling w32time again:

w32tm /query /configuration

If you see enabled is 1, then you are good to go. If not, take a look at the registry using either regedit or the reg command to ensure that the change really made it into the registry.

As usual, If you have specific thoughts or questions about this post, please feel free to leave a comment. For general questions about w32time, especially if you have problems with your w32time setup, I encourage you to ask them on Directory Services section of the Microsoft Technet forums.

Configure a client computer for automatic domain time synchronization

Administrative Credentials

To perform this procedure, you must be a member of the Administrators group on the local computer. To perform this procedure from a remote computer, you must be a member of the Domain Admins group.

To configure a client computer for automatic domain time synchronization

  1. Open a Command Prompt.

  2. Type the following command and then press ENTER:

    w32tm /config /syncfromflags:domhier /update

  3. Type the following command and then press ENTER:

    net stop w32time

  4. Type the following command and then press ENTER:

    net start w32time

Khamis, 13 Januari 2011

Step by step installation of the Backup Exec Remote Agent for Linux and UNIX Servers (RALUS) on the Red Hat Linux

Problem


Step by step installation of the Backup Exec Remote Agent for Linux and UNIX Servers (RALUS) on the Red Hat Linux platform.

Solution


Follow these steps to install the Remote Agent for Linux and UNIX Servers on Red Hat Linux:

Note: RALUS is an additionally purchased option and is enabled by installing the RALUS serial numbers on the Backup Exec media server.
For Backup Exec 2010, there is no separate download available, RALUS is included on the DVD, and can be found in the "LinuxUnixMac" folder present at the root of the DVD for Backup Exec for 2010.


It is also advisable to check the RALUS compatibility with LINUX host before installation, To check the compatibility refer to:
http://support.veritas.com/rd/bews-compatibility.htm


To install the Remote Agent for Linux and UNIX Servers on the LINUX host:

1. On a LINUX host, download the installation files from the Symantec support site.

2. Connect to the target host using a terminal session or Log On locally with super user, root, or administrator privileges.

3. Extract the contents of the installation files that were downloaded in Step 1 using the following command Figure 1a below:

Note: Do not extract the RALUS installer files on a Windows system and copy the resulting files to the Linux/Unix host. Doing so will cause difficult to diagnose installation errors. It is important to copy the .gz file to the Linux/Unix host and extract the files there as shown below.

Note: This is a one step command to extract and untar the file.
tar zxvf filename.tar.gz
z = Gunzip(uncompress) it before extracting, used on file ending in .tar.gz or .tgz
x = Extract the contents of the TAR file
v = Verbose - display contents as it is tarring or extracting
f = Filename to follow
Note: If the file does not have ".gz" extension that means its already uncompressed and one has to just extract it using "tar xvf"command.

Figure 1a:


Or, in two commands as shown in Figure 1b below:

Figure 1b:




Note: This is a two step command to extract and untar the file.
gunzip filename.tar.gz
tar xvf filename.tar

4. Navigate to the Linux folder that was extracted in Step 3 as shown in Figure 2 below:

Figure 2:



5. At the command prompt, type: installralus and press as shown in Figure 3 below:
./installralus

Figure 3:


6. The installation screen appears: (Figure 4)

Figure 4:



Type the LINUX server IP address or Hostname and press Enter as shown in Figure above.

7. RALUS performs the initial system check as shown in Figure 5 below:

Figure 5


Press Enter to continue.

8. RALUS will check and install the following rpms on Linux server as shown in Figure 6 below:

Figure 6:


Press Enter to continue.

9. Installation requirement checks completed successfully as shown in Figure 7 below.

Figure 7:


10. To configure RALUS with user friendly configuration press "Y" (Figure 8)

Figure 8:


11. The installation utility will now ask a series of questions to configure RALUS (Figure 9)

Figure 9:


Press Enter to continue.

12. The installation utility will ask for the Media Server IP address or Hostname to display the remote agent as a selection in the media server's backup selection tree as shown in Figure 10 below.

Note: A host name can be used, however make sure that the Linux server can resolve the host name properly. Its recommended to add the Windows host entry in the /etc/hosts file on the Linux server.

Figure 10:


13. To display the remote agent on more than one media server choose "Y" and press Enter or Simply type "N" and press Enter to continue as shown. (Figure 11)

Figure 11:


14. Confirm the Media Server IP address or Hostname by typing "Y" and press Enter, else press "N" and re-type the IP or Hostname as shown. (Figure 12)

Figure 12:


15. The installation utility will now ask to create "beoper" group as shown. (Figure 13)

Figure 13:



Note: beoper is a group that is used by Remote Agent for Linux and Unix Servers to authenticate the Backup Exec logon account, as the members of this group are given permissions to back up and restore the Linux server.


Press Enter to continue.

16. If the beoper group is not found, the installation utility will ask to create one. (Figure 14)

Figure 14:



Type "Y" and press Enter.


17. Installation utility will now prompt to specify any specific Group ID. (Figure 15)

Figure 15:



Group ID: All Linux users have a user ID and a group ID and a unique numerical identification number called a userid (UID) and a groupid (GID) respectively. Groups can be assigned to logically tie users together for a common security, privilege and access purpose. Its recommended not to assign any Group ID.


Type "N" and press Enter.


18. Note the "beoper" group has been created successfully as shown. (Figure 16)

Figure 16:


19. Installation utility will now ask to add the user root to the beoper group (Figure 17)

Figure 17:


Type "Y" and press Enter.

User root has been successfully added to the beoper group.

20. Installation utility shows successful installation of RALUS. (Figure 18)

Read the information and press Enter.

Figure 18:


21. The RALUS configuration has also completed successfully as shown. (Figure 19)

Figure 19:


Read the information and press Enter.

22. Finally, Symantec Backup Exec Remote Agent for Linux and Unix Server has completely successfully. (Figure 20)

Figure 20:



23. Reboot the server.

24. Go to the Backup Exec media server and check the remote selections listed on the Backup tab. Expand the Unix icon: (Figure 21)

Figure 21:



Utility Commands:

Use the following commands to stop and start the RALUS service as shown: (Figure 22)
To Stop: /etc/init.d/VRTSralus.init stop
To Start: /etc/init.d/VRTSralus.init start


Figure 22:


RALUS configuration file.

The ralus.cfg file can be edited for either troubleshooting or configuration purposes as shown.

The file is located in the following location: /etc/VRTSralus/ralus.cfg
Config file details:
SOFTWARE\VERITAS\Backup Exec\Agent Browser\TcpIp\AdvertisementPort=6101 Advertising port
Software\VERITAS\Backup Exec\Engine\Agents\Advertising Interval Minutes=60 To change time interval
Software\VERITAS\Backup Exec\Engine\Agents\Agent Directory List 1=10.0.0.2 To add media server(s)
Software\VERITAS\Backup Exec\Engine\Logging\RANT NDMP Debug Level=0 To debug set the value to 1
Software\VERITAS\Backup Exec\Engine\RALUS\Encoder=
Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude1=/dev/*.*
Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude2=/proc/*.*
Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude3=/mnt/nss/pools/
Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude4=/mnt/nss/.pools/
Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude5=/sys/*.*