SOME better way to handle NAS backups. I have multiple customers with NAS luns (from mutliple vendors) over 1 TB in size.
Backing them up via CIFS takes too long but preserves versioning. Backup via NDMP is improved in 5.4, but still results in dumping many TB per day of unchanged data, and you lose the beauty of TSM mgmt classes for managing different data differently and versioning. I know the underlying problem is the inability to install a client on the NAS head, from whatever vendor. I'm wondering if TSM could take the NDMP dump and post-process it, to carve out the changed files only and handle them according to regular mgmt classes. That way we could keep a couple of weeks of full dumps, in case we need a full restore, but retain versions at the file level for longer, based on mgmt classes. W On 5/5/08, Skylar Thompson <[EMAIL PROTECTED]> wrote: > > For me, > > On the server: > > * Ability to expire all files in a filespace. > * Ability to move filespaces between nodes. I know proxy node kind of > gives us this, but that requires some planning ahead of time. > * Ability to make archives from backups on hand. > * Ability to do multiple operations on a filespace at a time. It would > be nice to be able to do an export and a backup to a filesystem at the > same time. > > On the client: > > * Better terminal support. I have yet to see backspace work anywhere. > * Less confusing status messages. With lots of filesystems it's hard to > see what the progress is on each one. > > -- > -- Skylar Thompson ([EMAIL PROTECTED]) > -- Genome Sciences Department, System Administrator > -- Foege Building S048, (206)-685-7354 > -- University of Washington School of Medicine >
