Zoltan I kind of agree with Ung Yi
What is the purpose of your TSM backups? DR? Long term retention for auditability/sarbox/other regulation? It may well be that a daily or even more frequent snapshot regime might be the best way to get back that recently lost/deleted/corrupted file. Use a TSM backup of a weekly point-of-consistency snapshot as your long term strategy. Of course a better option would be an embedded TSM client on the Isilon itself, but the commercial realities are that will never happen. Cheers Steve Steven Harris TSM Admin Canberra Australia -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Yi, Ung Sent: Friday, 6 July 2018 6:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Looking for suggestions to deal with large backups not completing in 24-hours Hello, I don’t know much about Isilon. There might be SAN level snap backups option for Isilon. For our Data domain, we replicate from Main site to DR site, then take snap at our DR site every night. Each snap is consider a backup. Thank you. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, July 05, 2018 2:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Looking for suggestions to deal with large backups not completing in 24-hours As I have mentioned in the past, we have gone through large migrations to DFS based storage on EMC ISILON hardware. As you may recall, we backup these DFS mounts (about 90 at last count) using multiple Windows servers that run multiple ISP nodes (about 30-each) and they access each DFS mount/filesystem via -object=\\rams.adp.vcu.edu\departmentname. This has lead to lots of performance issue with backups and some departments are now complain that their backups are running into multiple-days in some cases. One such case in a department with 2-nodes with over 30-million objects for each node. In the past, their backups were able to finish quicker since they were accessed via dedicated servers and were able to use Journaling to reduce the scan times. Unless things have changed, I believe Journling is not an option due to how the files are accessed. FWIW, average backups are usually <50k files and <200GB once it finished scanning..... Also, the idea of HSM/SPACEMANAGEMENT has reared its ugly head since many of these objects haven't been accessed in many years old. But as I understand it, that won't work either given our current configuration. Given the current DFS configuration (previously CIFS), what can we do to improve backup performance? So, any-and-all ideas are up for discussion. There is even discussion on replacing ISP/TSM due to these issues/limitations. -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ucc.vcu.edu&d=DwIBaQ&c=k9MF1d71ITtkuJx-PdWme51dKbmfPEvxwt8SFEkBfs4&r=p7OfdQbObZllF-mnDqjrQg&m=jX8fSV2xXtioczSetX1viQa6EzVNOcZlBX9ddwWGXRM&s=KsUuBwu8G3pWJ7R7hedi0ZISk0CjIRrWQMJneyjNxD4&e= zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit https://urldefense.proofpoint.com/v2/url?u=http-3A__phishing.vcu.edu_&d=DwIBaQ&c=k9MF1d71ITtkuJx-PdWme51dKbmfPEvxwt8SFEkBfs4&r=p7OfdQbObZllF-mnDqjrQg&m=jX8fSV2xXtioczSetX1viQa6EzVNOcZlBX9ddwWGXRM&s=xiPt_TkUv02i1b7VQfKybQwokZGIKegAHQtBFG_G19U&e= This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance.
