Hi Christian,
It appears you did not run the cmdlet with the flags I requested.
More specifically, you *must* add the "-Status" flag, otherwise
you won't get the actual BackupInProgress setting.
Try this:
Get-Mailboxdatabase -Identity DAG1DB5 -Status | select
Name,BackupInProgress
Thanks,
Bent,
I have been down the road that you are about to travel, only on a smaller scale
(26 sites).
It was however before TSM offered de-duplication but I am sure that's of little
help regarding your initial backup. Some of our sites had 256k lines and a few
had single T1's. All of them had some d
Hi Del,
I'm talking to IBM Level 2 support at the moment but I think they have go home
for the day now in UK.
But the last test we did was to run a couple of PowerShell commands and this is
the output L2 support sow.
2013-01-16 15:18:38.788 [011060] [9320] : TdpExcApi.cpp (11099): Database
if you have TSMs at remote sites you can use export data on tapes and import.
If you do not have TSMs you can use trial TSM to migrate data ...
You can benefit from current installed TSM clients, and will no need
to install different backup client ...
Regards
Chavdar
On Wed, Jan 16, 2013 at 7:14
The only realistic solution to complete what you are trying to do over the wire
is a client side de-duplication solution. In that case you can seed the backup
server with local data.
I did not understand the quantity of sites you had to deal with.
Andy Huebner
-Original Message-
From:
Just on a whim today I had one of the other admins logon to the server and
remove the TSM services, re-add them and change the logon-as for the TSM
Scheduler service. And now it's working.
The first time I logged on as the user that the backup was going to logon as
and added the services. Don't kn
Have you looked at replication of those remote sites as opposed to backup of
the sites directly?
For those sites that could use a storage replication device to replace the
file server (Netapp, Data Domain,...) and replicate it to possibly a central
or hub sites. Then back up from there? Replace th
Andy,
I do not totally agree with you here.
The main issue for us is to get all 107 remote sites converted to TSM
reasonably fast to save maintenance and service fees on the existing backup
solutions. With the laptop server solution we predict the turn-around time for
each laptop to be around
On 01/15/2013 05:56 PM, Alex Paschal wrote:
> Are those 40mil spread across several filespaces? I've seen situations
> on TSM-classic (i.e. pre-6) where doing smaller workloads, like deleting
> one filespace at a time, worked better than deleting the whole node.
> Would that be practical in this c
Hi Christian,
One thing to check is the Exchange database "BackupInProgress" flag.
Data Protection for Exchange utilizes this flag to know whether
a backup is already in progress. I know you said there wasn't,
but if the Exchange Server thinks there is, it won't allow
another to start.
To check t
Hi all,
I have a strange situations I try to understand.
We have 2 x Microsoft Exchange Server 2010 DAG clusters and we have the same
issue on both of them.
We are running TSM Client Version 6.4.0.0 and TSM for Exchange 6.4.0.0 with TSM
Server 6.3.3.0 because of we want to get hold of the new DAG
11 matches
Mail list logo
