So I just started the restore on freshly built VM with 5.3.6 to see if just maybe the version is the issue. Seems to literally restart the entire restore each time (but Elapsed time when I do a q restore on the server keeps going up). It loads the first tape, then the second tape, then the third tape, and then dies. ![]() I then restarted it.Įvery time I restart the restore (dsmc restart restore) it starts from the beginning again, and prompts me if I want to overwrite or skip the already restored files. When I checked dsmc q restore, it showed that the restore was restartable. When I checked the server, the restore was inactive. I had to restart the restore several times though, and at one point, the local restore said it was finished, but only a few files were restored. Pretty well the same result with restoring it this time. The other drive I have disabled for now (waiting for IBM warranty). So I'll apply that, reboot the library and the server, take that drive path offline and do the restore with just one drive and see how it goes. I also found a fix pack (5.3.6.2) that hasn't been installed. I'll reboot the tape library, but there's a pretty good chance I might have a faulty drive. Activity log states issues with opening the drive. I brought it back online, and after a few minutes, it took itself back offline. I came into work tonight and the path to the one drive was offline. The node has 2 TB of data in my tape pool, and I don't have any free storage that large. and I have a space issue that prevents me from doing it. Though, am I able to restore data that was backed up by a 5.5.1 client with a 5.3.6 client? I was under the impression that it server/client versions didn't matter all that much, that they'd function at whichever functionality is available from either. Would need to build it but that won't take long (VM template). I can try restoring the data from a 5.3.6 client on a different linux box. The recovery log only gets up to about 3 or 4% usage. The size of the restore is only a couple hundred MB.Īny feedback or advice would be greatly appreciated. Volumes that it needs are all Read-Write access, and are in the library, checked in and all. ![]() There are no other processes or sessions running on TSM. No errors except that the sessions are being interrupted and will attempt to restart. When the client is disconnected, there's a message about the session being severed. ![]() Windows 2k3 32 bit TSM server with TSM 5.3.6ĭsmc restore -pitd= -pitt=07:00:00 -subdir=yes /var/spool/vmail//bj/ae/clientusername/ /home/tsm/restore/clientusername/ĭsmc restore -pitd= -pitt=07:00:00 /var/spool/vmail//bj/ae/clientusername/mdir/* /home/tsm/restore/clientusername/Īs soon as the restore starts or is restarted, it gives me the three volumes that it needs I just cancelled and restarted it with the second command. When I query the backup, it creates a list of files pretty fast. I restart the restore (dsmc restart restore) and even though it claims to be a restartable restore, it seems to start all over again and tries to restore the same files over again, then gets severed, and so on. A couple hours later, the connection is severed. After several hours (18 hours first time) the restore beings, and then after about 9.5 MB, it stops and just sits there. ![]() I'm having some issues restoring some data off of a Centos box running surgemail.
0 Comments
Leave a Reply. |