This work is licensed under a Creative Commons Attribution- NonCommercial 2.5 License.
Restore data from a UFS snapshot and delete the UFS snapshot.
This is a misleading objective in some ways, although it makes an important point. A UFS snapshot is simply a temporary copy of a filesystem, a snapshot in time of a live filesystem. Read the rest of this entry »
Traditional UFS backup tools (like ufsdump) cannot do their job effectively with a busy, mounted, multiuser filesystem. The fssnap utility provides the capability to create a temporary copy (UFS snapshot) of an active, mounted filesystem which can then be backed up using ufsdump or other tools.
Backup a mounted file system by creating a UFS snapshot and performing a backup of the snapshot file.
Perform Solaris 10 OS file system restores using the appropriate commands, including restoring a regular file system, the /usr file system, the /(root) file system, and performing interactive and incremental restores for SPARC, x64, and x86 based systems.
Once you have a filesystem backed up with ufsdump, it doesn’t do much good unless you can get recovered again. Read the rest of this entry »
Given a scenario, develop a strategy for scheduled backups, and backup an unmounted file system using the appropriate commands.
Developing a backup strategy is a major undertaking and there are many schools of thought as to what’s right. Sun provides their spin Read the rest of this entry »
The usage of four command line utilities comprise this objective: ps, kill, at, and crontab. Piece of cake.
Control system processes by viewing the processes, clearing frozen processes, and scheduling automatic one-time and recurring execution of commands using the command line.
Getting printers happily working on a Solaris box in the real world can make root canals fun, but what you need to know about printing for the exam is pretty reasonable.
Configure and administer Solaris 10 OS print services, including client and server configuration, starting and stopping the LP print service, specifying a destination printer, and using the LP print service.
One of the coolest features of UNIX-type operating systems is the fine-grained ability to control access to files and directories based on owner, groups, and other users. Everything on a Solaris system is a file of some sort and every file is owned by one user and associated with one group. Given this, it is possible to achieve most any access control scheme imaginable.
Restrict access to data in files through the use of group membership, ownership, and special file permissions.
Securing computers that are connected in any way to other computers has become critical, which is to say vaulable. While Solaris is less vulnerable to many common attacks, there are still vulnerabilities that can bring tears to the staunchest sysadmin. This objective covers some basic, common sense approaches including stronger access services and limiting access to legitimate users.
Control system security through restricting ftp access and using /etc/hosts.equiv and $HOME/ .rhosts files, and SSH fundamentals.
The need for switching users goes beyond multiple personality disorders. The proper use of the root account prevents logging into a system as root. Instead, a non-privileged user account should be used for logins, then the user can switch to root.
Perform system security by switching users on a system, and by becoming root and monitoring su attempts.
Monitor system access by using appropriate commands.
System access can be monitored with several commands. The simplest is who which lists the currently logged in users. The variant command w provides the information contained in who plus what command each user is running. Read the rest of this entry »