This has worked fine up until the rebuild of the backup server, when I'm now getting the following error:
Code:
DUMP: write: bad file descriptor
DUMP: Write error 0 blocks into volume 1
Other commands work OK, such as tar, rcp, rsh, and so on. It's just the ufsdump that's suddenly failing!
I've looked at things like max num of files (OK) and permissions on the backup server's destination (OK), to no avail.....
I've even tried googling the error, but no-one seems to have come across this problem, or else they've not mentioned it online!
Can anyone help / suggest anything that might cause this? I'm assuming there's some issue between the ufsdump output and negotiations with the ubuntu server's filesystem, but I can't see what
Ok, I'm sure this is a total newbie question, but I think I'm in the right place, no?
I'm trying to call a perl module from a cgi script - Mail::Sendmail - and my web host installed the module in a directory that doesn't seem to be accessible, at least not the way I'm trying. But I thought you... (1 Reply)
at the end of October i upgraded the distro to 8.10 at first it seemed fine until i restarted my machine the boot seqence started i logged in after that nothing? tried booting again and the same thing happened did i do something wrong during the upgrade to 8.10 did everything the computer asked me... (1 Reply)
I have a real need to telnet into my new Ubuntu 8.10 server and have Googled my eyes out with ideas that don't work. I CAN telnet out of the server, but I CANNOT telnet into it (connection refused error). I have updated my resolv.conf file but its expert time. ANY IDEAS??? THANKS!!! I knew I was... (13 Replies)
Gurus,
I want log in locally to my Lucid (10.04) workstation and have my code saved over the network on my samba account
At work, all developers have samba user ids and when we were running Red Hat, we went thru the following procedure to get setup.
* open a shell session to NFS server... (2 Replies)
Hi All,
First of all thanks for reading this post.
In my application, I am trying to create a new message queue . I am attaching the code below.
mqd_t mqopen2(const char * pName,
unsigned long Flags,
long maxMsg,
long msgSz)
{... (15 Replies)
Hello, i have a solaris 11 sparc64 and Im trying to do a backup to tape. This is the display:
# ufsdump 0uf /dev/rmt/0cbn /dev/rdsk/c2t0d0s2
DUMP: Date of this level 0 dump: February 27, 2013 01:58:23 PM CET
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c2t0d0s2 to... (2 Replies)
Hi ,
One of my zone went down and when i booted it up i could see the pool in degraded state with some check sum errors . we have brought the pool online after scrubbing. But few files are showing this error
Bad exchange descriptor
Please let me know how to remove these files (2 Replies)
Anyone ever see an issue where ufsdump 'hangs' after the IV Pass?
Normally, it will update with an estimate of how long it will take to complete...and update the info every 20 minutes.
I'm running the following command:
root# ufsdump 0f - /fsmount | ( cd /zfs/newfsmount ) ; ufsrestore rf - )... (2 Replies)
I'm learning SED command. And while doing that i got to this place where i'm taking a copy of my existing file. The code i used is -
sed -n '/Storm/ w Storm.txt' books.txt
As expected, the file 'books.txt' is read , and lines with 'Storm' is put in to the new file 'Storm.txt'. However, it also... (4 Replies)
Discussion started by: justo
4 Replies
LEARN ABOUT OPENSOLARIS
nisbackup
nisbackup(1M) System Administration Commands nisbackup(1M)NAME
nisbackup - backup NIS+ directories
SYNOPSIS
nisbackup [-v] backup-dir directory...
nisbackup [-v] -a backup-dir
DESCRIPTION
nisbackup backs up a NIS+ directory object on a NIS+ master server. Updates to the NIS+ database will be temporarily disabled while nis-
backup is running. The backup-dir is a UNIX directory that must exist prior to running nisbackup. The nisbackup command can be used to
backup an individual NIS+ directory object or all ( -a) of the NIS+ directory objects served by a master server. The NIS+ directory objects
being backed up will be placed into subdirectories under the backup-dir directory. These subdirectories are named according to the NIS+
directory object they contain. nisbackup operates on individual NIS+ directory objects (for example, org_dir.wiz.com). This allows an
administrator to selectively backup specific directories.
The rpc.nisd(1M) process must be running on the master server with a stable NIS+ database for nisbackup to complete. nisbackup will not
attempt to correct any corruption in the NIS+ database, so it is important that backups be done regularly as part of the NIS+ administra-
tion.
The first synopsis is used to backup a single NIS+ directory object or a list of NIS+ directory objects. The objects can be partially qual-
ified or fully qualified. The machine on which the command is executing must be the master for the NIS+ directory objects specified.
The second synopsis will backup all of the NIS+ directory objects that are served by this master. The -a option is the recommended method
of backing up a master server, since it will backup all NIS+ directory objects that are served by this master. If this server is a master
server for more than one domain, the backup will include NIS+ directories that belong to all of the domains served. Individual NIS+ direc-
tory objects can be selected for restoring from a backup-dir created with the -a option. See nisrestore(1M).
The -a option only includes directory objects for which this server is the master. It is possible, but not recommended, to configure a mas-
ter server as a replica for other domains. The objects belonging to those replicated domains will not be backed up with the -a option. The
backup of replicated objects must be run on the master server for those objects.
Do not use the same backup-dir to backup different master servers. Each master server must have its own backup-dir.
nisbackup will set the rpc.nisd(1M) to read only mode, which will disable updates to the NIS+ database. This is neccessary to ensure the
consistency of the backup. For this reason, nisbackup should not be run while large numbers of updates are being applied to the NIS+ data-
base. Update utilities such as nisaddent(1M) should not be run simultaneously with nisbackup.
OPTIONS -a Creates a backup of all NIS+ directory objects for which this server is a master.
-v Verbose option. Additional output will be produced and sent to syslog(3C) upon execution of the command (see syslog.conf(4)).
OPERANDS
backup-dir The directory into which the subdirectories containing the backed up objects are placed. This must be created prior to run-
ning nisbackup.
directory The NIS+ directory object(s) being backed up.
EXAMPLES
Example 1 Backup of the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup
To backup the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup:
master_server# nisbackup /backup org_dir.foo.com.
Example 2 Backup of the entire NIS+ domain foo.com to a directory named /backup
To backup the entire NIS+ domain foo.com to a directory named /backup:
master_server# nisbackup /backup foo.com.
org_dir.foo.com. groups_dir.foo.com.
ctx_dir.foo.com.
Example 3 Backup of an entire NIS+ database to a backup directory named /backup
To backup an entire NIS+ database to a backup directory named /backup:
master_server# nisbackup -a /backup
EXIT STATUS
0 Successful completion.
1 An error occurred.
FILES
/backup-dir/backup_list
This ascii file contains a list of all the objects contained in this backup-dir directory.
/backup-dir/directory-object
A subdirectory that is created in the backup-dir that contains the NIS+ directory-object backup.
/backup-dir/directory-object/data
A subdirectory that contains the data files that are part of the NIS+ directory-object backup.
/backup-dir/directory-object/last.upd
This data file contains timestamp information about the directory-object.
/backup-dir/directory-object/data.dict
A NIS+ data dictionary for all of the objects contained in the NIS+ directory-object backup.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO NIS+(1), nisdefaults(1), nisrm(1), nisrestore(1M), rpc.nisd(1M), syslog(3C), nisfiles(4), syslog.conf(4), attributes(5)NOTES
NIS+ might not be supported in future releases of the Solaris operating system. Tools to aid the migration from NIS+ to LDAP are available
in the current Solaris release. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.11 12 Dec 2001 nisbackup(1M)
06-17-2011
