Antwort: Re: [ADSM-L] Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?'copystgpool=[yadda]'

[Alexander Heindl]

yes, I mean 'copystgpool=[yadda]'.
well, I experienced this myself within a PMR.
the problem is the "data movement".
it's not the same, and therefore the pool is removed from the list of
copypools.
sadly have no more detailed information on this, maybe ask IBM...

I'm using nonblocked pools myself as a Content Manager target.

Regards, Alex



Von:"Allen S. Rout" 
An: ADSM-L@VM.MARIST.EDU
Datum:  04.01.2012 20:45
Betreff:Re: [ADSM-L] Antwort: Re: [ADSM-L] Sources of discrepancy
between FILE volume size on disk and reported space?
Gesendet von:   "ADSM: Dist Stor Manager" 



On 01/04/2012 09:17 AM, Alexander Heindl wrote:
> use a nonblocked pool
> (you cannot change this setting - you'll need to move all data)
>
> consider some disadvantages of nonblocked data, e.g. no autocopy with
> "blocked" pools...
>

Could you hit that with a little more detail?  When you say 'autocopy',
I think 'copystgpool=[yadda]'.  But nonblock is specifically allowed for
copystgpool sources.  I don't use copystgpool, but it's of interest
nonetheless.


- Allen S. Rout




smime.p7s
Description: S/MIME Cryptographic Signature

Memory/CPU requirements for TSM 6.2 Storage Agent on AIX

[Steve Harris]

Hi All and a happy 2012 to everyone. May all your DR plans be ready for
Dec 21 ;-)

I'm looking at rolling out a number of storage agents across a SAP
landscape of AIX LPARS over multiple CECs, the plan being to backup
large databases across the AIX virtual network to a storage agent on the
same CEC and from there to VTL.  One monster TSM 6.2 instance will be in
charge.

Looking at the Support web site, the requirements for the storage agent
are nowhere spelled out, there is just a circular loop of page
references.  While I'm waiting for Passport Advantage access to be able
to raise a support ticket against this customer, I thought I'd ask you
guys.  How much memory and CPU do I need for a 6.2 storage agent in its
own AIX lpar?  P6-595s running AIX 6.1

Thanks.

Steve.

Steven Harris
TSM Admin
Canberra Australia

linux client

[Tim Brown]

Does the x86 linux client support SUSE Linux SLES 10 SP2



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the intended 
recipient. If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.

Re: Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?

[Allen S. Rout]

On 01/04/2012 09:17 AM, Alexander Heindl wrote:

use a nonblocked pool
(you cannot change this setting - you'll need to move all data)

consider some disadvantages of nonblocked data, e.g. no autocopy with
"blocked" pools...



Could you hit that with a little more detail?  When you say 'autocopy',
I think 'copystgpool=[yadda]'.  But nonblock is specifically allowed for
copystgpool sources.  I don't use copystgpool, but it's of interest
nonetheless.


- Allen S. Rout

Re: - Exchange 2010 Restores

[Del Hoobler]

Hi Matt,

I am not sure I understand the actual problem you are having,
but you can launch the GUI pointing at a different options file.

For example:

tdpexc /tsmoptfile=XDCUserStore6.opt

If I did not address the problem you are having, please clarify.

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 01/04/2012
07:31:06 AM:

> From: "Leonard, Matthew" 
> To: ADSM-L@vm.marist.edu
> Date: 01/04/2012 07:39 AM
> Subject: - Exchange 2010 Restores
> Sent by: "ADSM: Dist Stor Manager" 
>
> All,
>
> I have a question.  We have a DAG Group in Exchange 2010 which we
> were using the TDP PowerShell script to backup the 12 datastores
> within the DAG, however the Backup would take way too long...and the
> logs would not clear until the entire job was complete.  So now, we
> created 7 separate .CMD Files using the following commands and 7
> different schedules to kick these off.  However, How would I restore
> one of these.  We have a 30 retention time and I can't figure out
> how to open the TDP GUI pointing to these jobs.  I tried the way we
> did it with exchange 2003 using the following shortcut path but it
> did not seem to work properly. ("C:\Program Files\Tivoli\TSM
> \TDPExchange\tdpexc.exe" /excserver=exvs01)
>
> One for each storage group (6 Total):
> tdpexcc backup "XDCUserStore6" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=XDCUserStore6.opt /logfile=C:\TSM
> \excsch_XDCUserStore6.log >> C:\TSM\excfull_XDCUserStore6.log
>
> One for 6 Small Datastores
> tdpexcc backup "XDCExecStore2" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=EXecCrewVendRes.opt /logfile=C:
> \TSM\excsch_EXecCrewVendRes.log >> C:\TSM\excfull_EXecCrewVendRes.log
> tdpexcc backup "XDCExecStore1" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=EXecCrewVendRes.opt /logfile=C:
> \TSM\excsch_EXecCrewVendRes.log >> C:\TSM\excfull_EXecCrewVendRes.log
> tdpexcc backup "XDCCrewStore1" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=EXecCrewVendRes.opt /logfile=C:
> \TSM\excsch_EXecCrewVendRes.log >> C:\TSM\excfull_EXecCrewVendRes.log
> tdpexcc backup "XDCCrewStore2" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=EXecCrewVendRes.opt /logfile=C:
> \TSM\excsch_EXecCrewVendRes.log >> C:\TSM\excfull_EXecCrewVendRes.log
> tdpexcc backup "XDCResStore1" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=EXecCrewVendRes.opt /logfile=C:
> \TSM\excsch_EXecCrewVendRes.log >> C:\TSM\excfull_EXecCrewVendRes.log
> tdpexcc backup "XDCVendorStore" full /BACKUPMETHOD=VSS /
> BACKUPDESTINATION=TSM /tsmoptfile=EXecCrewVendRes.opt /logfile=C:
> \TSM\excsch_EXecCrewVendRes.log >> C:\TSM\excfull_EXecCrewVendRes.log
>
>
> Matthew J. Leonard
> Network Infrastructure Administrator
> AtlasAir Worldwide Holdings
> matthew.leon...@atlasair.com
> Office: 914.701.8715
>

Re: Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?

[Underdown,John William]

Thanks Alex,

that works! it'll save me a TON of space!

is this a great forum or WHAT?!?!?!

On 01/04/2012 09:17 AM, Alexander Heindl wrote:
> use a nonblocked pool
> (you cannot change this setting - you'll need to move all data)
>
> consider some disadvantages of nonblocked data, e.g. no autocopy with
> "blocked" pools...
>
> Regards,
> Alex
>
>
>
>
> Von: "Allen S. Rout" 
> An: ADSM-L@VM.MARIST.EDU
> Datum: 04.01.2012 15:04
> Betreff: Re: [ADSM-L] Sources of discrepancy between FILE volume size on
> disk and reported space?
> Gesendet von: "ADSM: Dist Stor Manager" 
> 
>
>
>
> On 01/04/2012 08:01 AM, Underdown,John William wrote:
>  > i have the same issue with our document-imaging backups. this is due to
>  > zillions of itty-bitty files being backed up, see below. btw, the
>  > TXNGROUPMAX option only applies to files being backed up, not moved or
>  > reclaimed. [...]
>
> Sounds like this could very well be my problem. Thanks!
>
> Shame I can't fix it for extant data. I might not be able to fix it at
> all: if the content managment system sends just a page, or just a
> packet of metadata, the txngroupmax will be irrelevant: transaction
> size = 1. :P
>
>
> - Allen S. Rout
>
>

-
NOTICE: This communication is intended only for the person or
entity to whom it is addressed and may contain confidential,
proprietary, and/or privileged material. Unless you are the
intended addressee, any review, reliance, dissemination,
distribution, copying or use whatsoever of this communication is
strictly prohibited. If you received this in error, please reply
immediately and delete the material from all computers. Email sent
through the Internet is not secure. Do not use email to send us
confidential information such as credit card numbers, PIN numbers,
passwords, Social Security Numbers, Account numbers, or other
important and confidential information.

Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?

[Alexander Heindl]

use a nonblocked pool
(you cannot change this setting - you'll need to move all data)

consider some disadvantages of nonblocked data, e.g. no autocopy with
"blocked" pools...

Regards,
Alex




Von:"Allen S. Rout" 
An: ADSM-L@VM.MARIST.EDU
Datum:  04.01.2012 15:04
Betreff:Re: [ADSM-L] Sources of discrepancy between FILE volume
size on disk and reported space?
Gesendet von:   "ADSM: Dist Stor Manager" 



On 01/04/2012 08:01 AM, Underdown,John William wrote:
> i have the same issue with our document-imaging backups. this is due to
> zillions of itty-bitty files being backed up, see below. btw, the
> TXNGROUPMAX option only applies to files being backed up, not moved or
> reclaimed.  [...]

Sounds like this could very well be my problem.  Thanks!

Shame I can't fix it for extant data.  I might not be able to fix it at
all:  if the content managment system sends just a page, or just a
packet of metadata, the txngroupmax will be irrelevant:  transaction
size = 1. :P


- Allen S. Rout




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Sources of discrepancy between FILE volume size on disk and reported space?

[Allen S. Rout]

On 01/04/2012 08:01 AM, Underdown,John William wrote:

i have the same issue with our document-imaging backups. this is due to
zillions of itty-bitty files being backed up, see below. btw, the
TXNGROUPMAX option only applies to files being backed up, not moved or
reclaimed.  [...]


Sounds like this could very well be my problem.  Thanks!

Shame I can't fix it for extant data.  I might not be able to fix it at
all:  if the content managment system sends just a page, or just a
packet of metadata, the txngroupmax will be irrelevant:  transaction
size = 1. :P


- Allen S. Rout

Re: Sources of discrepancy between FILE volume size on disk and reported space?

[Underdown,John William]

i have the same issue with our document-imaging backups. this is due to 
zillions of itty-bitty files being backed up, see below. btw, the 
TXNGROUPMAX option only applies to files being backed up, not moved or 
reclaimed.

Volume 100% utilized, Estimated Capacity does not meet MAXCAPacity
Technote (FAQ)

Problem
The output from "q vol" on a FILE devclass volume in a TSM 5.3 Server is 
reporting 100% utilized, but the "Estimated Capacity" has not reached 
the MAXCAPacity.

Cause
For example, a FILE devclass named FILEDIR has been set to have a MAX 
Capacity of 64MB but each volume has only been filled to 34MB before 
becoming full:

Output from "q devclass":
Device Device Storage Device Format Est/Max Mount
Class Access Pool Type Capacity Limit
Name Strategy Count (MB)
- -- --- - --  --
FILEDIR Sequential 1 FILE DRIVE 64.0 20

After a backup of small objects, the output from "q vol" will show 
something like:
Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
 --- -- - - 
C:\TSMDATA\SERVER1\DIRM- FILEDIR FILEDIR 34.0 100.0 Full
C\01E6.BFS
C:\TSMDATA\SERVER1\DIRM- FILEDIR FILEDIR 34.0 100.0 Full
C\01E7.BFS

There was a design change to the file devclass in 5.3 where each I/O to 
the a FILE devclass volume will be at least 256K, regardless of how much 
data is being written. Under these conditions, if there is only one 
object backed up that is 500 bytes in size, it will take 256k to store 
it on the FILE devclass volume. This will have the biggest impact when 
backing up small objects (for instance, small files or directories).

Solution
Increasing the aggregate size may help reduce this overhead. This can be 
done by modifying the value for the TXNGROUPMAX on either the TSM Server 
or for this particular node (register/update node). This will make the 
aggregate size larger and less space is wasted with the overhead. Also 
the client option TXNBYTELIMIT may need to be adjusted as well.

NOTE: Increasing the TXNGROUPMAX value will result in increased recovery 
log utilization. Higher recovery log utilization may increase the risk 
of running out of log space. Evaluate each node's performance before 
changing this parameter. For more information on managing the recovery 
log, see the Administrator's Guide.

The results from the query volume may vary by environment. Also check 
the OS to see if the filesize of the volume is equal to the MAXCAPacity. 
If it is not, then APAR IC44597 is also affecting the environment.


On 01/03/2012 02:58 PM, Allen S. Rout wrote:
> So, I've got a passel of document-imaging data whose primary storage is
> on FILE. As you might imagine, it's amazingly static, and as a
> consequence gets little attention. But it just got some, and I'm
> confused by it.
>
> I recently set about moving my TSM infrastructure from the Old Storage
> (emc cx320) to the New Storage (emc VNX). I built new volume groups
> and filesystems, updated my management class to only write to the new
> filesystems, and started a long series of MOVE DATA macros.
>
> As I watched these go by, I was interested by the fact that the move
> processes were reporting less than 5G moved, sometimes substantially. I
> figured I'd neglected to set reclaim thresholds on this data, d'oh. So
> I was getting an opportunity to reclaim the whole dang infrastructure.
> how nice! I started counting space savings before it was hatched.
>
>
> So now the move is done, and I've got my 4.mumble TB of data all moved
> to brand new 5G volumes, none of which existed a month ago, all of which
> were populated by
>
> MOVE DATA [foo] reconst=yes
>
> and none of which have any reclaimable space
>
> tsm: VI>select pct_utilized,pct_reclaim,count(*) from volumes where
> devclass_name='MED FILE' group by pct_utilized,pct_reclaim
>
> PCT_UTILIZED PCT_RECLAIM Unnamed[3]
>  --- ---
> 6.1 0.0 1
> 100.0 0.0 848
>
>
> but the ESTCAP of these volumes is pretty far off 5G. Here's a
> histogram-like list of them, counted by GB of ESTCAP.
>
>
> 1 1.3
> 1 1.5
> 2 1.6
> 4 1.7
> 8 1.8
> 16 1.9
> 20 2.0
> 39 2.1
> 37 2.2
> 44 2.3
> 35 2.4
> 53 2.5
> 51 2.6
> 52 2.7
> 40 2.8
> 60 2.9
> 56 3.0
> 44 3.1
> 46 3.2
> 61 3.3
> 152 3.4
> 14 3.5
> 6 3.6
> 3 3.7
> 1 3.9
> 2 4.0
> 1 5.0
>
>
> So, what am I missing? I feel like a bozo, but I can't come up with a
> reason a full 5G volume would have an ESTCAP of 1.3G with no reclaimable
> space.
>
>
> - Allen S. Rout

-
NOTICE: This communication is intended only for the person or
entity to whom it is addressed and may contain confidential,
proprietary, and/or privileged material. Unless you are the
intended addressee, any review, reliance, dissemination,
distribution, copying or use whatsoever of this communication is
strictly prohibited. If you received this in error, please reply
immediately and delete the ma

- Exchange 2010 Restores

[Leonard, Matthew]

All,

I have a question.  We have a DAG Group in Exchange 2010 which we were using 
the TDP PowerShell script to backup the 12 datastores within the DAG, however 
the Backup would take way too long...and the logs would not clear until the 
entire job was complete.  So now, we created 7 separate .CMD Files using the 
following commands and 7 different schedules to kick these off.  However, How 
would I restore one of these.  We have a 30 retention time and I can't figure 
out how to open the TDP GUI pointing to these jobs.  I tried the way we did it 
with exchange 2003 using the following shortcut path but it did not seem to 
work properly. ("C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.exe" 
/excserver=exvs01)

One for each storage group (6 Total):
tdpexcc backup "XDCUserStore6" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=XDCUserStore6.opt /logfile=C:\TSM\excsch_XDCUserStore6.log >> 
C:\TSM\excfull_XDCUserStore6.log

One for 6 Small Datastores
tdpexcc backup "XDCExecStore2" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=EXecCrewVendRes.opt /logfile=C:\TSM\excsch_EXecCrewVendRes.log >> 
C:\TSM\excfull_EXecCrewVendRes.log
tdpexcc backup "XDCExecStore1" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=EXecCrewVendRes.opt /logfile=C:\TSM\excsch_EXecCrewVendRes.log >> 
C:\TSM\excfull_EXecCrewVendRes.log
tdpexcc backup "XDCCrewStore1" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=EXecCrewVendRes.opt /logfile=C:\TSM\excsch_EXecCrewVendRes.log >> 
C:\TSM\excfull_EXecCrewVendRes.log
tdpexcc backup "XDCCrewStore2" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=EXecCrewVendRes.opt /logfile=C:\TSM\excsch_EXecCrewVendRes.log >> 
C:\TSM\excfull_EXecCrewVendRes.log
tdpexcc backup "XDCResStore1" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=EXecCrewVendRes.opt /logfile=C:\TSM\excsch_EXecCrewVendRes.log >> 
C:\TSM\excfull_EXecCrewVendRes.log
tdpexcc backup "XDCVendorStore" full /BACKUPMETHOD=VSS /BACKUPDESTINATION=TSM 
/tsmoptfile=EXecCrewVendRes.opt /logfile=C:\TSM\excsch_EXecCrewVendRes.log >> 
C:\TSM\excfull_EXecCrewVendRes.log


Matthew J. Leonard
Network Infrastructure Administrator
AtlasAir Worldwide Holdings
matthew.leon...@atlasair.com
Office: 914.701.8715

Re: How to run a manual Exchange backup ?

[Minns, Farren - Chichester]

Many thanks Del

Farren




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del 
Hoobler
Sent: 04 January 2012 11:56
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to run a manual Exchange backup ?

Almost correct, but not quite. Here is the correct syntax:



tdpexcc backup "4B StorageGroup" incr /tsmoptfile=dsm.opt
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 01/04/2012
06:40:27 AM:

> From: "Minns, Farren - Chichester" 
> To: ADSM-L@vm.marist.edu
> Date: 01/04/2012 06:42 AM
> Subject: How to run a manual Exchange backup ?
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi all,
>
>
>
> I need to run a full exchange backup against just one Exchange storage
group.
>
>
>
> The current command that backs up all groups is as follows :-
>
>
>
> tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /
> excserver=chi-mb >> excincr.log
>
>
>
> To back up just one group (in this case called 4B StorageGroup), can
> I just run the following ?
>
>
>
> tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt /
> logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log
>
>
>
> Regards
>
>
>
> Farren


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.

Re: How to run a manual Exchange backup ?

[Del Hoobler]

Almost correct, but not quite. Here is the correct syntax:



tdpexcc backup "4B StorageGroup" incr /tsmoptfile=dsm.opt
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 01/04/2012
06:40:27 AM:

> From: "Minns, Farren - Chichester" 
> To: ADSM-L@vm.marist.edu
> Date: 01/04/2012 06:42 AM
> Subject: How to run a manual Exchange backup ?
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi all,
>
>
>
> I need to run a full exchange backup against just one Exchange storage
group.
>
>
>
> The current command that backs up all groups is as follows :-
>
>
>
> tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /
> excserver=chi-mb >> excincr.log
>
>
>
> To back up just one group (in this case called 4B StorageGroup), can
> I just run the following ?
>
>
>
> tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt /
> logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log
>
>
>
> Regards
>
>
>
> Farren

Re: How to run a manual Exchange backup (I was being an idiot)

[Minns, Farren - Chichester]

Actually, everyone please ignore me, I'm being an idiot!

Very early start and not enough coffee. I can indeed select the type of backup 
on the GUI.

Forgive me! :-)

And many thanks.

Farren







-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Bos, 
Karel
Sent: 04 January 2012 11:42
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] How to run a manual Exchange backup ?

What abt just firing off the GUI and select the group u want?


-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Minns, Farren 
- Chichester
Verzonden: woensdag 4 januari 2012 12:40
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: How to run a manual Exchange backup ?

Hi all,



I need to run a full exchange backup against just one Exchange storage group.



The current command that backs up all groups is as follows :-



tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /excserver=chi-mb 
>> excincr.log



To back up just one group (in this case called 4B StorageGroup), can I just run 
the following ?



tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Regards



Farren


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.







Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.

Re: How to run a manual Exchange backup ?

[Minns, Farren - Chichester]

Hi,

Well I was going to but because I don't get an option for full or incr etc 
(just Legacy backup), I wasn't sure if it was sufficient?

Also I see that I have made two errors in that I meant to specify full not 
incr. This was a mere typo :-)

Farren




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Bos, 
Karel
Sent: 04 January 2012 11:42
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] How to run a manual Exchange backup ?

What abt just firing off the GUI and select the group u want?


-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Minns, Farren 
- Chichester
Verzonden: woensdag 4 januari 2012 12:40
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: How to run a manual Exchange backup ?

Hi all,



I need to run a full exchange backup against just one Exchange storage group.



The current command that backs up all groups is as follows :-



tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /excserver=chi-mb 
>> excincr.log



To back up just one group (in this case called 4B StorageGroup), can I just run 
the following ?



tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Regards



Farren


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.







Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.

Re: How to run a manual Exchange backup ?

[Minns, Farren - Chichester]

And of course I meant


tdpexcc backup '4B StorageGroup' incr /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns, 
Farren - Chichester
Sent: 04 January 2012 11:40
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to run a manual Exchange backup ?

Hi all,



I need to run a full exchange backup against just one Exchange storage group.



The current command that backs up all groups is as follows :-



tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /excserver=chi-mb 
>> excincr.log



To back up just one group (in this case called 4B StorageGroup), can I just run 
the following ?



tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Regards



Farren


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.



John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.

Re: How to run a manual Exchange backup ?

[Bos, Karel]

What abt just firing off the GUI and select the group u want?


-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Minns, Farren 
- Chichester
Verzonden: woensdag 4 januari 2012 12:40
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: How to run a manual Exchange backup ?

Hi all,



I need to run a full exchange backup against just one Exchange storage group.



The current command that backs up all groups is as follows :-



tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /excserver=chi-mb 
>> excincr.log



To back up just one group (in this case called 4B StorageGroup), can I just run 
the following ?



tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Regards



Farren


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.







Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762

How to run a manual Exchange backup ?

[Minns, Farren - Chichester]

Hi all,



I need to run a full exchange backup against just one Exchange storage group.



The current command that backs up all groups is as follows :-



tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /excserver=chi-mb 
>> excincr.log



To back up just one group (in this case called 4B StorageGroup), can I just run 
the following ?



tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb >> excincr_4B.log



Regards



Farren


John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.