04-07-2013
If you are using the lun as a staging area for later backup to tape, fine. Or as short term backup. Disk as a permanent longterm "backup of official record" like for payroll data is a bad idea. Disk is not forever, tape is closer to forever.
Most SAN companies give you a warranty, and then a purchasable warranty for a longer period of time. They do that because they know that eventually every part on the SAN controller & trays will have to be replaced. And they stop making parts. So they can no longer replace them. We have SAN that went out of warranty and we are using another headless SAN to cannibalize for parts until the new one arrives. It is just temp storage.
This User Gave Thanks to jim mcnamara For This Post:
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I have been using the hostdump.sh backup script for over a year now and have recently run into a problem. I'm now getting the following error at the end of my jobs;
/bin/mt -f: error fsf'ing tape.
This script uses the native 'ufsdump'. So, I try to go back and read the last dump on the tape... (11 Replies)
Discussion started by: Solaris
11 Replies
2. UNIX for Dummies Questions & Answers
When using hostdump.sh to backup a system I can do it fine. But how can I restore what I backuped up?
:)
Thx in advance (2 Replies)
Discussion started by: merlin
2 Replies
3. UNIX for Dummies Questions & Answers
Hello everyone my ? is about backups. I'am running SCO OS 505 and currently backing up the hole HD. Well the back up is taking too long and this is becoming a problem for the users since we are a 24-7 bussines, I whant stop backing up every thing on the HD. What are the most important files and... (1 Reply)
Discussion started by: kikkin
1 Replies
4. UNIX Desktop Questions & Answers
I've been handed the task of backing up some of our system files on a Solaris box. No probs. Zipped the logs that needed backing up but my superiors do not want it on tape, they want it spanned on CD's. The CD-Writer is available on a MS box. FTP'd the zipped logs across too the MS Machine but now... (1 Reply)
Discussion started by: mccrack_2003
1 Replies
5. UNIX for Advanced & Expert Users
I've done this in the past, but I didn't save the syntax. I'm still kicking myself about that...
I am trying to mount \\server_name\share_name for read/write under CentOS 5.2 (a "generic" version of RedHat). As I recall, there was a fairly simple (maybe a oneline) command that would allow NTFS... (2 Replies)
Discussion started by: shew01
2 Replies
6. AIX
Hello,
I've got multiple AIX LPARs running on VIOS, within a blade environment. I need to dump a mksysb backup to backup rootvg and a couple of other volume groups.
mksysb -i "destination"; works however I'd like to make sure its being done correctly.
on the other volume groups, ive... (2 Replies)
Discussion started by: ollie01
2 Replies
7. Shell Programming and Scripting
Input data:
read1_data1
read1_data1
read2_data1
read3_data1
read4_data1
read4_data1
read4_data1
read5_data1
.
.
Desired output result:
read1_data1
read1_data2
read2_data1
read3_data1
read4_data1 (3 Replies)
Discussion started by: perl_beginner
3 Replies
8. Shell Programming and Scripting
Hello all,
I'm using nas4free as a SAN and am having troubles getting a backup of it's data to work properly. I've posted in the nas4free forums, but haven't received much help.
Here is the code I'm using:
#!/bin/sh
{... (1 Reply)
Discussion started by: dpatino
1 Replies
9. Solaris
I am trying to get ntfs-3g to work, so I can mount ntfs partitions. I installed ntfs-3g from SFE - Software Packages for Solaris, OpenIndiana and OmniOS | Get your favourite software for (TM) Solaris 11, OpenIndiana Hipster, OmniOS as ready-to-use IPS packages Repository
There are VLC, Wine, etc.... (0 Replies)
Discussion started by: kebabbert
0 Replies
iobind(1M) iobind(1M)
NAME
iobind - bind a driver to a device
SYNOPSIS
instance]
DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it.
As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware
paths.
The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will
be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated
with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The
optional forces the binding to occur at the next reboot if it cannot be done online.
The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of
these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The
user is given the option to proceed or not.
If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown
by the command:
The specified driver was successfully bound to the hardware path.
The specified driver cannot be used to claim the hardware at
the specified hardware path.
The device at the address is responding, but it is in an
error state.
The device at the specified hardware path is no longer responding.
The specified hardware path is locked. Try again later.
The driver failed.
Options
recognizes the following options:
Force the binding even though a driver does not support online unbinding
and binding or the device is in use. In this case, the binding will take effect at the next reboot.
The LUN hardware path of a device
must be of the form 64000/0x/0x.
The instance number to be assigned to the device.
The name of the driver that the LUN and legacy hardware paths are to be bound to.
RETURN VALUE
Exit values are:
Successful completion.
An error condition occurred.
EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class.
Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number
Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot.
WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short
window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If
this happens, must be executed again to bind the desired driver.
may be executed only by the superuser.
SEE ALSO
ioscan(1M), intro(7).
iobind(1M)