03-28-2017
Your question arises out of a fairly common scenario. Many sysadmins on this forum will have experienced such a thing and you may receive different answers. What I would say from my long experience is this.
If you are backing up over NFS (which is a very common thing to do and nothing wrong with that) then the bottleneck will be the network speed not the disk interface. Backup jobs have a habit of getting bigger over time and if you have to look at several volumes to find the necessary space, it makes things much more complicated to manage. Therefore, I would say that one big volume is much easier to manage because you can see what's on it all in one go, (and decide what old backups to delete to make room).
I would suggest that, if necessary, review your network interface speed and possibly upgrade and/or aggregate/team network interfaces to up the bandwidth.
Hope that helps. Let's see what others on here think.
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I've got a bunch of application CDs that I use here at home under Wine. They are Windows applications and as such, some of them want to see the volume label in order for the application to run. So... just copying the CD-ROM contents to a directory doesn't work. With that in mind, what I've done... (1 Reply)
Discussion started by: deckard
1 Replies
2. Linux
Hi,
I have created symlink under /.
It is /latest Pointing to /home/users/neel_prog_V1.0.
(Note: I have created this symlink so that when version get changed I will need to change only symlink instead of doing changes in /etc/exports.)
I have shared this symlink with NFS. in /etc/exports I... (0 Replies)
Discussion started by: neel.gurjar
0 Replies
3. High Performance Computing
I'm planning to load balance 2 web servers. I'm considering mounting an NFS share between the 2 servers so they can share the data. My question is: does this setup offset some of the benefits of load balancing? although there are 2 web servers, they both still access a single NFS server. Wouldn't... (2 Replies)
Discussion started by: gaspol
2 Replies
4. AIX
Hi,
I would like to know if there is a command similar to scsimgr in HP-UX that
can help me change the algorithm and reserve_policy attributes of all luns presented to an AIX host.
Otherwise I would have to use,
chdev -l hdiskX -a algorithm=round_robin reserve_policy=no_reserve
in a... (1 Reply)
Discussion started by: kanna_geekworkz
1 Replies
5. Solaris
Hi,
Not sure where to post this, I'm sorry and need suggestion if this is wrong section.
we are running NFS Server on Solaris 10 and client box is HP-UX 11.11 (Can't apply latest patches/upgrades as in-house appln. doesn't allow)
I am able to mount NFS shares from this Solaris box onto all... (4 Replies)
Discussion started by: prvnrk
4 Replies
6. AIX
Hi,
I would like to know how to share lun in between 2 lpars.
I have run tbe below command on vio server.
/usr/sbin/chdev -l hdisk1 -a reserve_policy=no_reserve
after above command I am able to assign lun on one Lpar. but it is not visible to other lpar.
even after this I have run... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
7. UNIX for Dummies Questions & Answers
I am not sure is this plausible...
I have just built a NFS master server on a solaris box (secured by NIS)
And I have a dozen of virtual machines running 32 and 64 bits linux and windows, running different types of servers.
I am not sure is it possible to move most of the programs to the... (6 Replies)
Discussion started by: xstaci
6 Replies
8. UNIX for Dummies Questions & Answers
Hello,
I would like to share a 9p (Plan 9) passthrough/share to a VM via NFS (using a guest as an NFS server to share a directory from the host)
At the moment I am getting the error message: 'exportfs: /share does not support NFS export'... (2 Replies)
Discussion started by: Scratch
2 Replies
9. Solaris
Hi,
I've noticed that mpathadm states that one of our luns has no active paths:
/dev/rdsk/c6t60000970000298700009533031324333d0s2
Total Path Count: 4
Operational Path Count: 4
/dev/rdsk/c6t60000970000298700009533031333037d0s2
... (3 Replies)
Discussion started by: badoshi
3 Replies
10. UNIX for Dummies Questions & Answers
input file:
AD,00,--,---,---,---,---,---,---,--,--,---
AM,000,---,---,---,---,---,---
AR, ,---,--,---,---
AA,---,---,---,---
AT,---
AU,---,---,---
AS,---,---
AP,---,---,---
AI,---
AD,00,---,---,---, ,---,---,---,---,---,---
AM,000,---,---,---
AR,... (6 Replies)
Discussion started by: kcdg859
6 Replies
share(1M) share(1M)
NAME
share - make local resource available for mounting by remote systems
SYNOPSIS
share [-F FSType] [-o specific_options] [-d description] [pathname]
The share command exports, or makes a resource available for mounting, through a remote file system of type FSType. If the option -F FSType
is omitted, the first file system type listed in /etc/dfs/fstypes is used as default. For a description of NFS specific options, see
share_nfs(1M). pathname is the pathname of the directory to be shared. When invoked with no arguments, share displays all shared file sys-
tems.
-F FSType
Specify the filesystem type.
-o specific_options
The specific_options are used to control access of the shared resource. (See share_nfs(1M) for the NFS specific options.) They may be
any of the following:
rw
pathname is shared read/write to all clients. This is also the default behavior.
rw=client[:client]...
pathname is shared read/write only to the listed clients. No other systems can access pathname.
ro
pathname is shared read-only to all clients.
ro=client[:client]...
pathname is shared read-only only to the listed clients. No other systems can access pathname.
Separate multiple options with commas. Separate multiple operands for an option with colons. See .
-d description
The -d flag may be used to provide a description of the resource being shared.
Example 1: Sharing a Read-Only Filesystem
This line will share the /disk file system read-only at boot time.
share -F nfs -o ro /disk
Example 2: Invoking Multiple Options
The following command shares the filesystem /export/manuals, with members of the netgroup having read-only access and users on the speci-
fied host having read-write access.
share -F nfs -o ro=netgroup_name,rw=host1:host2:host3 /export/manuals
/etc/dfs/dfstab
list of share commands to be executed at boot time
/etc/dfs/fstypes
list of file system types, NFS by default
/etc/dfs/sharetab
system record of shared file systems
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mountd(1M), nfsd(1M), share_nfs(1M), shareall(1M), unshare(1M), attributes(5)
Export (old terminology): file system sharing used to be called exporting on SunOS 4.x, so the share command used to be invoked as
exportfs(1B) or /usr/sbin/exportfs.
If share commands are invoked multiple times on the same filesystem, the last share invocation supersedes the previous--the options set by
the last share command replace the old options. For example, if read-write permission was given to usera on /somefs, then to give read-
write permission also to userb on /somefs:
example% share -F nfs -o rw=usera:userb /somefs
This behavior is not limited to sharing the root filesystem, but applies to all filesystems.
9 Dec 2004 share(1M)