Ask SGI
				-------

Personal notes on the "Ask SGI" session on 5th December 2012:


The only question on notice was discussed at some length but I don't
recall any outcome apart from "tell us more":

    All sites running DMF must take backups of the DMF-managed file
    systems to protect against loss.

    What are SGI's plans for providing a good canned solution (with
    the ability of sites to do local configuration) for the management
    of backups and backup tapes?


The following four wish-list items were mentioned:

36  Allow the dmmove and dmget commands to specify the preferred VG
    to use for recalls.
    (Duplicates #10 from the 2010 list).

SGI:	Possibly in ISSP 3.0

42  The packaging of patches is overly complicated, especially for
    DMF clients with the Linux ones being the worst.  A tarball
    containing client RPMs to be installed on the server(!) which
    install further tarballs containing RPMs for installation on
    the clients.

SGI:	These follow the precedent set by CXFS

09  The option to have load balancing of recalls across both VGs
    containing copies of the migrated files.

SGI:	We have some concerns about the best approach.	Maybe a test
	implementation after ISSP 3.0 is released, though some beta
	test sites might be required.

45  If a recall is received requiring a tape currently in use for
    migrations, the migrations should switch to a different tape to
    avoid delaying the recall.  This is becoming more important as
    tape capacities grow over time.
    (Duplicates #18 from the 2010 list).

SGI:	This may be implemented as well as #9 above.