Sponsored Content
Full Discussion: Mksysb restoration
Operating Systems AIX Mksysb restoration Post 302979509 by bakunin on Monday 15th of August 2016 03:17:58 PM
Old 08-15-2016
Quote:
Originally Posted by AIXBlueCat
can we do an mksysb backup with other userid other than root ?
Consider this: to create a backup of something you need at least read access to it. A mksysb image is the complete rootvg, which includes the most sensitive information of the system (namely everthing in /etc/security and the like). Ask yourself: will any other user except root be allowed to do it?

The answer is: of course NOT! That should answer your other questions too.

You can do it from a user using a sudo-rule if you have sudo installed, but that means that this user runs some process effectively as root either.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

Can before and after snapshots be used to verify successful filesystem restoration?

Hello Guys, Can before and after snapshots be used to verify successful filesystem restoration? snapshots will be created using fssnaps and restoration is thru legato restore? Any ideas on this? or any other ways I could verify that restoration is good? Regards (0 Replies)
Discussion started by: MarkyBoy
0 Replies

2. Shell Programming and Scripting

Restoration issue

Dear All, I am using sun OS server and performing weekly backup on a tape DDS2 for log files for the past 7 days, the log file sizes are ranging between 1 - 2 G......When i want to restore a specific file from the tape, i have to restore the whole files from the tape by using the command (tar... (1 Reply)
Discussion started by: charbel
1 Replies

3. Solaris

restoration

i have 2 hardisk. Hardisk A and Hardisk B. i have backup the oracle folder from hardisk A to hardisk B c0t0d0s4/oracle. If i want to restore , what is the command and what do i need to do ? urgent help needed. Thanks for your quick reply . (1 Reply)
Discussion started by: Farbegas
1 Replies

4. UNIX for Dummies Questions & Answers

LTO multivolume restoration problem in SELS9

Can anybody help me ? ? Previously data was taken multi volume LTO Tape backup in Red hat Linux by following command : tar -cvf /dev/rmt/tps6d7v -b 1000 -M filenames , now i try to Restore it in SELS9 by following command : tar -xvf /dev/st1 -b 1000 -M filenames , it extracts only part of the... (0 Replies)
Discussion started by: pramanik
0 Replies

5. AIX

mksysb restoration steps

please provide me with the steps to restore from mksysb tape. i m using AIX 5.3 TL 7 (2 Replies)
Discussion started by: debasis9
2 Replies

6. AIX

mksysb restoration using NIM

Hi, I just want to ask whether anyone has experience on restoring mksysb backup in NIM. We have taken the mksysb backup and the SPOT has been configured on NIM also. I just want to know the checkpoints before doing this. Is there any checkpoints we need to do? Do we need to unmirrorvg? This... (12 Replies)
Discussion started by: depam
12 Replies

7. AIX

Data restoration

I am having the Lexmark/IBM 1/2” 3490E Tape Cartridge which contains old data which had taken up some years back. I want to know what kind of data is available and which backup product is used for backup the data and from which OS the data has been backup. It would be helpful for me if could... (3 Replies)
Discussion started by: kmvinay
3 Replies

8. Solaris

question about restoration from backup tape (solaris 10)

I am trying to restore opt on my server. my issue is, all the partitions are saved into the same back up tape. what is the exact command to just restore /opt for example, supposing c0t0d0s7 is the partition for /opt ---------- Post updated at 01:16 PM ---------- Previous update was at... (7 Replies)
Discussion started by: feg
7 Replies

9. Shell Programming and Scripting

MySQL Restoration Backup Script

Hi there, Alright I have this line that I'm working with (bash programming): mysql -u username -pHASH ${args} < /home/site/backups/site.${args}.sql I get this error on that line: ./restore.sh: line 51: syntax error near unexpected token `newline' ./restore.sh: line 51: `mysql -u... (5 Replies)
Discussion started by: Pandoula
5 Replies

10. Solaris

Error after systeme restoration

Rebooting with command: boot Boot device: /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a File and args: SunOS Release 5.10 Version Generic_147440-01 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. WARNING: system call missing from bind file... (8 Replies)
Discussion started by: andersonedouard
8 Replies
VISUDO(8)						       MAINTENANCE COMMANDS							 VISUDO(8)

NAME
visudo - edit the sudoers file SYNOPSIS
visudo [-chqsV] [-f sudoers] DESCRIPTION
visudo edits the sudoers file in a safe fashion, analogous to vipw(8). visudo locks the sudoers file against multiple simultaneous edits, provides basic sanity checks, and checks for parse errors. If the sudoers file is currently being edited you will receive a message to try again later. There is a hard-coded list of one or more editors that visudo will use set at compile-time that may be overridden via the editor sudoers Default variable. This list defaults to "/usr/bin/vi". Normally, visudo does not honor the VISUAL or EDITOR environment variables unless they contain an editor in the aforementioned editors list. However, if visudo is configured with the --with-env-editor option or the env_editor Default variable is set in sudoers, visudo will use any the editor defines by VISUAL or EDITOR. Note that this can be a security hole since it allows the user to execute any program they wish simply by setting VISUAL or EDITOR. visudo parses the sudoers file after the edit and will not save the changes if there is a syntax error. Upon finding an error, visudo will print a message stating the line number(s) where the error occurred and the user will receive the "What now?" prompt. At this point the user may enter "e" to re-edit the sudoers file, "x" to exit without saving the changes, or "Q" to quit and save changes. The "Q" option should be used with extreme care because if visudo believes there to be a parse error, so will sudo and no one will be able to sudo again until the error is fixed. If "e" is typed to edit the sudoers file after a parse error has been detected, the cursor will be placed on the line where the error occurred (if the editor supports this feature). OPTIONS
visudo accepts the following command line options: -c Enable check-only mode. The existing sudoers file will be checked for syntax errors, owner and mode. A message will be printed to the standard output describing the status of sudoers unless the -q option was specified. If the check completes successfully, visudo will exit with a value of 0. If an error is encountered, visudo will exit with a value of 1. -f sudoers Specify and alternate sudoers file location. With this option visudo will edit (or check) the sudoers file of your choice, instead of the default, /etc/sudoers. The lock file used is the specified sudoers file with ".tmp" appended to it. In check- only mode only, the argument to -f may be "-", indicating that sudoers will be read from the standard input. -h The -h (help) option causes visudo to print a short help message to the standard output and exit. -q Enable quiet mode. In this mode details about syntax errors are not printed. This option is only useful when combined with the -c option. -s Enable strict checking of the sudoers file. If an alias is used before it is defined, visudo will consider this a parse error. Note that it is not possible to differentiate between an alias and a host name or user name that consists solely of uppercase letters, digits, and the underscore ('_') character. -V The -V (version) option causes visudo to print its version number and exit. ENVIRONMENT
The following environment variables may be consulted depending on the value of the editor and env_editor sudoers variables: VISUAL Invoked by visudo as the editor to use EDITOR Used by visudo if VISUAL is not set FILES
/etc/sudoers List of who can run what /etc/sudoers.tmp Lock file for visudo DIAGNOSTICS
sudoers file busy, try again later. Someone else is currently editing the sudoers file. /etc/sudoers.tmp: Permission denied You didn't run visudo as root. Can't find you in the passwd database Your userid does not appear in the system passwd file. Warning: {User,Runas,Host,Cmnd}_Alias referenced but not defined Either you are trying to use an undeclare {User,Runas,Host,Cmnd}_Alias or you have a user or host name listed that consists solely of uppercase letters, digits, and the underscore ('_') character. In the latter case, you can ignore the warnings (sudo will not complain). In -s (strict) mode these are errors, not warnings. Warning: unused {User,Runas,Host,Cmnd}_Alias The specified {User,Runas,Host,Cmnd}_Alias was defined but never used. You may wish to comment out or remove the unused alias. In -s (strict) mode this is an error, not a warning. Warning: cycle in {User,Runas,Host,Cmnd}_Alias The specified {User,Runas,Host,Cmnd}_Alias includes a reference to itself, either directly or through an alias it includes. This is only a warning by default as sudo will ignore cycles when parsing the sudoers file. SEE ALSO
vi(1), sudoers(5), sudo(8), vipw(8) AUTHOR
Many people have worked on sudo over the years; this version of visudo was written by: Todd Miller See the CONTRIBUTORS file in the sudo distribution (http://www.sudo.ws/sudo/contributors.html) for a list of people who have contributed to sudo. CAVEATS
There is no easy way to prevent a user from gaining a root shell if the editor used by visudo allows shell escapes. BUGS
If you feel you have found a bug in visudo, please submit a bug report at http://www.sudo.ws/sudo/bugs/ SUPPORT
Limited free support is available via the sudo-users mailing list, see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or search the archives. DISCLAIMER
visudo is provided ``AS IS'' and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. See the LICENSE file distributed with sudo or http://www.sudo.ws/sudo/license.html for complete details. 1.8.5 March 14, 2012 VISUDO(8)
All times are GMT -4. The time now is 03:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy