Sponsored Content
Operating Systems Solaris VxVM..anything to worry about in here.. Post 302267802 by incredible on Sunday 14th of December 2008 12:38:23 AM
Old 12-14-2008
Its a Production system, connected to a D1000 Array.
No worries about the availibility of parts. We will want a resolution so that we can follow up on that as soon.
And if there should be a downtime required, let me know with the action plan so that we can proceed.

Last edited by incredible; 12-14-2008 at 01:50 AM..
 

7 More Discussions You Might Find Interesting

1. Solaris

VxVM

All solaris rescue gurus out there .... I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory. The machine is (was) running Vxvm with the root volume encapsulated. I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies

2. Filesystems, Disks and Memory

vmstat -d with VxVM

I've got a Linux box that I'm pretty sure is having some disk issues. iostat isn't installed, but vmstat is, so i've been trying to use that to do some initial diagnostics while I go through our company's change control process to get iostat installed. The problem I'm having is that the disks... (4 Replies)
Discussion started by: kknigga
4 Replies

3. Solaris

VxVM on Solaris.

Hi, Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies

4. Solaris

Reg. VXVM

Hi Guys, I have a doubt either to Reboot the server after Replacing the disk0. I have two disks under vxvm root mirrored and i had a problem with primary disk so i replace the disk0 failed primary disk and then mirrored. After mirroring is it reboot required ? (7 Replies)
Discussion started by: kurva
7 Replies

5. Filesystems, Disks and Memory

VxVM and MPxIO

:confused: Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO. If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies

6. Solaris

No of volumes in vxvm

Anyone knows that how many volumes can be created in a Diskgroup? Thanks in advance... (1 Reply)
Discussion started by: bpsunadm
1 Replies

7. Solaris

vxvm

hi all, how can we check whether vxvm is installed in our system or not in solaris? Thanks in advance dinu (4 Replies)
Discussion started by: dinu
4 Replies
DOWNTIMES(1)						      General Commands Manual						      DOWNTIMES(1)

NAME
downtimes - display system downtime records made by downtimed(8) SYNOPSIS
downtimes [-d downtimedbfile] [-n num] [-s sleep] downtimes -v downtime [-d downtimedbfile] [-n num] [-s sleep] downtime -v DESCRIPTION
The downtimes command displays the contents of the downtime database in human readable format. The downtime database is maintained by down- timed(8). The singular form downtime displays details only about the last time the system was down, whereas the plural form downtimes displays all records in the database. The -n option can be used to specify the number of downtime records to display. OPTIONS
-d downtimedbfile Use the specified downtime database file instead of the system default. -n num Define how many latest downtime records to output. Default is all. -s sleep Calculate the approximate crash time by specifying what was the sleep value of downtimed(8). -v Display the program version number, copyright message and the default settings. EXIT STATUS
The program exits 0 on success, and >0 if an error occurs. SEE ALSO
downtimed(8), uptime(1), http://dist.epipe.com/downtimed/ BUGS
The reporting accuracy in case of a system crash depends on how often the time stamp is updated. COPYRIGHT
Copyright (C) 2009-2011 EPIPE Communications. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``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. IN NO EVENT SHALL THE AUTHOR OR CONTRIBU- TORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE- MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABIL- ITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as represent- ing official policies, either expressed or implied, of EPIPE Communications. version 0.5 2011-03-02 DOWNTIMES(1)
All times are GMT -4. The time now is 03:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy