We currently perform SQL database backups using TDP (using the tdpsqlc
backup * full command)
We then use Enterprise Manager to run a log backup (using the BACKUP LOG
command) followed by a log shrink job (using the DBCC SHRINKFILE
command)
Is there a way to do all of these within TDP for
Hi Richard,
first, thank you for your reply. You'are absolutly right with the mirrored
filesystem or maybe a clustered system. In fact I'm not sure if it's mirrored
or if it is a Raid 5 system (because I'm not the admin of this system - I have
to ask my colleague). I'm only responsible for
Hi Orville,
thanks for your answer. I have to use tsm for backing up this system. I've also
thought of making image backups of the readonly filesystems. The problem is,
that I don't know at which time a readwrite filesystem (of which I've also to
do daily incremental backups) changed to the
Hi all,
I started to backup my data via encryption from an AIX system via the
following extra lines in the dsm.sys file;
encryptkey save
encryptiontype aes128
include.encrypt/ros/BACKUP/.../*cr_servers_one_year
I've checked the data in TSM and all
I once had the same problem.
A MC isn't valid on a include.encrypt line.
You need two lines:
encryptkey save
encryptiontype aes128
include/ros/BACKUP/.../*cr_servers_one_year
include.encrypt/ros/BACKUP/.../*
One to assign a MC and another to encrypt.
Hi Thomas,
You're right. I added the include line, did a test and it worked
Thanks,
Oscar
UNIX / TSM Administrator | ING Direct
410 Thames Valley Park Drive, Reading, Berkshire, RG6 1RH
Tel: 0118 938 1990 l Email: [EMAIL PROTECTED]
-Original Message-
From: ADSM: Dist Stor Manager
On Jul 4, 2007, at 5:56 AM, Thomas Rupp wrote:
I once had the same problem.
A MC isn't valid on a include.encrypt line.
You need two lines:
encryptkey save
encryptiontype aes128
include/ros/BACKUP/.../*cr_servers_one_year
include.encrypt
Yes, Include.encrypt does not INCLUDE files for backup processing or assign
mgmtclass to files. It only specified files to have
encryption applied to them. I just ran in to a similar problem where a user
wanted to exclude everything on a drive except for a
single directory and have that
I think so (not being an SQL guru I'm now sure what shrink means exactly.)
Look at the TDP for SQL book, there are some parms you can add after the
backup * full that determines whether the log is reset or not.
We currently perform SQL database backups using TDP (using the tdpsqlc
backup *