Re: [gpfsug-discuss] GPFS(snapshot, backup) vs. GPFS(backup scripts) vs. TSM(backup)

2016-03-09 Thread Jaime Pinto
Quoting Yaron Daniel : Hi Did u use mmbackup with TSM ? https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.adm.doc/bl1adm_mmbackup.htm I have used mmbackup on test mode a few times before, while under gpfs 3.2 and 3.3, but not under 3.5

Re: [gpfsug-discuss] GPFS(snapshot, backup) vs. GPFS(backup scripts) vs. TSM(backup)

2016-03-09 Thread Yaron Daniel
Hi Did u use mmbackup with TSM ? https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.adm.doc/bl1adm_mmbackup.htm Please also review this : http://files.gpfsug.org/presentations/2015/SBENDER-GPFS_UG_UK_2015-05-20.pdf Regards Yaron Daniel 94 Em

[gpfsug-discuss] GPFS(snapshot, backup) vs. GPFS(backup scripts) vs. TSM(backup)

2016-03-09 Thread Jaime Pinto
Here is another area where I've been reading material from several sources for years, and in fact trying one solution over the other from time-to-time in a test environment. However, to date I have not been able to find a one-piece-document where all these different IBM alternatives for

Re: [gpfsug-discuss] GPFS+TSM+HSM: staging vs. migration priority

2016-03-09 Thread Jaime Pinto
Interesting perspective Mark. I'm inclined to think EBUSY would be more appropriate. Jaime Quoting Marc A Kaplan : For a write or create operation ENOSPC would make some sense. But if the file already exists and I'm just opening for read access I would be very confused

Re: [gpfsug-discuss] GPFS+TSM+HSM: staging vs. migration priority

2016-03-09 Thread Marc A Kaplan
For a write or create operation ENOSPC would make some sense. But if the file already exists and I'm just opening for read access I would be very confused by ENOSPC. How should the system respond: "Sorry, I know about that file, I have it safely stored away in HSM, but it is not available

Re: [gpfsug-discuss] GPFS+TSM+HSM: staging vs. migration priority

2016-03-09 Thread Chris Scott
Not meaning to hjack the thread but while we're on the topic of transparent recall: I'd like to be able to disable it such that I can use SS ILM policies agreed with the data owners to "archive" their data and recover disk space by migrating files to tape, marking them as immutable to defend

Re: [gpfsug-discuss] GPFS+TSM+HSM: staging vs. migration priority

2016-03-09 Thread Dominic Mueller-Wicke01
Hi Jamie, I see. So, the recall-shutdown would be something for a short time period. right? Just for the time it takes to migrate files out and free space. If HSM would allow the recall-shutdown the impact for the users would be that each access to migrated files would lead to an access denied