05-07-2014
Thank you very much.
Yes I can get downtime for cluster
---------- Post updated 05-07-14 at 08:31 AM ---------- Previous update was 05-06-14 at 02:01 PM ----------
Hi,
Thank you ver much.
Yes i can get a downtime for the cluster
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Discussion started by: Hils
0 Replies
2. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
3. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
4. HP-UX
Hello gurus,
I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place.
Environment: Migrating from CX4 to VMAX - using OR/Hot Pull.
Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies
5. Solaris
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies
6. HP-UX
Hi,
I am very new to HP-UX, and we're going to be doing a SAN migration.
We're going to take down the machine, and zone it to the new SAN.
My question is, will the device names change and will that interfere with the LVM?
If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
7. Red Hat
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
8. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
9. Solaris
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
10. Filesystems, Disks and Memory
hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB.
i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 Replies
LEARN ABOUT DEBIAN
downtimes
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)