Jump to content

bradp015

Members
  • Content count

    50
  • Joined

  • Last visited

Community Reputation

1 Neutral

About bradp015

  • Rank
    Advanced Member

Recent Profile Visitors

250 profile views
  1. Nigel, Thank you for your help! So this raid only unmounted on its own when Ret was copying a media set from it (reading). Never has it unmounted otherwise. That makes me think its a poss. issue with ret. Maybe ret paused long enough for the raid to self sleep? Really not sure what happened. But i know it happened 2 times. When I checked "match" and "dont dupe file" for the script and re ran it (third time BUT I did a "cat rebuild" first as tech support recommended). I did not do a cat rebuild before the other 2 times. ret finished up and i now have a dupe of the media set on another drive (single internal drive). This new single drive is the same model drive as the raid's. (the other single drive was not). Not that is should matter though. Agreed on when to use DU. If 1 raid drive was to fail, showing the red light on the enclosure, Id complete the process per instructions to replace the bad with a good drive and let it do a hardware rebuild. I get what your saying about the "unexpect'd unmount". That does keep the concern in the back of my mind..... 😞 I did email macsales.com but havnt heard back from them. all the best! brad p
  2. David, thank you for all your help. You have been instrumental in my edu for ret. You have educated me more than you realize. I want to convey my appreciation for all you have done for me. thank you..... I did a copy backup script today, and although it took a while for "match" and "dont copy dupes" to complete, I dont think it will be a time burden to run the script periodically. Saving my arse in case of "the sky is falling" on the raid drive. If I duplicate every client folder backup script to my SAFE drive, and get the SAFE copy done that way, I dont think it will save much time as just doing the "copy backup" script. Copy bacup script seems to take a lot less time the duping every client script. And easy to deal with. Gratitude! bradp
  3. Lennart, You have helped me a lot, i want to thank you for that! best! bradp
  4. Q: Is it possible to use 1 script to backup to 2 different media sets that are on 2 different drives, with 1 script execution? It seems that running a script, even when the script is set to use 2 media sets, you can only choose 1 set in the run dialog. Is there any way to select 2 media scripts so data goes to both sets with one run of a script? Workaround: You could make 2 identical scripts and just change the destination on one of them, then run them concurrently... ?? thanks bradp
  5. I realize iv posted this in another thread.... I was worried about the raid due to the unmounting.... Im under impression that unexpected unmounting can create data corruption. Yes, it was in the "read" in not "write" task (having data copied "from" the raid while it unmounted) but im not an expert in this area therefor extremely cautious here.
  6. Hi David, No its not a NAS. This is the drive im using https://eshop.macsales.com/item/Other World Computing/MED3FR7T08.0/ thanks b
  7. David, Thanks for do all that searching. Helpful! i have another 4TB drive on the way and plan to try a "copy media set" again. Im not sure why it unmounted during the copy before. If i can get that solved ill be able to move on, hopefully. At least with the 2 4TB drives i can have a safe copy aside from the Raid copy media set trial. The unexpected unmounting of the raid drive gave a bit of panic. So I feel I need at least a finder copy of it somewhere before screwing with the raid again. b
  8. You are correct about finder copy worked fine. I did submit a ticket and am corresponding with support. I have to say, because of the time lapse in corresponding, lots happens between comments. its been difficult to convey everything to them. Q: Whats your take on using Mac "disk utility's first aid" on a raid enclosure with 2 4TB drives in mirrored mode. https://eshop.macsales.com/item/Other World Computing/MED3FR7T08.0/ Because disk first aid would see 1 drive. How does that work within the raid enclosure? Can one drive need fixing and the other not needing fixing? If disk first aid fixes an error, how does that translate to 2 identical drives? This raid doesnt have a external controller or software controller, its all inside the enclosure. So there's no way to address the 2 drives separately. Macsales said i shouldnt have to use disk utility because if one drive fails the led will light RED. They didnt say it would hurt the drive (corruption etc. ) No other comments about using DU first aid. You can see im not a raid expert by any means.... By "personalized help" you mean "no charge" for 30 days? Thank you David
  9. David, 1. Sorry to confuse. the original 'copy from 4T to raid' was done in finder. In ret the member in SFA 3 media set was changed from 4T to raid. Everything worked fine. Lenart posted that idea. And since then my journey has brought me thru many roads with the goal of using 4T as a safe. Eventually using 'copy backup' per your suggestion. Having a bit of 'panic' happen on the journey im now in this state. raid=regular media set (SFA 3) and backups going fine. 4T= a 'finder' copy of the media set SFA 3. 2. Before i did have my original media set SFA 3 still on 4T. And was 'leaving it there' cause i did not trust the raid yet. The last items we tried, was to do 'copy media set' from raid to 4T. That task failed. You asked, did i have enough space. We figured yes i did have enough space. But i thot maybe it needs the full 4TB's (i have the raid set to use all space). So i dumped my original set and cleared the drive. I did 'copy media set again. Thats when raid unmounted. Re-try then same=unmounted. After that i had panic about the raid. Unmounting can lead to corruption. So i did 'finder copy' to 4T. The changing number in ret 'use this much space' i had noticed a long the way. I would change it to 99% and the next time i checked it would be different. I even see 146GB/99%. Which obviously is not right. I honestly didnt think this would drag on so long, so i didnt start a trouble shoot log of events. I prob. should have. But I do our thread here. thank you for all your help.... its incredibly useful. b
  10. David, I do not know if the unmount event happened at the same point in the copy media set. Two items on your comments. Yes, i did set the space on the destination 4T to be large enough to hold the media set. When i returned to that very same page to check that i had set enough space i was surprised to see numbers had changed to be very low... Like 146Gb/ 46%. When I change them back to 3750/99% and left the page, on returning later the numbers had changed again. I thot this bizarre and stated it in my posts. So as it stands now there's 2 things that are not acting as you would expect. 1. when choosing a member there's nothing under the existing retrospect folder shown in the select dialog. Although the 1-SFA 3 member is indeed seen in the finder directory. And when I did this the very first time (retro 9) to move the set to raid, I DID SEE THE WHOLE DIRECTORY in retrospect. NOW i do not! 2. When setting the member space, the numbers will change when you visit the dialog again. Im not sure how much, when and which members change. (raid and/or 4T). It seems random. Although after checking the raid set many times I recall it sticking at 99%. Ill need to check that again. thanks
  11. I was seeing if Don had solved the issue. Reason for posting here. Id be happier to continue with the other newer thread i started. Yes, confusing is correct! Thanks for posting the link of the proper thread..... we should use that one since all my whoa's are there.
  12. Lennart After having the unmounting issue i got a little un-nerved and did a finder copy just to have the bu set on the single 4T drive. The raid drive did NOT unmount. That gives me some confidence that its not the raid drive that is buggy or going south. So the unmounting only happened on the "media set copy" task. I think it was about 4 hours into the copy that it unmounted. Not sure if was the same length of time on the 2 times I tried the "copy media set" in ret. David, Yes it does have that... just to inform you, i dumped the "copy media set" files we did last time. I didnt want to have any space issue (and not that it should been an issue as we discussed) to get my set (currently the only one) copied to back to the single drive from the raid. (a bit of panic on the unmounting problem i had). thank you b
  13. Well, Im still having some issues here....using ret 15 mac now. 1. I tried moving the media set back to a single drive from a raid drive. In the copy media set task the raid drive unmounted for no reason and ret thru the error "cant find volume" Iv done this 2 times. Both time the raid will just unmount in the middle of the task. Because of the unexpected unmounting and not knowing if its the raid drive or ret. doing this, I decided to put back the media set to the single drive, which now i trust more. 2. Now in selecting the path of the media set, NOTHING is in the "retrospect" folder. Its as it is empty. In the finder I see the correct path for the set. But not in retrospect. Don Lee, have you solved the moving media set yet?? I have emailed support and now have a ticket, but it took long enough for support to get back to me, that i am on to a bunch of diff issues than my original issue.
  14. I all seems so simple! Then the gotchya's come out.... On the rebuild, when adding the member im not getting anything contained within the retrospect folder. I click the carrot and nothing is shown..... So i can select a member to rebuild.... Maybe i should start from scratch deleting the media set, cat, and script. Just love the bumps in the road....Its a way of life really.... This was happening before. The nothing in the ret folder as it shows in the app.
  15. David, thank you for the insight! I did wonder how smart the ret app would be. Iv run into this before in other apps. Yes, I agree that naming and in app coding may be confused. Moves and delete's you suggested completed. Now, Im pondering what to do next. Redo the whole 'copy media set' task (deleting the stalled run data first) OR run it again as is OR create a 'copy backup' script and run (with dont add dupes and match checked). Since 'copy media set' had almost finished most of the data is copied. Re running it without "dont add dupes' and 'match source media' checked (so in the unchecked state) would add to the whole set to the existing set i believe, doubling most of it. Since most of the set is already copied, to me, it makes sense to do a 'copy backup' run. yes???? thank you bradp
×