Friday, November 11, 2005
Sorry I haven't posted in a while.
Today is Friday the end of the first week of the Tivoli crit-sit 198111,082. I was out sick on Tues and Wed so we didn't have our conference call. However, after our call on Monday I updated 2 modules. The first was the TSA client to the latest version as of Monday Nov 7th. The second was an update from Novell called TSAUP18. This updated the files listed at the end of this post.
Since updating the modules/files I ahve experienced the following problems. Monday I started a new restore session that never finished. I kept getting out of disk errors and eventually the sessions timed out. Thursday Chuck and I decided to start over. Chuck created a new node for the locker server called studentlocker. I started a backup session at 10:42 and it finished 19 minutes later. I discovered I had forgotten the -subdir=y option, so I started another backup session using this option and the -tapep=n option at 11:04am Thursday. At 1:25pm Locker abended and I had to restart the server. I took a screen shot and saved the abend log and sent them to Chris. Soon after getting on the conference call, Chris told me to restart the backup session which I did somewhere between 4:00 and 4:30 pm. Thursday night shortly before 8:00 I received a call from the machine room saying Locker was down. I restarted the server via HP's remote access card. I did not want to restart the backup session until Friday morning when I could look at the server more closely while the session was going on.
\6X
MAP3XIDS.NLM 1971 04-09-1999 03:32AM
QMAN.NLM 109158 05-17-2005 11:19AM
SBCON.NLM 374092 05-17-2005 11:23AM
SMDR.NLM 359438 05-17-2005 11:26AM
SME.NLM 185466 05-17-2005 11:20AM
SMSDI.NLM 145173 10-16-2002 12:21AM
SMSSTART.NCF 49 10-05-2004 02:21PM
SMSSTOP.NCF 83 09-02-2004 11:11AM
SMSUT.NLM 82478 05-31-2005 03:40PM
TSAFS.NLM 500890 06-08-2005 04:50PM
TSANDS.NLM 52109 02-03-2004 12:01AM
TSATEST.NLM 87507 10-27-2004 04:19PM
\6X\NLS\4
QMAN.MSG 3048 05-22-2002 12:48AM
SBCON.HLP 41112 06-19-2001 11:47AM
SBCON.MSG 23714 07-22-2003 02:44PM
SMDR.MSG 11714 12-01-2003 01:20PM
SMSDI.MSG 8737 03-22-2002 01:17PM
TSAFS.MSG 14179 11-24-2004 03:00PM
\6X\SCHEMA
SMS.SCH 787 05-28-1998 10:31PM
Today is Friday the end of the first week of the Tivoli crit-sit 198111,082. I was out sick on Tues and Wed so we didn't have our conference call. However, after our call on Monday I updated 2 modules. The first was the TSA client to the latest version as of Monday Nov 7th. The second was an update from Novell called TSAUP18. This updated the files listed at the end of this post.
Since updating the modules/files I ahve experienced the following problems. Monday I started a new restore session that never finished. I kept getting out of disk errors and eventually the sessions timed out. Thursday Chuck and I decided to start over. Chuck created a new node for the locker server called studentlocker. I started a backup session at 10:42 and it finished 19 minutes later. I discovered I had forgotten the -subdir=y option, so I started another backup session using this option and the -tapep=n option at 11:04am Thursday. At 1:25pm Locker abended and I had to restart the server. I took a screen shot and saved the abend log and sent them to Chris. Soon after getting on the conference call, Chris told me to restart the backup session which I did somewhere between 4:00 and 4:30 pm. Thursday night shortly before 8:00 I received a call from the machine room saying Locker was down. I restarted the server via HP's remote access card. I did not want to restart the backup session until Friday morning when I could look at the server more closely while the session was going on.
\6X
MAP3XIDS.NLM 1971 04-09-1999 03:32AM
QMAN.NLM 109158 05-17-2005 11:19AM
SBCON.NLM 374092 05-17-2005 11:23AM
SMDR.NLM 359438 05-17-2005 11:26AM
SME.NLM 185466 05-17-2005 11:20AM
SMSDI.NLM 145173 10-16-2002 12:21AM
SMSSTART.NCF 49 10-05-2004 02:21PM
SMSSTOP.NCF 83 09-02-2004 11:11AM
SMSUT.NLM 82478 05-31-2005 03:40PM
TSAFS.NLM 500890 06-08-2005 04:50PM
TSANDS.NLM 52109 02-03-2004 12:01AM
TSATEST.NLM 87507 10-27-2004 04:19PM
\6X\NLS\4
QMAN.MSG 3048 05-22-2002 12:48AM
SBCON.HLP 41112 06-19-2001 11:47AM
SBCON.MSG 23714 07-22-2003 02:44PM
SMDR.MSG 11714 12-01-2003 01:20PM
SMSDI.MSG 8737 03-22-2002 01:17PM
TSAFS.MSG 14179 11-24-2004 03:00PM
\6X\SCHEMA
SMS.SCH 787 05-28-1998 10:31PM
Thursday, October 27, 2005
OK, so here's a problem. I've just run an incremental for the vol1: volume. It backed up 204 objects for a total of 303.5 KB taking 1:23. I used the following command:
i vol1:home/
This is the command line command to tell TSM that I want an incremental backup of the home directory on vol1: This worked fine.
Trying to continue my testing I tried to restore vol1:/home to the copy: volume, so I issued the command:
res vol1:home/ copy:tsm/
This tells TSM to restore everything it has for vol1:home/ and put it on the copy: volume in a directory called TSM. This didn't work. I got the following error:
"ANS1084 No files have previously been backed up for vol1:home/"
Thinking I may have had a syntax error, I tried restoring sys:system to the copy: volume. I issued:
res sys:system/ copy:/ This worked just fine.
I then tried various other ways to restore the previous vol1: information, but always got the same error.
I have started the restore via the web client although I've been told by TSM support that this isn't the best way to do restores.
i vol1:home/
This is the command line command to tell TSM that I want an incremental backup of the home directory on vol1: This worked fine.
Trying to continue my testing I tried to restore vol1:/home to the copy: volume, so I issued the command:
res vol1:home/ copy:tsm/
This tells TSM to restore everything it has for vol1:home/ and put it on the copy: volume in a directory called TSM. This didn't work. I got the following error:
"ANS1084 No files have previously been backed up for vol1:home/"
Thinking I may have had a syntax error, I tried restoring sys:system to the copy: volume. I issued:
res sys:system/ copy:/ This worked just fine.
I then tried various other ways to restore the previous vol1: information, but always got the same error.
I have started the restore via the web client although I've been told by TSM support that this isn't the best way to do restores.
The TSM incremental finished in 10 minutes. It backed up 78.3 megs.
For reference the last incremental for this volume finished 20:09:02 10/25/05.
There are too many variables to determine with any certainty the huge discrepancy between Veritas and TSM. The test will be repeated this afternoon. Now that I have a baseline, I should be able to get some better reading for everyone.
For reference the last incremental for this volume finished 20:09:02 10/25/05.
There are too many variables to determine with any certainty the huge discrepancy between Veritas and TSM. The test will be repeated this afternoon. Now that I have a baseline, I should be able to get some better reading for everyone.
I have been testing a trial version of veritas. I did a full backup of the live locker data. this morning I did an incremental. This took 37:13 and backed up 4.3 gigs. I am doing the same on the TSM side right now and will post the results later.
For reference, the Full for this volume ended at00:02:42 on the 10/27/05
For reference, the Full for this volume ended at00:02:42 on the 10/27/05
So the backup job that started yesterday has been stopped. TSM has again hogged the cache memory causing me not only to stop the job, but restart the system.
Wednesday, October 26, 2005
I have deleted the home/home dirs that were on the copy and restore volumes.
I have started an incremental of the copy volume.
I have started an incremental of the copy volume.
Tuesday, October 25, 2005
Here is the Restore from the Copy volume to the Restore volume. It completedObjects restored 951,198
Objects Failed 0
71 gigs
2 hrs 2 mins. Data Transfer Time: 4,424.29 sec
Netware Data Transfer Rate: 16,856.59 KB/sec
Aggregate data Transder Rate: 11,261.67 KB/sec
Elapsed Processing Time: 2:02:40
Monday, October 24, 2005
Started the restore of copy to restore via the command line. The last two from the web client didn't start.
Restore process of the copy volume to the restore volume has started.
Friday, October 21, 2005
Another restore has been initiated. I checked to see which tsa nlm's were loaded and the were TSANDS and TSAFS. The latter is the one that is supposed to be used now instead of TSA600.
The three day restore went down. I feel this is because of a cache memory allocator problem. Kevin has been having problems with this when he's been trying restores for CNS.
I just stopped the second dsmc thread that was running - trying to get the backup to run a little faster.
The job is still running. Currently it has backed up about 500 MEGS. This is day 3 of the backup job.
On a side note. I downloaded Veritas and did a backup to disk in about 57 minutes. I realize this is going to disk, but I will test backing up to DLT tape shortly.
On a side note. I downloaded Veritas and did a backup to disk in about 57 minutes. I realize this is going to disk, but I will test backing up to DLT tape shortly.
Thursday, October 20, 2005
Stopped the restore process that was started yesterday. I have just started another restore via the dsmc command line.
The error log had the following at the bottom:
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:12:06 Error -50 sending ht request
10/19/2005 16:12:06 Error writing to http socket.
10/19/2005 19:17:54 ANS1005E TCP/IP read error on socket = 16, errno = 54, reason : 'Connection reset by peer'.
10/19/2005 19:17:55 sessSendVerb: Error sending Verb, rc: -58
10/19/2005 19:17:55 sessSendVerb: Error sending Verb, rc: -58
10/19/2005 19:17:55 Operation stopped by user
10/19/2005 19:17:55 sessSendVerb: Error sending Verb, rc: -58
The "connection reset by peer" is a bit odd. I didn't stop it, so I'm not sure what it's talking about here. Either way, I've started the backup again. I did start two threads from the dsmc command line, but I'm not sure if this will actually give me two threads or not.
The error log had the following at the bottom:
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:08:44 Error -50 sending ht request
10/19/2005 16:08:44 Error writing to http socket.
10/19/2005 16:12:06 Error -50 sending ht request
10/19/2005 16:12:06 Error writing to http socket.
10/19/2005 19:17:54 ANS1005E TCP/IP read error on socket = 16, errno = 54, reason : 'Connection reset by peer'.
10/19/2005 19:17:55 sessSendVerb: Error sending Verb, rc: -58
10/19/2005 19:17:55 sessSendVerb: Error sending Verb, rc: -58
10/19/2005 19:17:55 Operation stopped by user
10/19/2005 19:17:55 sessSendVerb: Error sending Verb, rc: -58
The "connection reset by peer" is a bit odd. I didn't stop it, so I'm not sure what it's talking about here. Either way, I've started the backup again. I did start two threads from the dsmc command line, but I'm not sure if this will actually give me two threads or not.
