| |
 |
My site consists various application servers running mail, databases and webservers. Can TSM supports online consistent backups of these applications? |
|
|
| |
Yes. There are agents available for online consistent backups with TSM.
|
| |
|
If the entire site is down due to natural calamaity or fire accident, how
can i secure my data with TSM? |
|
|
| |
Data can secured from fire accident or natural calamity by sending the data offsite. TSM supports this. Retsoration time can be minimized by implementing Disaster Recovery Manager (DRM).
|
| |
|
Ours is a heterogeneous environment inlcludes AIX,Solaris and windows. There are various applications running on various servers. If there is a complete server crash including OS, can i get the server back to its original state without re-installing the OS with TSM |
|
|
| |
Yes, it is possible. There is a third party software BMR is available, works with TSM which serves the above mentioned problem.
|
| |
|
Initially when we install TSM server data transferred speed throughput considerably slow. |
|
|
| |
Change the TCPwindow Size to 64512 throughput of our Win95 & Win98 clients has been increased dramatically from 200 kB/s to 4-5 MB/s.
|
| |
|
Users were complaining abt. their PC is very slow after installing TSM client agent for TSM scheduled backup. |
|
|
| |
We have informed those users that it takes nominal account of memory, some systems user might have anticipate some sort of degradation while their backup is going on and we have informed their backup scheduled timings.
|
| |
|
The customer is having two RS6000 with tape drives on both machines. One tape drive was gone bad and was to be replaced. But in the mean time some user deleted some critical files which were backed up previous day. User forcing the system administrator to get back the data from the previous day’s tape. |
|
|
| |
As the tape drive is not working on the machine system administrator has to restore the files from the other machine. But by using restore command on the other machine some common files will be overwritten with the one in the tape which should be avoided.
We suggested the solution to remote execute the command as given below
#dd if=/dev/rmt0 | rsh {remote host, which have faulty tape drive} tar –xvf –
This will restore the tape to the target machine with the help of rsh command.
|
| |
|
User getting the message re-spawning too rapidly on terminals connected to AIX server
1). The problem happened because of a loose serial cable to a tty terminal. The error started in the following way
System spawns a getty and sends a login herald to terminal (tty0). Loose cable on that tty caused noise in the line which forced a new getty to be spawned. System keeps track of the total number of getty spawn on tty0 within 3 minutes and 45 seconds period. If this exceeds 5 then system display error on console and shutdown the port. This continues for 20 minutes and enable the port once again. If this continues again the system will shutdown the port until the next reboot |
|
|
| |
Checked the cable and replaced the faulty cable.
|
| |
|
A naïve administrator logged in the machine and accidentally given the command rm * in the root. |
|
|
| |
Executing the command rm * will remove all files from the current directory, so only a partial recovery can be done on that.
This command will delete the required links given below
bin -> /usr/bin
lib -> /usr/lib
u -> /home
unix -> /usr/lib/boot/unix_up (or unix_mp)
Procedure for the recovery is
1. boot the machine in maintenance mode
2. Choose access vg and start a shell before mounting the file systems
3. Run fsck on /dev/hd4
4. Mount the root over /mnt
5. And rebuild the missing links
cd /mnt
ln -s /usr/bin bin
ln -s /usr/lib/boot/unix_up unix OR ln -s /usr/lib/boot/unix_mp unix
ln -s /usr/lib lib
ln -s /home u
6. Umount /mnt
7. Execute sync
8. Reboot the machine
This procedure helps to reboot the machine in normal mode so logging in is possible. Depending what else was there in the root directory, files may have to be restored from backup tape
|
| |
|
An user complained that she cannot get the CDE graphical interface on AIX server after she typed the login and password from the initial CDE login screen. |
|
|
| |
|
| |
|
One day a System Administrator transferred a file from a Windows NT machine to an RS/6000 Workstation running AIX. After the transfer the systems administrator could not access the file in the AIX system, even though he was the root user. |
|
|
| |
Unknown to the Systems Administrator, a newly appointed fresh Systems Administrator, in an earlier shift was experimenting with the ftpd deamon on the RS/6000 Workstation. After his experimentations, he forgot to replace the setting to their original values. The changes done were:
In the file /etc/inetd.conf the new systems admin had modified the following (default) line
ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd
to the following:
ftp stream tcp6 nowait root /usr/sbin/ftpd -u 666 ftpd
The “-u” option to the ftpd sets the umask for the files created during the ftp transfer. Since it is an umask setting, the final permissions that will be set on the transferred file will be the complement of 666, which is 000 for a file! So no wonder the root user could not access the file. So the solution is to remove the “–u 666” entry from the /etc/inetd.conf file.
Moral:
(a) ALWAYS keep a backup of the configure files.
(b) Never fix something that works well!
|
| |
|
| |
1 2
Next
|
