What's up all *SMers.
It is close to x-mas and I hope you have been a good person so you got any
presents this year also. :)
From one thing to another.
I have a small question for you all.
The scenario is like this.
Day 1:
I have over 400 Windows nodes that run daily backups to our TSM Server.
On Dec 4, 2008, at 4:18 AM, Christian Svensson wrote:
During the backup window and we say that maybe 50% of all our
backups have run successfully and the other half is maybe in
progress or are waiting for their time slot. But middle of the
backup windows does my SAN go down and all my backups
Hi Rich,
Please don't comment our setup. We got much better performance when we moved
from local disk to SAN and we have configure our SAN so it should work perfect.
The issue was a Dell driver issue and nothing with the SAN. But we are still
talking to DELL to understand why this happened.
I
The Journal is extremely finicky. So much so that if you reboot the server
you have to do a completely new backup of the drive the Journal service is
watching so that the db will know what's going on again. Now, for those that
did not backup, if they did not reboot you should be able to just
Expiration takes about 1 hour. DB Backup takes about 1 hour 15 minutes.
Thanks,
Jeremy
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Wanda Prather
Sent: Wednesday, December 03, 2008 7:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L]
Ok, 350GB tsm db backing up in 1 hour? How did you get it that fast?
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Conradt, Jeremy
Sent: donderdag 4 december 2008 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Database size, Split
Hello everyone,
I recently upgraded a TSM AIX 5.3 server to 5.5.1.1 and would like to
begin utilizing the copy pools for our offsite backups. I've been
searching in the 5.5 manuals for good documentation on how to set this up
and then fold it into our DRM plan, but I'm not finding much. Does
Are you mis-reading/writing that info?350GB takes 1-hour to expire and
about the same to backup??
My 190GB DB used to take 48+ hours to run expire (350M objects) and
2-hours for a full backups! With recent cleanup/load balancing by moving
nodes to a new server, the expires are down to
Well, I'd say that you are doing great right now, if you can do a DB backup
of 350 G from a Windows box in an hour and 15 minutes!
The biggest problem you are likely to have, as mentioned, is the time it
takes to do the conversion to 6.1 (or in the unlikely event you have a
problem and need to do
On Dec 4, 2008, at 17:51 , Joni Moyer wrote:
Hello everyone,
I recently upgraded a TSM AIX 5.3 server to 5.5.1.1 and would like to
begin utilizing the copy pools for our offsite backups. I've been
searching in the 5.5 manuals for good documentation on how to set
this up
and then fold it into
Good day all,
The on going saga of Centera backups and now restore attempts using TSM.
I have performed a number of backups of our Centera. 1 full and three
Differentials using the following command.
BACKUP NODE test_cbrm c:\centera mode=differential toc=yes w=y
I am unable to see any of the
Its actually not 350 GB. The actual used size is:
Available Assigned Maximum MaximumPage Total Used Pct
Max.
Space Capacity Extension ReductionSizeUsable Pages Util
Pct
(MB) (MB) (MB) (MB) (bytes) Pages
Util
- -
On Dec 4, 2008, at 17:45 , Bos, Karel wrote:
Ok, 350GB tsm db backing up in 1 hour? How did you get it that fast?
lots of very fast disk, very wide striping? And I guess using stk
t10kb drives of disk to store the backups, since those are the only
two I know that can go this fast
This is the script I use:
ASSUMPTIONS: RMAN is backing-up using the node name ORACLE-NODE-BU
select NODE_NAME,cast(BACKUP_DATE as date) as
BACKUP_DATE,STATE,cast(DEACTIVATE_DATE as date) as DEACTIVATE_DATE,
HL_NAME,LL_NAME from BACKUPS where NODE_NAME='ORACLE-NODE-BU' order by
BACKUP_DATE
If it helps this is our sequence.
4am start backup storage pool
Run DB backup
Eject tapes and do DRM stuff
Start expiration and run single thread migration
After expiration completes increase migration threads
Run reclaim
9pm terminate reclaims
9pm run a spare DB backup.
We move about 3TB per day
My NAS backup scripts looks like
serial
backup node NAS /fs1 mode=full wait=yes
.
backup node NAS /fsx mode=full wait=yes
backup stgpool nasprimary nascopy
The NAS unit backups over the SAN and creates the copies over the SAN.
The NAS unit creates the copy and not TSM
-Original
We are currently running 3 TSM servers at Version 5.5, two on z/OS and
the third on a Solaris 10 box. We have been tasked to combine these
into one.
The current Solaris system is on a Sun V240 w/8GB memory:
Around 400 clients (combined) including a 3TB Exchange system, and a
fairly
If I were going to be in the x86 family, I would move into the larger platforms
with more processors and more PCI-E slots. So the HP DL580 I think would be
your best bet. That will reduce the 5x cost benefit somewhat but provide you
with more flexibility. Consider the IBM x3850 M2 server.
Go the P550 route. I've seen P-series boxes handle 3 to 5 times the
amount of workload an Intel box can handle, and I'm a big fan of Linux.
I know more about Linux than I do AIX. However, you need the right tool
for the job, and the P-series box will do the job, and do it longer.
On heavy I/O
.
The missing 38GB is just simply gone. Wave it goodbye. Disks are cheap -
find something more expensive to worry about.
You will get it back, though, if you ever refill this database with
data. But wait, you say, won't the new data be fragmented too? Sure,
just like it would be if you started
On Dec 4, 2008, at 23:41 , Roger Deschner wrote:
.
The missing 38GB is just simply gone. Wave it goodbye. Disks are
cheap -
find something more expensive to worry about.
ok, I'll have to disagree here. an empty db (and this one is) should
not have 100% fragmentation. And like my test server,
Interesting.. we have a database that's about the same size, but it takes
us 2 hours and 40 minutes to back it up to LTO3. We also have 15K rpm 36GB
drives, in two mirrored RAID5,7 sets (TSM mirroring). SAN is 2Gb
FC. Server is P5 570. Server is not entire idle, but mostly so. Our
database
If you use a windows base client and sign in to the TSM server using a
privilege account.
You will see in the GUI for restore the expansion tab for nodes.
You will see the NAS nodes and then the windows nodes.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Hello all
I am trying to figure out an effective way to get alerted if a backup
job is idle or not proceeding due to a MediaWait state. I want it
to have the smarts to maybe only alert me if it finds the same
successive node has been in the same MediaWait state for a predetermined
period (eg
Try
select * from sessions
and see if that gives you what you need
Steven Harris
Tivoli Storage Manager SME
Backup Recovery Team
Storage Services Group
Cumberland Forest
Phone:
IBM Internal :70-75130 External:02 9407 5130
Mobile: 0422 932 065
It's asynchronous, the software doesn't wait for the write to complete
on the fastback server.
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens steve
sorenson
Verzonden: maandag 1 december 2008 20:20
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L]
True, the fastback exchange software is installed on a machine with
outlook installed on it, it used the outlook connection to inject the
objects back into exchange.
Fastback exchange software does NOT run on the exchange server.
On the exchange server you only have the default (one size fits all)
Larsa,
Fastback doesn't work with 2008 yet, it's XP/2003 only (SP1 and up).
Exchange 2007 works fine with 2003 64bit.
Restoring public folders is no problem.
I can restore data to another server also, as long as I have access on the
domain network.
Restored items from Exchange do come back as
28 matches
Mail list logo
