0 penilaian0% menganggap dokumen ini bermanfaat (0 suara)
63 tayangan1 halaman
A Solaris administrator's daily activities include monitoring server health by checking CPU usage, memory, processes, and disk space. They also perform performance monitoring, file system usage monitoring and maintenance, user administration, troubleshooting hardware and network issues, managing storage, patching servers, and ensuring backups are running successfully. Any server reboots or hardware failures require opening a change management ticket to track resolution.
A Solaris administrator's daily activities include monitoring server health by checking CPU usage, memory, processes, and disk space. They also perform performance monitoring, file system usage monitoring and maintenance, user administration, troubleshooting hardware and network issues, managing storage, patching servers, and ensuring backups are running successfully. Any server reboots or hardware failures require opening a change management ticket to track resolution.
A Solaris administrator's daily activities include monitoring server health by checking CPU usage, memory, processes, and disk space. They also perform performance monitoring, file system usage monitoring and maintenance, user administration, troubleshooting hardware and network issues, managing storage, patching servers, and ensuring backups are running successfully. Any server reboots or hardware failures require opening a change management ticket to track resolution.
1. Check the status of all the servers (Health check) @Cpu,Memory ,processes,services & diskspace 2.Performance monitoring cpu & swap memory 3.File system usage monitoring & extension 4.User credentials and logons maintenance 5.Troubleshooting like server crash ,reboots,hardware problems 6.Network problem on the server. 7.Managing & configuration of SVM & Maintaining SVM Filesystem. 8. Managing zones creation deletion extension etc. 9. Doing Patch Management to the server. 10. Noramly general request Extending the file system & creating new mount point user administration. 11. If incident happens like server rebooted by itself any harware component failed raise Change Management and Working with H/W vendor till close Change management. 12. Check the backup report (scheduled by crontab and ctrl-m) @ In my company Veritas netbackup 6.5 using for Backup @ Backup types will be BCV/Snap/Tape/D2D @ If any client backup fails i have to re-run if its hot backup @ otherwise inform the database or application team to re-run the bakup