Sponsored Content
Operating Systems Linux Ubuntu Md0 raid don't see my folders Post 303029078 by stomp on Sunday 20th of January 2019 03:54:18 PM
Old 01-20-2019
Since you likely destroyed your data by reformatting I would suppose data recovery very difficult.

Better have your backup restored.
 

8 More Discussions You Might Find Interesting

1. Solaris

RAID 5 mount points don't automount on boot

Hi, I set up a RAID 5 configuration and for some reason the volumes won't mount when the system boots. I have to manually mount them from the command line and all is fine. Here's the vfstab entries: #device device mount FS fsck mount mount #to mount ... (2 Replies)
Discussion started by: rpollard001
2 Replies

2. UNIX for Advanced & Expert Users

Bad magic number on /dev/md0

Hello All, (RHEL4) Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array. I somehow managed to up the system with working raid1 array. But the main problem persisted.. i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies

3. UNIX for Dummies Questions & Answers

Copying multiple folders to local machine (don't know folder names)

Hi. I'm trying to copy multiple folders from the remote machine to the local machine. I wrote a batch file to run an ftp window. The problem I am having is that the only command to copy files is mget *, and this copies only files, not folders. For example, ftp ts555 cd ts555/test ' test... (5 Replies)
Discussion started by: leenyburger
5 Replies

4. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

5. Linux

If i don't have raid disks can i shut down dmraid device-mapper?

hello my centOS newly installed system loading dmraid modules on startup I did remove all LVM/raid things from system installation menus and after installation too but dmraid is still there and he says: no raid disks found also I did modprobe -r dm_raid45 and it do remove it but only until... (7 Replies)
Discussion started by: tip78
7 Replies

6. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies

7. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

8. Red Hat

RAID Configuration for IBM Serveraid-7k SCSI RAID Controller

Hello, I want to delete a RAID configuration an old server has. Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton? I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies
nisrestore(1M)						  System Administration Commands					    nisrestore(1M)

NAME
nisrestore - restore NIS+ directory backup SYNOPSIS
nisrestore [-fv] backup-dir directory... nisrestore [-fv] -a backup-dir nisrestore -t backup-dir DESCRIPTION
nisrestore restores an existing backup of a NIS+ directory object that was created using nisbackup(1M). The backup-dir is the UNIX direc- tory that contains the NIS+ backup on the server being restored. The nisrestore command can be used to restore a NIS+ directory object or a complete NIS+ database. It also can be used as an "out of band" fast replication for a new replica server being initialized. The rpc.nisd(1M) daemon must be stopped before running nisrestore. The first synopsis is used to restore a single directory object or a specified list of directory objects. The directory can be partially qualified or fully qualified. The server being restored will be verified against the list of servers serving the directory. If this server is not configured to serve this object, nisrestore will exit with an error. The -f option will override this check and force the operation. The second synopsis will restore all of the directory objects contained in the backup-dir. Again, the server will be validated against the serving list for each of the directory objects in the backup-dir. If one of the objects in the backup-dir are not served by this server, nisrestore will exit with an error. The -f option will override this check and force the operation. The -a option will attempt to restore all NIS+ objects contained in the backup-dir. If any of these objects are not served by the server, nisrestore will exit with an error. If the backup-dir contains objects that are not served by the server, nisrestore must be executed with- out the -a option and the specific directory objects listed. The -f option will disable verification of the server being configured to serve the objects being restored. This option should be used with care, as data could be inadvertently restored to a server that doesn't serve the restored data. This option is required in the case of restoring a single server domain (master server only) or if the other NIS+ servers are unavailable for NIS+ lookups. The combination of options -f and -a should be used with caution, as no validation of the server serving the restored objects will be done. New replicas can be quickly added to a namespace with the nisrestore command. The steps are as follows. Configure the new replica on the master server (see nisserver(1M)): master# nisserver -R -h replica Temporarily stop the rpc.nisd server process on the new replica server: replica# svcadm disable -t network/rpc/nisplus:default Create a backup of the NIS+ database on the master, which will include the new replica information. See nisbackup(1M). The /backup will need to be exported to the new replica. See share_nfs(1M). master# nisbackup -a /backup Restore the backup of the NIS+ database on the new replica. Use the -f option if nisrestore is unable to lookup the NIS+ objects being restored. The backup should be available through nfs or similar means. See share_nfs(1M). replica# nisrestore -f -a //nfs-mnt/backup Restart the rpc.nisd(1M) process on the new replica, and the server will immediately be available for service: replica# svcadm enable network/rpc/nisplus:default OPTIONS
The following options are supported: -a Restores all directory objects included in the backup-dir partition. -f Forces the restoration of a directory without the validation of the server in the directory object's serving list. -t Lists all directory objects contained in backup-dir. -v Verbose option. Additional output will be produced upon execution of the command. OPERANDS
The following options are supported: backup-dir The UNIX directory that contains the data files for the NIS+ directory objects to be restored. directory The NIS+ directory object(s) to be restored. This can be a fully or partially qualified name. EXAMPLES
Example 1: Restoring the Directory Object on a Replica Server from a Local UFS Partition To restore the org_dir directory object of the domain foo.com on a replica server from a local ufs partition named /var/backup: replica_server# nisrestore /var/backup org_dir.foo.com. Example 2: Forcing the Restore of a Backed up NIS+ Namespace to a Replica Server From the Backup Partition To force the restore of an entire backed up NIS+ namespace to a replica server from the backup partition named /var/backup: replica_server# nisrestore -f -a /var/backup Example 3: Restoring the Subdomain on a Master Server From a Backup that Includes Other Directory Objects To restore the subdomain sub.foo.com on a master server, from a backup that includes other directory objects: master_server# nisrestore /var/backup sub.foo.com. org_dir.sub.foo.com. groups_dir.sub.foo.com. 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. This information can be displayed with the -t option. /backup-dir/directory-object A subdirectory that is created in the backup-dir which contains the directory-object backup. /backup-dir/directory-object/data A subdirectory that contains the data files that are part of the 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 this directory-object backup. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), nis+(1), nisdefaults(1), nisbackup(1M), nisserver(1M), rpc.nisd(1M), share_nfs( 1M), svcadm(1M), nisfiles(4), attributes(5), smf(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. The NIS+ service is managed by the service management facility, smf(5), under the service identifier: svc:/network/rpc/nisplus:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 13 Aug 2004 nisrestore(1M)
All times are GMT -4. The time now is 10:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy