Help needed TSM Sharepoint

s_valtchanov

ADSM.ORG Member
Joined
Jul 19, 2007
Messages
15
Reaction score
2
Points
0
PREDATAR Control23

When I use the site level backup the backup always fails on 99 %
I have started the trace logs and here is the output:

INFO 2009-03-12 12:26:22,176 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Write data to tsm successfully. Use time: 1s
INFO 2009-03-12 12:26:24,676 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Begin write data to tsm. higthName: \Farm(w2k8sps33;SharePoint_Config)\PLAN20090309091200\FB20090312122140, lowName: \data31.dat, size: 52428800
INFO 2009-03-12 12:26:26,317 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Write data to tsm successfully. Use time: 1s
INFO 2009-03-12 12:26:27,207 [Thread-16] media.transfer.FileTransferConnection.readHead - <FileHeader type="E" path="http://w2k8sps33/sites/complaint"></FileHeader>
INFO 2009-03-12 12:26:31,145 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Begin write data to tsm. higthName: \Farm(w2k8sps33;SharePoint_Config)\PLAN20090309091200\FB20090312122140, lowName: \data32.dat, size: 52428800
INFO 2009-03-12 12:26:32,973 [Thread-17] media.transfer.BlockReceiver.run - Block receiver thread exist. CurrentSize: 800, freeQueueSize: 362, workingQueueSize: 437
INFO 2009-03-12 12:26:41,395 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Write data to tsm successfully. Use time: 10s
INFO 2009-03-12 12:26:41,442 [Thread-16] media.transfer.FileTransferConnection.readHead - <FileHeader type="E" path="http://w2k8sps33/ssp/admin"></FileHeader>
INFO 2009-03-12 12:26:41,442 [Thread-16] media.transfer.FileTransferConnection.backupClose - Receive from agent. Success=1
INFO 2009-03-12 12:26:41,442 [Thread-16] media.transfer.FileTransferConnection.backupClose - remove serialNo and data writer.
INFO 2009-03-12 12:26:41,442 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Begin write data to tsm. higthName: \Farm(w2k8sps33;SharePoint_Config)\PLAN20090309091200\FB20090312122140, lowName: \data33.dat, size: 21409918
INFO 2009-03-12 12:26:45,082 [Thread-16] data4.dsm.DsmOutputStream.writeToTsm - Write data to tsm successfully. Use time: 3s
INFO 2009-03-12 12:26:45,098 [Thread-16] data4.impl.BackupDataWriterDsm.flushIndexs - name: http://w2k8sps33, siblingLocation: 126
INFO 2009-03-12 12:26:45,098 [Thread-16] data4.impl.BackupDataWriterDsm.flushIndexs - name: http://w2k8sps33/sites/complaint, siblingLocation: 236
INFO 2009-03-12 12:26:45,129 [Thread-16] data4.dsm.DsmOutputStream.close - Close successfully.
INFO 2009-03-12 12:26:45,129 [Thread-16] media.data4.BackupDataLogger.info - Backup faild. JobId: FB20090312122140
 
PREDATAR Control23

The backups are going to diskpool on the TSM Server, but first they are buffered on a disk by the DOCAVE Media Server which is on a machine different from the sharepoint and the TSM Server
 
PREDATAR Control23

The backups are going to diskpool on the TSM Server, but first they are buffered on a disk by the DOCAVE Media Server which is on a machine different from the sharepoint and the TSM Server

By "buffered on a disk" I assume that this is a disk pool that has been defined within TSM server as a primary storage pool. Is this correct?

If this is not the case, correct the storage pool settings and setup for TSM to backup properly.
 
PREDATAR Control23

From the TSM for SharePoint Install Guide:

"In DocAve, by default backup data is saved under the path C:\Program Files\Tivoli\tsm\SharePoint\DocAve4\VaultServer\DocAveMedia\data However, it may not be very convenient to use those default paths, since setup of the system is usually installed on disc
 
PREDATAR Control23

The backups are going to diskpool on the TSM Server, but first they are buffered on a disk by the DOCAVE Media Server which is on a machine different from the sharepoint and the TSM Server

Actually, The Docave Media agents receive data from all the SharePoint farms components and buffers it on a DocAve "Buffer pool".
Data is sent to TSM in a process than can be described as "dsmc i ; sleep x; dsmc i ; sleep ...".
The storage destination is based on the MC set in the option file set-up by DocAve when configuring Physical and logical devices (Located somewhere on the DocAve software directory tree).

We are having awfull perf and trying to understand why .... not an easy task (11MB/sec is not acceptable unfortunately)
 
Top