Hi,
Have you got purge your VSS snapshot ?
vssadmin delete shadows all
Best regards,
Yann
-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de
Robert Ouzen
Envoyé : dimanche 15 septembre 2013 07:08
À : ADSM-L AT VM.MARIST DOT EDU
Objet : [ADSM-L] TDP for Exchange errors
Hello again
I had previously an old environment to backup my Exchange Server ExchsrvB as:
My TSM client version is: 6.2.3.1
My TSN TDP Exchange version is: 6.1.3.2
My TSM server version is: 5.5.5.2 on AIX O.S
My TSM Lanfree version is: 5.5.5.1
Now I made all the configuration to backup it on a new environment as: (Just
change for now the version of the TSM server and O.S)
My TSM client version is: 6.2.3.1
My TSM TDP Exchange version is: 6.1.3.2
My TSM server version is: 6.3.4 on Windows 2008R2 O.S
My TSM Lanfree version is: 5.5.5.1
I succeed to configure all the stuff (Zone, Data Domain configure , devices,
drives , paths , proxy etc ……..)
I check the commands: (Correct results)
Tdpexcc q tsm
Tdpecc q echange
Here output:
Tivoli Storage Manager Server Connection Information
----------------------------------------------------
Nodename ............................... EXCHSRVBN_DB NetWork Host Name of
Server ............ 132.74.XX.XX TSM API Version ........................
Version 6, Release 2, Level 3.1
Server Name ............................ ADSM2 Server Type
............................ Windows Server Version .........................
Version 6, Release 3, Level 4.0 Compression Mode ....................... Client
Determined Domain Name ............................ DOCC Active Policy Set
...................... POCC Default Management Class ............... MGEXCHANGE
Volume Shadow Copy Service (VSS) Information
--------------------------------------------
Writer Name : Microsoft Exchange Writer
Local DSMAgent Node : exchsrvb
Remote DSMAgent Node :
Writer Status : Online
Selectable Components : 46
Two days ago I think I succeed to run a full backup here output:
09/11/2013 17:17:02 ANE4952I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects inspected: 6,967 (SESSION: 1716)
09/11/2013 17:17:02 ANE4954I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects backed up: 6,967 (SESSION: 1716)
09/11/2013 17:17:02 ANE4958I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects updated: 0 (SESSION: 1716)
09/11/2013 17:17:02 ANE4960I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects rebound: 0 (SESSION: 1716)
09/11/2013 17:17:02 ANE4957I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects deleted: 0 (SESSION: 1716)
09/11/2013 17:17:02 ANE4970I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects expired: 0 (SESSION: 1716)
09/11/2013 17:17:02 ANE4959I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of objects failed: 0 (SESSION: 1716)
09/11/2013 17:17:02 ANE4977I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of bytes inspected: 1.07 TB (SESSION: 1716)
09/11/2013 17:17:02 ANE4961I (Session: 1716, Node: EXCHSRVBN_DB) Total
number of bytes transferred: 1.07 TB (SESSION: 1716)
09/11/2013 17:17:02 ANE4971I (Session: 1716, Node: EXCHSRVBN_DB) LanFree
data bytes: 1.00 TB (SESSION:
1716)
09/11/2013 17:17:02 ANE4963I (Session: 1716, Node: EXCHSRVBN_DB) Data
transfer time: 7,593.38 sec (SESSION:
1716)
09/11/2013 17:17:02 ANE4966I (Session: 1716, Node: EXCHSRVBN_DB) Network
data transfer rate: 152,440.87 KB/sec
(SESSION: 1716) 09/11/2013 17:17:02
ANE4967I (Session: 1716, Node: EXCHSRVBN_DB) Aggregate
data transfer rate: 69,078.67 KB/sec (SESSION:
1716)
09/11/2013 17:17:02 ANE4968I (Session: 1716, Node: EXCHSRVBN_DB) Objects
compressed by: 0%% (SESSION: 1716)
09/11/2013 17:17:02 ANE4976I (Session: 1716, Node: EXCHSRVBN_DB) Total
data reduction ratio: 0.00%% (SESSION: 1716)
09/11/2013 17:17:02 ANE4964I (Session: 1716, Node: EXCHSRVBN_DB) Elapsed
processing time: 04:39:16 (SESSION: 1716)
Tried this morning to run a log backup and got those errors: before it check
the vssadmin list witers , everything was Stable and Correct.
After my try now: Microsoft Exchange Writer is:
State: [9] Failed
Last error: Retryable error
I now that that I have to restart the Information Store but what else ?
Errors:
09/15/2013 07:03:59 ANS1577I The Windows console event handler received a
'Ctrl-C' console event.
09/15/2013 07:05:04 ANS1751E Error processing
'\\exchsrvb\c$\exchangedata\restoreold': The file system can not be accessed.
09/15/2013 07:05:21 ANS0361I DIAG: VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2013 07:05:21 ANS5268W The Microsoft Volume Shadow Copy Services writer
'Microsoft Exchange Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not
valid for the current operation.
09/15/2013 07:05:51 ANS0361I DIAG: VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2013 07:05:51 ANS5268W The Microsoft Volume Shadow Copy Services writer
'Microsoft Exchange Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not
valid for the current operation.
09/15/2013 07:06:21 ANS0361I DIAG: VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2013 07:06:21 ANS5268W The Microsoft Volume Shadow Copy Services writer
'Microsoft Exchange Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not
valid for the current operation.
09/15/2013 07:06:52 ANS0361I DIAG: VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2013 07:06:52 ANS5268W The Microsoft Volume Shadow Copy Services writer
'Microsoft Exchange Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not
valid for the current operation.
09/15/2013 07:06:52 ANS5273E A Microsoft Volume Shadow Copy Services writer is
in an invalid state after taking a snapshot.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ac19-Users34\53cec8c4-5fa6-43b8-a3c4-4358fc7c7ab3'
failed with error code: -1.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ad12-Users12\08097b7e-0cd8-45e9-987a-90fe6e349845'
failed with error code: -1.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ac25-Users40\52c7962d-39ce-4fae-b8ce-3abf47fd6a9c'
failed with error code: -1.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ac26-Users41\538b99a6-1681-495c-a094-abeb70c99456'
failed with error code: -1.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ad15-Users15\25888c66-bf7c-4292-8348-df9b68c7f290'
failed with error code: -1.
09/15/2013 07:06:52 ANS5283E The operation was unsuccessful.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ad14-Users14\4296a6ab-18c3-4af5-abd4-fbd1da193002'
failed with error code: 4353.
09/15/2013 07:06:52 ANS4000E Error processing 'EXCHSRVB\Microsoft Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ac20-Users35\7d4b7d91-41bf-4f9c-8585-8ec0b37376e6':
file space does not exist.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ad10-Users10\8063e587-a217-464a-b226-38d4686c6fe4'
failed with error code: -1.
09/15/2013 07:06:52 ANS4000E Error processing 'EXCHSRVB\Microsoft Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ac22-Users37\a974f03c-6be9-4c44-b654-83b3ecaca6b1':
file space does not exist.
09/15/2013 07:06:52 ANS4000E Error processing 'EXCHSRVB\Microsoft Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ac21-Users36\b9aa5093-b3bc-4de9-9ca7-5afe160d02bf':
file space does not exist.
09/15/2013 07:06:52 ANS1327W The snapshot operation for 'EXCHSRVB\Microsoft
Exchange
Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}\Ad11-Users11\fc45a5b8-a6ff-4f33-a793-7f10370fd331'
failed with error code: -1.
09/15/2013 07:06:52 ANS5283E The operation was unsuccessful.
09/15/2013 07:06:52 Filespace not found
09/15/2013 07:06:52 ANS5258E Microsoft volume shadow copy snapshot
initialization failed.
09/15/2013 07:06:52 Filespace not found
09/15/2013 07:06:52 ANS5283E The operation was unsuccessful.
09/15/2013 07:06:52 Filespace not found
09/15/2013 07:06:52 ANS5283E The operation was unsuccessful.
Any advice what to do ?
I plan to upgrade the Tsm Client to 6.4.0 , Tsm Lanfree to 6.3.4 , TDP to
6.4.02 but first need to have a consistent backup for a while
T.I.A Best Regards
Robert
Ce message et toutes les pièces jointes (ci-après le « message ») sont
confidentiels et établis à l’intention exclusive de ses destinataires. Toute
utilisation de ce message non conforme à sa destination, toute diffusion ou
toute publication, totale ou partielle, est interdite, sauf autorisation
expresse. Si vous recevez ce message par erreur, merci de le détruire sans en
conserver de copie et d’en avertir immédiatement l’expéditeur. Internet ne
permettant pas de garantir l’intégrité de ce message, la Caisse des Dépôts et
Consignations décline toute responsabilité au titre de ce message s’il a été
modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les
précautions prises pour éviter la présence de virus dans nos envois, nous vous
recommandons de prendre, de votre côté, les mesures permettant d'assurer la
non-introduction de virus dans votre système informatique.
This email message and any attachments (“the email”) are confidential and
intended only for the recipient(s) indicated. If you are not an intented
recipient, please be advised that any use, dissemination, forwarding or copying
of this email whatsoever is prohibited without Caisse des Depots et
Consignations's prior written consent. If you have received this email in
error, please delete it without saving a copy and notify the sender
immediately. Internet emails are not necessarily secured, and declines
responsibility for any changes that may have been made to this email after it
was sent. While we take all reasonable precautions to ensure that viruses are
not transmitted via emails, we recommend that you take your own measures to
prevent viruses from entering your computer system.
|
