Folks:
I¹m not well versed in Windows platform specifics, so this question from
one of my customers has me flummoxed - and curious.
The system (³solid state computer with an i3 CPU²) in question will be
dedicated to the backup of a 3rd party NAS device (not NetApp, sadly) so
the TSM client
The first go around failed after about 5-hours with DB2 space shortage. The
V5 has a 260GB DB so I created 4x100GB TSM db file systems. When I got the
failure messages about file system full 2 of them were 100% and the other 2
were at 87%. So we create a 5th and had 500GB of database space. Then
You can do both backups by the TDP for databases, but only legacy backup
can be restored to another server, VSS backup just can be restored at the
same server. If you try to issue a restore you can recover the database
files but never put online in SQL instance.
Best Regards
2014-04-08 23:54
Could you share more details, I'm not sure to understand you
best regards
2014-04-09 8:40 GMT-05:00 Robert Talda r...@cornell.edu:
Folks:
I¹m not well versed in Windows platform specifics, so this question from
one of my customers has me flummoxed - and curious.
The system (³solid
TSM Server Version 7, Release 1, Level 0.0 running on Linux/x86_64
have:
FILETEXTEXIT YES /home/tsminst1/txteventlog/texteventlog.log APPEND
in the dsmserv.opt file
executed
enable ev filetext all node=*
in a command console
and started collecting the information I wanted in the file. No
I'm running 6.3.4 server on AIX. The server is getting to the end of
it's life so we're planning to replace the hardware. I have just about
everything related to TSM installed on SAN disk, besides the stuff that
gets installed in /usr. The last time I did a hardware swap was with TSM
5.5. The
I've done something similar w/ TSM 6.3 on RHEL x86_64, and it's worked. I did a
DB
backup/restore since our DB and active/archive logs are on direct-attach
disks, but otherwise it's the same procedure.
On Wed, Apr 09, 2014 at 03:02:24PM -0500, Kevin Kettner wrote:
I'm running 6.3.4 server on
I have done this recently on Windows, AIX and Linux.
We treated it like a DR exercise and basically installed TSM (same version) on
new hardware.
Made sure I migrated storage pools to 0.
Ran a prepare.
Put the volhist, devconf, dsmserv.opt in the proper place.
Took care of zoning with the
I've also done it this way, treating it as a DR exercise and restoring the DB,
not difficult at all.
Restoring DB very well documented in the V6 cmd ref.
But I realize you wanted to do it without restoring the DB, just importing the
VG.
I could be wrong, but I think it's more complicated now
We have TSM v6.3. On two Windows 2012 64bit servers we have the TDP Storage
Flashcopy manager v3.2.1.0 client.
Both of these servers run MS SQL Server 2012.
I would like to restore databases backed up on one server to the other. The
databases are backed up using the tdpsqlc backup * full
Hi Kevin,
I did follow the below steps on the same server and yet to test on DR server,,,
I have kept TSM DB and Log(active/archive ) in different VG
Configured flash copy ( DS8K)
Note: Tested it when TSM database was running
DB2 has feature called write suspend and it will ensure TSM DB
Hi Francisco
Thanks a lot
Best Regards,
Dhammika
From: Francisco Parrilla francisco.parri...@gmail.com
To: ADSM-L@vm.marist.edu,
Date: 04/09/2014 08:25 PM
Subject:Re: [ADSM-L] TDP for SQL Server - restoring Database to another
server (VSS Backup)
Sent by:
More research and testing on the issue below seems to indicate that I have to
change the backup type from VSS to Legacy to fully enable the Restore Alternate
Location option on the target server.
Thanks Regards
Paul
We have TSM v6.3. On two Windows 2012 64bit servers we have the TDP Storage
13 matches
Mail list logo
