Hi,
Our company is embarking on a massive TSM upgrade from an old, old version. One thing the Admins are doing is assessing best approach for a vast VM and Storage environment.
I'd like advice, particularly regardnig best/recommended methods of configuration around NFS.
There are mutliple sites, but for now, the primary one as our example...
Namespaces that are currently not grouped (we think re-creating the namespaces on the Netapp will be the way to go as it will allow us to group mounts and therefore manage and concurrently back up the many volumes rather than mount / and have the single ridiculously big back up)
So - I am sure we are not the first poor slobs to face this.
Does anyone have thoughts as to best approach for managing this type of environment? The current leading proposal is re-create namespaces so as to allow grouping on specific attributes (prod systems, test systems, data types, etc), mount these into the TSM server and run the back ups as needed. This might not make a lot of sense, to explain, the Storage have 'namespace' exports allowing not only the export of the volume, but a "root level" export (contains all volumes as directories). I'd really like to hear from someone who has similar experience with NetApp Cluster Mode storage with similar landscape as I have described.
Management are not keen on backing up the NFS mounts through the client servers they are mounted into as keeping track of what is captured (and not duplicated when 1 volume is mounted into multiple clients) presents some reconciliation challenges. (how can we tell EVERYTHING is backed up!)
There is also the path the back up takes.
Netapp > client – client > TSM server
Not ideal. Would rather back up direct from NetApp
Netapp > TSM server
Just on that....
Does TSM have the capability to look at NFS mount points (assume 'domain all-local all-nfs' supplied in dsm.opt) and get that filespace directly from the source? Probably not, but I am not familiar yet with the stunning new features of the latest TSM.
Thanks in advance for any advice offered.
Our company is embarking on a massive TSM upgrade from an old, old version. One thing the Admins are doing is assessing best approach for a vast VM and Storage environment.
I'd like advice, particularly regardnig best/recommended methods of configuration around NFS.
There are mutliple sites, but for now, the primary one as our example...
- 400+ VMs.
- Multiple NFS (v3) mounts into most of the VM servers. (some mounts shared between servers)
- Multiple vServers from NetApp 'Cluster Mode' storage (OnTap 8.2.1) providing the NFS shares.
Namespaces that are currently not grouped (we think re-creating the namespaces on the Netapp will be the way to go as it will allow us to group mounts and therefore manage and concurrently back up the many volumes rather than mount / and have the single ridiculously big back up)
So - I am sure we are not the first poor slobs to face this.
Does anyone have thoughts as to best approach for managing this type of environment? The current leading proposal is re-create namespaces so as to allow grouping on specific attributes (prod systems, test systems, data types, etc), mount these into the TSM server and run the back ups as needed. This might not make a lot of sense, to explain, the Storage have 'namespace' exports allowing not only the export of the volume, but a "root level" export (contains all volumes as directories). I'd really like to hear from someone who has similar experience with NetApp Cluster Mode storage with similar landscape as I have described.
Management are not keen on backing up the NFS mounts through the client servers they are mounted into as keeping track of what is captured (and not duplicated when 1 volume is mounted into multiple clients) presents some reconciliation challenges. (how can we tell EVERYTHING is backed up!)
There is also the path the back up takes.
Netapp > client – client > TSM server
Not ideal. Would rather back up direct from NetApp
Netapp > TSM server
Just on that....
Does TSM have the capability to look at NFS mount points (assume 'domain all-local all-nfs' supplied in dsm.opt) and get that filespace directly from the source? Probably not, but I am not familiar yet with the stunning new features of the latest TSM.
Thanks in advance for any advice offered.