IdentifiantMot de passe
Loading...
Mot de passe oublié ?Je m'inscris ! (gratuit)
Navigation

Inscrivez-vous gratuitement
pour pouvoir participer, suivre les réponses en temps réel, voter pour les messages, poser vos propres questions et recevoir la newsletter

Administration SQL Server Discussion :

Impact des sauvegardes sur les journaux de transaction


Sujet :

Administration SQL Server

  1. #1
    Membre régulier
    Profil pro
    Inscrit en
    Avril 2009
    Messages
    217
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Avril 2009
    Messages : 217
    Points : 112
    Points
    112
    Par défaut Impact des sauvegardes sur les journaux de transaction
    Bonjour,
    J'effectue quotidiennement une sauvegarde complete de mes bases via la commande BACKUP DATABASE WITH FORMAT.
    Je constate que les fichiers .ldf de mes bases ne grossissent pas : est ce que la sauvegarde a un impact sur la taille de ces fichiers?

    Merci d'avance

    Frédéric

  2. #2
    Rédacteur

    Avatar de SQLpro
    Homme Profil pro
    Expert bases de données / SQL / MS SQL Server / Postgresql
    Inscrit en
    Mai 2002
    Messages
    21 768
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Localisation : France, Var (Provence Alpes Côte d'Azur)

    Informations professionnelles :
    Activité : Expert bases de données / SQL / MS SQL Server / Postgresql
    Secteur : Conseil

    Informations forums :
    Inscription : Mai 2002
    Messages : 21 768
    Points : 52 577
    Points
    52 577
    Billets dans le blog
    5
    Par défaut
    Oui et non. Tout dépend du mode de journalisation (RECOVERY MODE).
    Si simple le journal est recyclé en permanence, donc croissance nulle ou très faible.
    Si BULK LOGGED ou FULL, alors croissance du JT, que seul une sauvegarde transactionnelle peut contenir.

    A +
    Frédéric Brouard - SQLpro - ARCHITECTE DE DONNÉES - expert SGBDR et langage SQL
    Le site sur les SGBD relationnels et le langage SQL: http://sqlpro.developpez.com/
    Blog SQL, SQL Server, SGBDR : http://blog.developpez.com/sqlpro
    Expert Microsoft SQL Server - M.V.P. (Most valuable Professional) MS Corp.
    Entreprise SQL SPOT : modélisation, conseils, audit, optimisation, formation...
    * * * * * Expertise SQL Server : http://mssqlserver.fr/ * * * * *

  3. #3
    Membre régulier
    Profil pro
    Inscrit en
    Avril 2009
    Messages
    217
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Avril 2009
    Messages : 217
    Points : 112
    Points
    112
    Par défaut
    Merci,
    C'est bizarre j'ai un Mode de récupération complet et pourtant mon fichier ldf ne grossit pas, 100 Mo pour un fichier mdf de 5 Go.
    Quel autre paramètre pourrait expliquer que le log ne grossit pas ?

    Frédéric

  4. #4
    Expert éminent sénior
    Avatar de mikedavem
    Homme Profil pro
    Administrateur de base de données
    Inscrit en
    Août 2005
    Messages
    5 450
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Âge : 45
    Localisation : France, Ain (Rhône Alpes)

    Informations professionnelles :
    Activité : Administrateur de base de données
    Secteur : Distribution

    Informations forums :
    Inscription : Août 2005
    Messages : 5 450
    Points : 12 891
    Points
    12 891
    Par défaut
    Si ton journal ne grossit pas il se peut que l'activité de ton serveur ne soit pas consommateur en terme d'écriture de transaction.

    - Quelles sont les applications qui tournent sur ton serveur SQL ? Est-ce que ces applications mettent à jour des données ou font elles uniquement des lectures de données ?
    - Est-ce que tu as des tâches de maintenance qui tournent sur le serveur SQL ?
    - Est-ce que tu n'aurais pas un outil tiers qui viendrait faire une sauvegarde ?

    Tu peux surveiller l'évolution d'occupation de ton journal en utilisant la commande DBCC SQLPERF(LOGSPACE) ou en visualisant le rapport "disk usage" pour la base de données concernée

    ++

  5. #5
    Membre éprouvé
    Homme Profil pro
    Administrateur de base de données
    Inscrit en
    Août 2009
    Messages
    623
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Localisation : France

    Informations professionnelles :
    Activité : Administrateur de base de données

    Informations forums :
    Inscription : Août 2009
    Messages : 623
    Points : 1 049
    Points
    1 049
    Par défaut
    Soit le journal de transaction est vidé par une sauvegarde régulière (BACKUP LOG) soit il n'y a pas d'activité

    Edit : Grilled par mikedavem et en plus il explique mieux
    Blog Perso | Kankuru (logiciel gratuit pour SQL Server)

  6. #6
    Membre régulier
    Profil pro
    Inscrit en
    Avril 2009
    Messages
    217
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Avril 2009
    Messages : 217
    Points : 112
    Points
    112
    Par défaut
    - Quelles sont les applications qui tournent sur ton serveur SQL ? Est-ce que ces applications mettent à jour des données ou font elles uniquement des lectures de données ?
    => Les applications font des mises à jour massives de données, c'est pour ça que je suis étonné que le log soit si petit
    - Est-ce que tu as des tâches de maintenance qui tournent sur le serveur SQL ?
    => Oui
    - Est-ce que tu n'aurais pas un outil tiers qui viendrait faire une sauvegarde ?
    => Non

    Frédéric

  7. #7
    Expert éminent sénior
    Avatar de mikedavem
    Homme Profil pro
    Administrateur de base de données
    Inscrit en
    Août 2005
    Messages
    5 450
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Âge : 45
    Localisation : France, Ain (Rhône Alpes)

    Informations professionnelles :
    Activité : Administrateur de base de données
    Secteur : Distribution

    Informations forums :
    Inscription : Août 2005
    Messages : 5 450
    Points : 12 891
    Points
    12 891
    Par défaut
    Dans ce cas si tu es en vraiment mode de récupération FULL et que tu ne fais aucune sauvegarde du journal toi même ton journal devrait grossir sans être vidé. Maintenant à voir depuis quand tournent tes applications .. il se faut que cela soit normal que pour le moment ton journal ne grossisse pas plus que cela ... à vérifier

    Que donne la commande suivante :

    Est-ce que dans le journal des erreurs SQL tu ne verrais pas des lignes qui concernent des sauvegardes des journaux de transactions par hasard ?

    Sinon il ne te reste plus qu'à surveiller l'évolution de la quantité de données dans ton journal et voir quand est-ce que celui se vide et corréler cela avec ce qui pourrait vider ton journal. Mais encore une fois le seul moyen de vider le journal et d'éviter que celui-ci grossisse lorsqu'on utilise un mode de récupération FULL est une sauvegarde explicite du journal des transactions.

    ++

  8. #8
    Membre régulier
    Profil pro
    Inscrit en
    Avril 2009
    Messages
    217
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Avril 2009
    Messages : 217
    Points : 112
    Points
    112
    Par défaut
    Maintenant à voir depuis quand tournent tes applications
    Le fichier ldf a été créé le 4/11/2011

    Que donne la commande suivante :
    Voici le résultat de la commande :

    master 1,242188 55,97484 0
    tempdb 0,7421875 47,36842 0
    model 0,7421875 62,63158 0
    msdb 3,367188 28,30626 0
    ReportServer 6,242188 17,67053 0
    ReportServerTempDB 0,8046875 43,20388 0
    BASE1 109,7422 24,76285 0
    BASE2 132,8672 4,907538 0
    BEST 0,9921875 55,36417 0
    BASE3 30,99219 13,36022 0
    Est-ce que dans le journal des erreurs SQL tu ne verrais pas des lignes qui concernent des sauvegardes des journaux de transactions par hasard ?
    Comment puis je voir ça ?

    Frédéric

  9. #9
    Expert éminent sénior
    Avatar de mikedavem
    Homme Profil pro
    Administrateur de base de données
    Inscrit en
    Août 2005
    Messages
    5 450
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Âge : 45
    Localisation : France, Ain (Rhône Alpes)

    Informations professionnelles :
    Activité : Administrateur de base de données
    Secteur : Distribution

    Informations forums :
    Inscription : Août 2005
    Messages : 5 450
    Points : 12 891
    Points
    12 891
    Par défaut
    Comment puis je voir ça ?
    Dans SQL Server Management Studio > nœud management > SQL Server Error log

    ou

    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    EXEC xp_readerrorlog;
    GO
    A tout hasard tu peux nous donner le résultat de cette requête :

    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    SELECT 
     name,
     recovery_model_desc,
     log_reuse_wait_desc
    FROM sys.databases
    WHERE database_id > 4
    ++

  10. #10
    Membre régulier
    Profil pro
    Inscrit en
    Avril 2009
    Messages
    217
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Avril 2009
    Messages : 217
    Points : 112
    Points
    112
    Par défaut
    EXEC xp_readerrorlog;
    GO
    Donne :
    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    100
    101
    102
    103
    104
    105
    106
    107
    108
    109
     
    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)    Apr  2 2010 15:48:46    Copyright (c) Microsoft Corporation   Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (Hypervisor)  
    (c) Microsoft Corporation.
    All rights reserved.
    Server process ID is 1188.
    System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
    Authentication mode is MIXED.
    Logging SQL Server messages in file 'D:\Data_SQL\MSSQL10_50.CG04\MSSQL\Log\ERRORLOG'.
    This instance of SQL Server last reported using a process ID of 1220 at 21/05/2013 02:00:06 (local) 21/05/2013 00:00:06 (UTC). This is an informational message only; no user action is required.
    Registry startup parameters:     -d D:\Data_SQL\MSSQL10_50.CG04\MSSQL\DATA\master.mdf    -e D:\Data_SQL\MSSQL10_50.CG04\MSSQL\Log\ERRORLOG    -l D:\Data_SQL\MSSQL10_50.CG04\MSSQL\DATA\mastlog.ldf
    SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    Detected 4 CPUs. This is an informational message; no user action is required.
    Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    Starting up database 'master'.
    Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    SQL Trace ID 1 was started by login "sa".
    Starting up database 'mssqlsystemresource'.
    The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    Starting up database 'model'.
    Server name is 'SERVER'. This is an informational message only. No user action is required.
    Clearing tempdb database.
    A self-generated certificate was successfully loaded for encryption.
    Server is listening on [ 'any' <ipv6> 1433].
    Server is listening on [ 'any' <ipv4> 1433].
    Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
    Server is listening on [ ::1 <ipv6> 1434].
    Server is listening on [ 127.0.0.1 <ipv4> 1434].
    Dedicated admin connection support was established for listening locally on port 1434.
    Starting up database 'tempdb'.
    The Service Broker protocol transport is disabled or not configured.
    The Database Mirroring protocol transport is disabled or not configured.
    Service Broker manager has started.
    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVER.cg.ahp ] for the SQL Server service. 
    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVER.cg.ahp:1433 ] for the SQL Server service. 
    SQL Server is now ready for client connections. This is an informational message; no user action is required.
    Erreur*: 18456, Gravité*: 14, État*: 38.
    Login failed for user 'AUTORITE NT\SERVICE RÉSEAU'. Raison*: impossible d'ouvrir la base de données spécifiée explicitement. [CLIENT*: <local machine>]
    Erreur*: 18456, Gravité*: 14, État*: 38.
    Login failed for user 'AUTORITE NT\SERVICE RÉSEAU'. Raison*: impossible d'ouvrir la base de données spécifiée explicitement. [CLIENT*: <local machine>]
    A new instance of the full-text filter daemon host process has been successfully started.
    Starting up database 'BASE_PROD'.
    Starting up database 'msdb'.
    Starting up database 'ReportServerTempDB'.
    Starting up database 'BASE2'.
    Starting up database 'BASE3'.
    Starting up database 'ReportServer'.
    Starting up database 'BASE_TEST'.
    CHECKDB for database 'BASE_TEST' finished without errors on 2011-12-08 17:35:55.650 (local time). This is an informational message only; no user action is required.
    CHECKDB for database 'BASE_PROD' finished without errors on 2011-12-08 17:35:55.650 (local time). This is an informational message only; no user action is required.
    Recovery is complete. This is an informational message only. No user action is required.
    Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    Starting up database 'BASE_TEST'.
    The database 'BASE_TEST' is marked RESTORING and is in a state that does not allow recovery to be run.
    Starting up database 'BASE_TEST'.
    CHECKDB for database 'BASE_TEST' finished without errors on 2011-12-08 17:35:55.650 (local time). This is an informational message only; no user action is required.
    Restore is complete on database 'BASE_TEST'.  The database is now available.
    Database was restored: Database: BASE_TEST, creation date(time): 2011/11/04(12:00:31), first LSN: 44951:2495:149, last LSN: 44951:2557:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak'}). Informational message. No user action required.
    Database backed up. Database: BASE3, creation date(time): 2012/03/16(14:27:56), pages dumped: 2201, first LSN: 1882:170:36, last LSN: 1882:186:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE3\BASE3_backup.bak'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE2, creation date(time): 2011/11/04(16:47:10), pages dumped: 48266, first LSN: 17939:81:67, last LSN: 17939:109:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE2\BASE2_backup.bak'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE_PROD, creation date(time): 2011/11/04(12:00:31), pages dumped: 600986, first LSN: 44966:3216:17, last LSN: 44966:3224:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak'}). This is an informational message only. No user action is required.
    I/O is frozen on database BASE3. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database BASE2. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database ReportServer. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database ReportServerTempDB. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database BASE_PROD. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database BASE_TEST. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    I/O was resumed on database BASE_TEST. No user action is required.
    I/O was resumed on database BASE_PROD. No user action is required.
    I/O was resumed on database ReportServer. No user action is required.
    I/O was resumed on database msdb. No user action is required.
    I/O was resumed on database ReportServerTempDB. No user action is required.
    I/O was resumed on database model. No user action is required.
    I/O was resumed on database BASE2. No user action is required.
    I/O was resumed on database master. No user action is required.
    I/O was resumed on database BASE3. No user action is required.
    Database backed up. Database: BASE2, creation date(time): 2011/11/04(16:47:10), pages dumped: 48250, first LSN: 17939:167:67, last LSN: 17939:195:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}2'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE3, creation date(time): 2012/03/16(14:27:56), pages dumped: 2137, first LSN: 1882:196:36, last LSN: 1882:212:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}1'}). This is an informational message only. No user action is required.
    Database backed up. Database: master, creation date(time): 2013/05/21(02:00:47), pages dumped: 379, first LSN: 652:400:88, last LSN: 652:448:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}9'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE_PROD, creation date(time): 2011/11/04(12:00:31), pages dumped: 600897, first LSN: 44966:3233:37, last LSN: 44966:3249:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}7'}). This is an informational message only. No user action is required.
    Database backed up. Database: ReportServerTempDB, creation date(time): 2011/10/13(14:30:53), pages dumped: 177, first LSN: 42:199:37, last LSN: 42:215:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}6'}). This is an informational message only. No user action is required.
    Database backed up. Database: msdb, creation date(time): 2010/04/02(17:35:08), pages dumped: 3146, first LSN: 669:152:44, last LSN: 669:184:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}4'}). This is an informational message only. No user action is required.
    Database backed up. Database: ReportServer, creation date(time): 2011/10/13(14:30:52), pages dumped: 417, first LSN: 74:530:37, last LSN: 74:546:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}5'}). This is an informational message only. No user action is required.
    Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 178, first LSN: 87:400:37, last LSN: 87:424:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}3'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE_TEST, creation date(time): 2011/11/04(12:00:09), pages dumped: 614842, first LSN: 45091:3798:74, last LSN: 45091:3829:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C95A4BD-A925-4466-866B-B2795E510171}8'}). This is an informational message only. No user action is required.
    Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 87:304:1, last LSN: 87:464:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This is an informational message only. No user action is required.
    Log was backed up. Database: ReportServer, creation date(time): 2011/10/13(14:30:52), first LSN: 74:508:1, last LSN: 74:555:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This is an informational message only. No user action is required.
    Log was backed up. Database: BASE_PROD, creation date(time): 2011/11/04(12:00:31), first LSN: 44951:2592:1, last LSN: 44966:3259:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This is an informational message only. No user action is required.
    Log was backed up. Database: BASE_TEST, creation date(time): 2011/11/04(12:00:09), first LSN: 44951:2557:1, last LSN: 45091:3839:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This is an informational message only. No user action is required.
    Log was backed up. Database: BASE3, creation date(time): 2012/03/16(14:27:56), first LSN: 1882:148:1, last LSN: 1882:222:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This is an informational message only. No user action is required.
    This instance of SQL Server has been using a process ID of 1188 since 21/05/2013 02:00:57 (local) 21/05/2013 00:00:57 (UTC). This is an informational message only; no user action is required.
    Erreur*: 18456, Gravité*: 14, État*: 8.
    Login failed for user 'sa'. Raison*: le mot de passe ne correspond pas à la connexion spécifiée. [CLIENT*: <local machine>]
    Erreur*: 18456, Gravité*: 14, État*: 8.
    Login failed for user 'sa'. Raison*: le mot de passe ne correspond pas à la connexion spécifiée. [CLIENT*: <local machine>]
    Database backed up. Database: BASE3, creation date(time): 2012/03/16(14:27:56), pages dumped: 2201, first LSN: 1882:224:36, last LSN: 1882:240:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE3\BASE3_backup.bak'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE2, creation date(time): 2011/11/04(16:47:10), pages dumped: 48266, first LSN: 17946:488:67, last LSN: 17946:516:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE2\BASE2_backup.bak'}). This is an informational message only. No user action is required.
    Database backed up. Database: BASE_PROD, creation date(time): 2011/11/04(12:00:31), pages dumped: 601114, first LSN: 44978:557:46, last LSN: 44978:577:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak'}). This is an informational message only. No user action is required.
    This instance of SQL Server has been using a process ID of 1188 since 21/05/2013 02:00:57 (local) 21/05/2013 00:00:57 (UTC). This is an informational message only; no user action is required.
    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
     
    ELECT 
     name,
     recovery_model_desc,
     log_reuse_wait_desc
    FROM sys.DATABASES
    WHERE database_id > 4
    Donne :
    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
     
    ReportServer	FULL	NOTHING
    ReportServerTempDB	SIMPLE	NOTHING
    BASE_PROD	FULL	LOG_BACKUP
    BASE_TEST	FULL	NOTHING
    BASE2	SIMPLE	NOTHING
    BASE3	FULL	NOTHING
    Frédéric

  11. #11
    Expert éminent sénior
    Avatar de mikedavem
    Homme Profil pro
    Administrateur de base de données
    Inscrit en
    Août 2005
    Messages
    5 450
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Âge : 45
    Localisation : France, Ain (Rhône Alpes)

    Informations professionnelles :
    Activité : Administrateur de base de données
    Secteur : Distribution

    Informations forums :
    Inscription : Août 2005
    Messages : 5 450
    Points : 12 891
    Points
    12 891
    Par défaut
    Visiblement tu utilises un outil tiers qui réalise :

    - Des backups FULL de tes bases
    - Des backups LOG de tes bases
    - Un snapshot de tes bases


    Dans les logs on peut voir cela concernant le backup des logs :

    Log was backed up. DATABASE: model, creation date(time): 2003/04/08(09:13:36), first LSN: 87:304:1, last LSN: 87:464:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This IS an informational message only. No user action IS required.
    Log was backed up. DATABASE: ReportServer, creation date(time): 2011/10/13(14:30:52), first LSN: 74:508:1, last LSN: 74:555:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This IS an informational message only. No user action IS required.
    Log was backed up. DATABASE: BASE_PROD, creation date(time): 2011/11/04(12:00:31), first LSN: 44951:2592:1, last LSN: 44966:3259:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This IS an informational message only. No user action IS required.
    Log was backed up. DATABASE: BASE_TEST, creation date(time): 2011/11/04(12:00:09), first LSN: 44951:2557:1, last LSN: 45091:3839:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This IS an informational message only. No user action IS required.
    Log was backed up. DATABASE: BASE3, creation date(time): 2012/03/16(14:27:56), first LSN: 1882:148:1, last LSN: 1882:222:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'NUL'}). This IS an informational message only. No user action IS required.

    ++

  12. #12
    Membre éprouvé
    Homme Profil pro
    Administrateur de base de données
    Inscrit en
    Août 2009
    Messages
    623
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Localisation : France

    Informations professionnelles :
    Activité : Administrateur de base de données

    Informations forums :
    Inscription : Août 2009
    Messages : 623
    Points : 1 049
    Points
    1 049
    Par défaut
    Essaye cette requête pour voir l'historique des sauvegardes pour une base donnée :
    Code sql : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    DECLARE @DATABASENAME varchar(128)
    SET @DATABASENAME = 'BASE1'
     
    SELECT s.database_name,
        m.physical_device_name,
        CAST(CAST(s.backup_size / 1000000 AS INT) AS VARCHAR(14)) + ' ' + 'MB' AS bkSize,
        CAST(DATEDIFF(second, s.backup_start_date,
        s.backup_finish_date) AS VARCHAR(4)) + ' ' + 'Seconds' TimeTaken,
        s.backup_start_date,
        s.backup_finish_date,
        CAST(s.first_lsn AS VARCHAR(50)) AS first_lsn,
        CAST(s.last_lsn AS VARCHAR(50)) AS last_lsn,
        CASE s.[type]
        WHEN 'D' THEN 'Full'
        WHEN 'I' THEN 'Differential'
        WHEN 'L' THEN 'Transaction Log'
        END AS BackupType,
        s.server_name,
        s.recovery_model
    FROM msdb.dbo.backupset s (nolock)
        INNER JOIN msdb.dbo.backupmediafamily m (nolock) ON s.media_set_id = m.media_set_id
    where s.database_name = @DATABASENAME
    ORDER BY backup_start_date DESC, backup_finish_date
    Il suffit de renseigner le nom de la base dans la variable
    Blog Perso | Kankuru (logiciel gratuit pour SQL Server)

  13. #13
    Membre régulier
    Profil pro
    Inscrit en
    Avril 2009
    Messages
    217
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Avril 2009
    Messages : 217
    Points : 112
    Points
    112
    Par défaut
    Et voilà :
    BASE_PROD NUL 28 MB 0 Seconds 2013-05-23 21:27:57.000 2013-05-23 21:27:57.000 44966000000325900001 45007000000046900001 Transaction Log SERVER FULL
    BASE_PROD {E9236F41-E7F4-4F12-AF18-B403A3C37FD2}7 4924 MB 9 Seconds 2013-05-23 21:23:42.000 2013-05-23 21:23:51.000 45007000000044300037 45007000000045900001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4925 MB 78 Seconds 2013-05-23 21:00:08.000 2013-05-23 21:01:26.000 45007000000037600141 45007000000043400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4924 MB 79 Seconds 2013-05-22 21:00:08.000 2013-05-22 21:01:27.000 44978000000055700046 44978000000057700001 Full SERVER FULL
    BASE_PROD NUL 30 MB 0 Seconds 2013-05-21 21:24:54.000 2013-05-21 21:24:54.000 44951000000259200001 44966000000325900001 Transaction Log SERVER FULL
    BASE_PROD {3C95A4BD-A925-4466-866B-B2795E510171}7 4922 MB 9 Seconds 2013-05-21 21:19:32.000 2013-05-21 21:19:41.000 44966000000323300037 44966000000324900001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4923 MB 78 Seconds 2013-05-21 21:00:11.000 2013-05-21 21:01:29.000 44966000000321600017 44966000000322400001 Full SERVER FULL
    BASE_PROD NUL 1 MB 0 Seconds 2013-05-20 21:19:00.000 2013-05-20 21:19:00.000 44950000000264800001 44951000000259200001 Transaction Log SERVER FULL
    BASE_PROD {9590CA6B-DD0E-4035-B20C-8A9C7450EB3C}7 4917 MB 7 Seconds 2013-05-20 21:15:58.000 2013-05-20 21:16:05.000 44951000000256600036 44951000000258200001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4918 MB 78 Seconds 2013-05-20 21:00:07.000 2013-05-20 21:01:25.000 44951000000249500149 44951000000255700001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-19 21:18:10.000 2013-05-19 21:18:10.000 44950000000194000001 44950000000264800001 Transaction Log SERVER FULL
    BASE_PROD {1D9B6124-4850-44D8-98DB-EEBEBB3952B7}7 4917 MB 9 Seconds 2013-05-19 21:15:53.000 2013-05-19 21:16:02.000 44950000000260000098 44950000000263900001 Full SERVER FULL
    BASE_PROD NUL 1 MB 0 Seconds 2013-05-18 21:17:36.000 2013-05-18 21:17:36.000 44949000000282700001 44950000000194000001 Transaction Log SERVER FULL
    BASE_PROD {9E3A7315-67A0-485C-B38E-E3A5DF2A298D}7 4917 MB 9 Seconds 2013-05-18 21:15:12.000 2013-05-18 21:15:21.000 44950000000192300017 44950000000193100001 Full SERVER FULL
    BASE_PROD NUL 27 MB 0 Seconds 2013-05-17 21:25:49.000 2013-05-17 21:25:49.000 44917000000089700001 44949000000282700001 Transaction Log SERVER FULL
    BASE_PROD {71E62041-D284-45C8-BB2A-736F16A7906E}7 4917 MB 9 Seconds 2013-05-17 21:22:05.000 2013-05-17 21:22:14.000 44949000000280100037 44949000000281700001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4918 MB 79 Seconds 2013-05-17 21:00:08.000 2013-05-17 21:01:27.000 44949000000268400263 44949000000279200001 Full SERVER FULL
    BASE_PROD NUL 14 MB 0 Seconds 2013-05-16 21:22:12.000 2013-05-16 21:22:12.000 44887000000042600001 44917000000089700001 Transaction Log SERVER FULL
    BASE_PROD {B2E3F0B9-4F62-4DC6-8030-27DAD95544BF}7 4915 MB 9 Seconds 2013-05-16 21:17:37.000 2013-05-16 21:17:46.000 44917000000087100037 44917000000088700001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4915 MB 78 Seconds 2013-05-16 21:00:08.000 2013-05-16 21:01:26.000 44917000000079400164 44917000000086200001 Full SERVER FULL
    BASE_PROD NUL 12 MB 0 Seconds 2013-05-15 21:19:50.000 2013-05-15 21:19:50.000 44870000000074400001 44887000000042600001 Transaction Log SERVER FULL
    BASE_PROD {A3012173-A549-4F31-AB60-F8DC6BB4CE86}7 4913 MB 9 Seconds 2013-05-15 21:16:18.000 2013-05-15 21:16:27.000 44887000000040000037 44887000000041600001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4914 MB 78 Seconds 2013-05-15 21:00:08.000 2013-05-15 21:01:26.000 44887000000037600034 44887000000039100001 Full SERVER FULL
    BASE_PROD NUL 18 MB 0 Seconds 2013-05-14 21:22:14.000 2013-05-14 21:22:14.000 44835000000114600001 44870000000074400001 Transaction Log SERVER FULL
    BASE_PROD {EDAC4168-6126-42B0-8575-58617FEFB2A5}7 4912 MB 9 Seconds 2013-05-14 21:18:14.000 2013-05-14 21:18:23.000 44870000000071700037 44870000000073400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4913 MB 79 Seconds 2013-05-14 21:00:11.000 2013-05-14 21:01:30.000 44870000000060700246 44870000000070800001 Full SERVER FULL
    BASE_PROD NUL 18 MB 0 Seconds 2013-05-13 21:18:24.000 2013-05-13 21:18:24.000 44827000000319300001 44835000000114600001 Transaction Log SERVER FULL
    BASE_PROD {47F77128-4003-47CD-AAB0-6E26ECC407AE}7 4909 MB 8 Seconds 2013-05-13 21:14:53.000 2013-05-13 21:15:01.000 44835000000112000037 44835000000113600001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4910 MB 79 Seconds 2013-05-13 21:00:09.000 2013-05-13 21:01:28.000 44835000000107100096 44835000000111100001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-12 21:15:59.000 2013-05-12 21:15:59.000 44827000000249400001 44827000000319300001 Transaction Log SERVER FULL
    BASE_PROD {BB38D15F-1254-4B87-B6DC-C18246D8E979}7 4907 MB 7 Seconds 2013-05-12 21:13:52.000 2013-05-12 21:13:59.000 44827000000314500098 44827000000318400001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-11 21:16:10.000 2013-05-11 21:16:10.000 44827000000180000001 44827000000249400001 Transaction Log SERVER FULL
    BASE_PROD {ED10B745-06E3-49CE-801A-50839485D86F}7 4907 MB 11 Seconds 2013-05-11 21:13:57.000 2013-05-11 21:14:08.000 44827000000244600098 44827000000248500001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-10 21:21:24.000 2013-05-10 21:21:24.000 44827000000097900001 44827000000180000001 Transaction Log SERVER FULL
    BASE_PROD {1E9242F1-9ED2-4637-AFD4-E10A23503203}7 4907 MB 8 Seconds 2013-05-10 21:18:15.000 2013-05-10 21:18:23.000 44827000000177400036 44827000000179000001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4907 MB 78 Seconds 2013-05-10 21:00:07.000 2013-05-10 21:01:25.000 44827000000166300253 44827000000176500001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-09 21:17:18.000 2013-05-09 21:17:18.000 44827000000092500001 44827000000097900001 Transaction Log SERVER FULL
    BASE_PROD {3EFD592D-2B1D-423A-8F8C-E8E0E469A63C}7 4907 MB 8 Seconds 2013-05-09 21:14:35.000 2013-05-09 21:14:43.000 44827000000095300036 44827000000096900001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4907 MB 78 Seconds 2013-05-09 21:00:08.000 2013-05-09 21:01:26.000 44827000000092700036 44827000000094300001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-08 21:17:53.000 2013-05-08 21:17:53.000 44827000000049600001 44827000000092500001 Transaction Log SERVER FULL
    BASE_PROD {24460655-CF43-467D-B83D-033ADA7381AC}7 4907 MB 7 Seconds 2013-05-08 21:15:11.000 2013-05-08 21:15:18.000 44827000000089900037 44827000000091500001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4907 MB 78 Seconds 2013-05-08 21:00:07.000 2013-05-08 21:01:25.000 44827000000077800276 44827000000089000001 Full SERVER FULL
    BASE_PROD NUL 11 MB 0 Seconds 2013-05-07 21:20:10.000 2013-05-07 21:20:10.000 44821000000263400001 44827000000049600001 Transaction Log SERVER FULL
    BASE_PROD {FC57AE4F-1429-4CDD-95E9-4618E08F11D8}7 4907 MB 9 Seconds 2013-05-07 21:16:37.000 2013-05-07 21:16:46.000 44827000000047000036 44827000000048600001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4907 MB 78 Seconds 2013-05-07 21:00:10.000 2013-05-07 21:01:28.000 44827000000034100276 44827000000046000001 Full SERVER FULL
    BASE_PROD NUL 21 MB 0 Seconds 2013-05-06 21:19:38.000 2013-05-06 21:19:38.000 44808000000185100001 44821000000263400001 Transaction Log SERVER FULL
    BASE_PROD {89037729-E8B6-4297-AA8B-7B785B2C059E}7 4904 MB 8 Seconds 2013-05-06 21:16:20.000 2013-05-06 21:16:28.000 44821000000260800037 44821000000262400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4905 MB 80 Seconds 2013-05-06 21:00:08.000 2013-05-06 21:01:28.000 44821000000255600102 44821000000259900001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-05 21:17:43.000 2013-05-05 21:17:43.000 44808000000115500001 44808000000185100001 Transaction Log SERVER FULL
    BASE_PROD {A719FF63-C730-4E22-883F-E7F0ABAF3FF5}7 4903 MB 8 Seconds 2013-05-05 21:15:38.000 2013-05-05 21:15:46.000 44808000000180300098 44808000000184200001 Full SERVER FULL
    BASE_PROD NUL 4 MB 0 Seconds 2013-05-04 21:20:45.000 2013-05-04 21:20:45.000 44805000000006400001 44808000000115500001 Transaction Log SERVER FULL
    BASE_PROD {2D65EF0F-EB46-4998-9DF1-6FB61B6B2401}7 4903 MB 9 Seconds 2013-05-04 21:18:25.000 2013-05-04 21:18:34.000 44808000000108800141 44808000000114600001 Full SERVER FULL
    BASE_PROD NUL 12 MB 0 Seconds 2013-05-03 21:28:05.000 2013-05-03 21:28:05.000 44782000000183000001 44805000000006400001 Transaction Log SERVER FULL
    BASE_PROD {F365C47B-1A0E-4A3B-8602-2921EAE72251}7 4903 MB 8 Seconds 2013-05-03 21:24:30.000 2013-05-03 21:24:38.000 44805000000003800037 44805000000005400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4903 MB 78 Seconds 2013-05-03 21:00:08.000 2013-05-03 21:01:26.000 44805000000001600029 44805000000002900001 Full SERVER FULL
    BASE_PROD NUL 18 MB 0 Seconds 2013-05-02 21:21:58.000 2013-05-02 21:21:58.000 44748000000075800001 44782000000183000001 Transaction Log SERVER FULL
    BASE_PROD {242435DA-BCD1-4EFF-9212-8D439929324B}7 4902 MB 9 Seconds 2013-05-02 21:17:21.000 2013-05-02 21:17:30.000 44782000000180400037 44782000000182000001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4903 MB 79 Seconds 2013-05-02 21:00:08.000 2013-05-02 21:01:27.000 44782000000168100279 44782000000179500001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-05-01 21:20:09.000 2013-05-01 21:20:09.000 44748000000070400001 44748000000075800001 Transaction Log SERVER FULL
    BASE_PROD {71DE5041-3433-49E2-A7AE-3B98EBA10363}7 4900 MB 7 Seconds 2013-05-01 21:17:36.000 2013-05-01 21:17:43.000 44748000000073200036 44748000000074800001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4901 MB 77 Seconds 2013-05-01 21:00:08.000 2013-05-01 21:01:25.000 44748000000070600036 44748000000072200001 Full SERVER FULL
    BASE_PROD NUL 22 MB 1 Seconds 2013-04-30 21:23:00.000 2013-04-30 21:23:01.000 44705000000033100001 44748000000070400001 Transaction Log SERVER FULL
    BASE_PROD {99062645-57AD-467A-B9E6-CAA0214657BC}7 4900 MB 8 Seconds 2013-04-30 21:19:25.000 2013-04-30 21:19:33.000 44748000000067800036 44748000000069400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD_backup.bak 4901 MB 78 Seconds 2013-04-30 21:00:10.000 2013-04-30 21:01:28.000 44748000000066400008 44748000000066900001 Full SERVER FULL
    BASE_PROD NUL 20 MB 1 Seconds 2013-04-29 21:47:47.000 2013-04-29 21:47:48.000 44694000000154600001 44705000000033100001 Transaction Log SERVER FULL
    BASE_PROD {4D4F47D6-0AE7-405E-BEA4-6C7A07EE62A7}7 4896 MB 8 Seconds 2013-04-29 21:35:29.000 2013-04-29 21:35:37.000 44705000000030400037 44705000000032100001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4897 MB 79 Seconds 2013-04-29 21:00:11.000 2013-04-29 21:01:30.000 44705000000025600094 44705000000029500001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-04-27 21:19:44.000 2013-04-27 21:19:44.000 44694000000076800001 44694000000154600001 Transaction Log SERVER FULL
    BASE_PROD {09A94DDE-6DFD-4370-B7B8-092B2B17B20E}7 4892 MB 6 Seconds 2013-04-27 21:17:20.000 2013-04-27 21:17:26.000 44694000000149800098 44694000000153700001 Full SERVER FULL
    BASE_PROD NUL 16 MB 0 Seconds 2013-04-26 21:26:41.000 2013-04-26 21:26:41.000 44686000000195300001 44694000000076800001 Transaction Log SERVER FULL
    BASE_PROD {70063940-B45A-4C57-BF8F-3748B2A927B9}7 4892 MB 9 Seconds 2013-04-26 21:22:57.000 2013-04-26 21:23:06.000 44694000000074200037 44694000000075800001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4893 MB 79 Seconds 2013-04-26 21:00:08.000 2013-04-26 21:01:27.000 44694000000072800008 44694000000073300001 Full SERVER FULL
    BASE_PROD NUL 10 MB 0 Seconds 2013-04-25 21:21:40.000 2013-04-25 21:21:40.000 44680000000216800001 44686000000195300001 Transaction Log SERVER FULL
    BASE_PROD {CA693A95-B78C-4A23-85FD-485DA77FC004}7 4891 MB 9 Seconds 2013-04-25 21:17:59.000 2013-04-25 21:18:08.000 44686000000192600037 44686000000194300001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4891 MB 79 Seconds 2013-04-25 21:00:08.000 2013-04-25 21:01:27.000 44686000000191100012 44686000000191700001 Full SERVER FULL
    BASE_PROD NUL 23 MB 1 Seconds 2013-04-24 21:22:19.000 2013-04-24 21:22:20.000 44651000000197800001 44680000000216800001 Transaction Log SERVER FULL
    BASE_PROD {F6D4687D-FAEF-42DF-868B-82444B013838}7 4890 MB 7 Seconds 2013-04-24 21:18:15.000 2013-04-24 21:18:22.000 44680000000214200037 44680000000215800001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4891 MB 78 Seconds 2013-04-24 21:00:08.000 2013-04-24 21:01:26.000 44680000000207200148 44680000000213300001 Full SERVER FULL
    BASE_PROD NUL 14 MB 0 Seconds 2013-04-23 21:22:20.000 2013-04-23 21:22:20.000 44623000000045700001 44651000000197800001 Transaction Log SERVER FULL
    BASE_PROD {D41C98B8-6FA2-41DB-B6EB-CCEBA7199E85}7 4888 MB 7 Seconds 2013-04-23 21:18:10.000 2013-04-23 21:18:17.000 44651000000195200037 44651000000196800001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4888 MB 79 Seconds 2013-04-23 21:00:11.000 2013-04-23 21:01:30.000 44651000000186000202 44651000000194300001 Full SERVER FULL
    BASE_PROD NUL 6 MB 0 Seconds 2013-04-22 21:20:51.000 2013-04-22 21:20:51.000 44616000000091100001 44623000000045700001 Transaction Log SERVER FULL
    BASE_PROD {BD5724E7-4793-4CAC-AAF9-ADDB313237CB}7 4885 MB 9 Seconds 2013-04-22 21:17:13.000 2013-04-22 21:17:22.000 44623000000043000037 44623000000044700001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4886 MB 78 Seconds 2013-04-22 21:00:08.000 2013-04-22 21:01:26.000 44623000000037600107 44623000000042100001 Full SERVER FULL
    BASE_PROD NUL 0 MB 0 Seconds 2013-04-21 21:18:00.000 2013-04-21 21:18:00.000 44616000000005200001 44616000000091100001 Transaction Log SERVER FULL
    BASE_PROD {8B6F0981-A796-4C18-8EB1-EE12478F6CCF}7 4885 MB 9 Seconds 2013-04-21 21:15:31.000 2013-04-21 21:15:40.000 44616000000080000253 44616000000090200001 Full SERVER FULL
    BASE_PROD NUL 1 MB 0 Seconds 2013-04-20 21:18:33.000 2013-04-20 21:18:33.000 44615000000020200001 44616000000005200001 Transaction Log SERVER FULL
    BASE_PROD {3538BE7F-6CC4-45D8-9E99-D6982FEE8835}7 4885 MB 9 Seconds 2013-04-20 21:16:07.000 2013-04-20 21:16:16.000 44616000000001600063 44616000000004300001 Full SERVER FULL
    BASE_PROD NUL 14 MB 0 Seconds 2013-04-19 21:23:17.000 2013-04-19 21:23:17.000 44593000000066300001 44615000000020200001 Transaction Log SERVER FULL
    BASE_PROD {BC0EF00F-C026-47F8-8C23-0D2B6881B4B2}7 4885 MB 8 Seconds 2013-04-19 21:19:38.000 2013-04-19 21:19:46.000 44615000000017600037 44615000000019200001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4885 MB 78 Seconds 2013-04-19 21:00:09.000 2013-04-19 21:01:27.000 44615000000013600073 44615000000016700001 Full SERVER FULL
    BASE_PROD NUL 20 MB 0 Seconds 2013-04-18 21:22:26.000 2013-04-18 21:22:26.000 44563000000068400001 44593000000066300001 Transaction Log SERVER FULL
    BASE_PROD {741FA4F4-0DE5-4E3F-9B7C-9E6DCBD1D18F}7 4883 MB 8 Seconds 2013-04-18 21:18:44.000 2013-04-18 21:18:52.000 44593000000063700037 44593000000065300001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4884 MB 78 Seconds 2013-04-18 21:00:08.000 2013-04-18 21:01:26.000 44593000000061000042 44593000000062800001 Full SERVER FULL
    BASE_PROD NUL 105 MB 1 Seconds 2013-04-17 21:42:12.000 2013-04-17 21:42:13.000 44432000000042000001 44563000000068400001 Transaction Log SERVER FULL
    BASE_PROD {3C7175EB-75A8-4310-B388-CA566341439A}7 4882 MB 7 Seconds 2013-04-17 21:34:24.000 2013-04-17 21:34:31.000 44563000000065800037 44563000000067400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4883 MB 78 Seconds 2013-04-17 21:00:09.000 2013-04-17 21:01:27.000 44563000000063800024 44563000000064900001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4881 MB 79 Seconds 2013-04-16 21:00:11.000 2013-04-16 21:01:30.000 44554000000080100264 44554000000091000001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4876 MB 79 Seconds 2013-04-15 21:00:08.000 2013-04-15 21:01:27.000 44536000000135700002 44536000000136100001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4875 MB 77 Seconds 2013-04-12 21:00:11.000 2013-04-12 21:01:28.000 44492000000014600216 44492000000023400001 Full SERVER FULL
    BASE_PROD NUL 17 MB 1 Seconds 2013-04-11 21:21:16.000 2013-04-11 21:21:17.000 44398000000050800001 44432000000042000001 Transaction Log SERVER FULL
    BASE_PROD {AF45927A-FC47-4321-A71B-3901CB534532}7 4871 MB 8 Seconds 2013-04-11 21:17:40.000 2013-04-11 21:17:48.000 44432000000039400037 44432000000041000001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4871 MB 79 Seconds 2013-04-11 21:00:08.000 2013-04-11 21:01:27.000 44432000000037600020 44432000000038500001 Full SERVER FULL
    BASE_PROD NUL 31 MB 0 Seconds 2013-04-10 21:21:21.000 2013-04-10 21:21:21.000 44346000000051100001 44398000000050800001 Transaction Log SERVER FULL
    BASE_PROD {227B4E33-04BB-4B82-A7C1-936E5628873B}7 4869 MB 7 Seconds 2013-04-10 21:17:59.000 2013-04-10 21:18:06.000 44398000000048100037 44398000000049800001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4870 MB 78 Seconds 2013-04-10 21:00:09.000 2013-04-10 21:01:27.000 44398000000037600232 44398000000047200001 Full SERVER FULL
    BASE_PROD NUL 47 MB 0 Seconds 2013-04-09 21:23:53.000 2013-04-09 21:23:53.000 44258000000008900001 44346000000051100001 Transaction Log SERVER FULL
    BASE_PROD {A5F548E3-168C-4B91-8339-3742680CB1D5}7 4867 MB 7 Seconds 2013-04-09 21:19:03.000 2013-04-09 21:19:10.000 44346000000048500037 44346000000050100001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4867 MB 78 Seconds 2013-04-09 21:00:11.000 2013-04-09 21:01:29.000 44346000000044900063 44346000000047600001 Full SERVER FULL
    BASE_PROD NUL 29 MB 1 Seconds 2013-04-08 21:23:47.000 2013-04-08 21:23:48.000 44196000000075700001 44258000000008900001 Transaction Log SERVER FULL
    BASE_PROD {53AC7AE1-60B9-4004-AFF8-8CE315FBC4B8}7 4860 MB 8 Seconds 2013-04-08 21:20:14.000 2013-04-08 21:20:22.000 44258000000006300037 44258000000007900001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4861 MB 78 Seconds 2013-04-08 21:00:08.000 2013-04-08 21:01:26.000 44258000000001600090 44258000000005400001 Full SERVER FULL
    BASE_PROD NUL 2 MB 0 Seconds 2013-04-07 21:21:40.000 2013-04-07 21:21:40.000 44189000000009700001 44196000000075700001 Transaction Log SERVER FULL
    BASE_PROD {A6619C9A-A95E-4D64-BC39-EC43BA3E221E}7 4857 MB 8 Seconds 2013-04-07 21:19:27.000 2013-04-07 21:19:35.000 44196000000064100263 44196000000074800001 Full SERVER FULL
    BASE_PROD NUL 1 MB 0 Seconds 2013-04-06 21:18:57.000 2013-04-06 21:18:57.000 44185000000028400001 44189000000009700001 Transaction Log SERVER FULL
    BASE_PROD {59DA9D87-5476-42B1-B5DC-F9F8843CB15A}7 4857 MB 9 Seconds 2013-04-06 21:16:46.000 2013-04-06 21:16:55.000 44189000000001600175 44189000000008800001 Full SERVER FULL
    BASE_PROD NUL 30 MB 1 Seconds 2013-04-05 21:40:48.000 2013-04-05 21:40:49.000 44137000000022800001 44185000000028400001 Transaction Log SERVER FULL
    BASE_PROD {86FAEC09-B021-4536-A067-CF0281526C53}7 4857 MB 7 Seconds 2013-04-05 21:37:16.000 2013-04-05 21:37:23.000 44185000000025800037 44185000000027400001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4858 MB 78 Seconds 2013-04-05 21:00:08.000 2013-04-05 21:01:26.000 44185000000013600274 44185000000024900001 Full SERVER FULL
    BASE_PROD NUL 51 MB 1 Seconds 2013-04-04 21:43:26.000 2013-04-04 21:43:27.000 44042000000032200001 44137000000022800001 Transaction Log SERVER FULL
    BASE_PROD {A03817B7-184A-4CCB-8113-0BF768903668}7 4854 MB 9 Seconds 2013-04-04 21:36:56.000 2013-04-04 21:37:05.000 44137000000020200037 44137000000021800001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4855 MB 77 Seconds 2013-04-04 21:00:08.000 2013-04-04 21:01:25.000 44137000000013600137 44137000000019300001 Full SERVER FULL
    BASE_PROD NUL 23 MB 0 Seconds 2013-04-03 21:32:21.000 2013-04-03 21:32:21.000 43992000000005700001 44042000000032200001 Transaction Log SERVER FULL
    BASE_PROD {0CF32B00-B46A-4CAF-B214-D964D65FB1D6}7 4850 MB 8 Seconds 2013-04-03 21:27:23.000 2013-04-03 21:27:31.000 44042000000029600037 44042000000031200001 Full SERVER FULL
    BASE_PROD D:\Backup_SQL\BASE_PROD\BASE_PROD.bak 4851 MB 77 Seconds 2013-04-03 21:00:08.000 2013-04-03 21:01:25.000 44042000000025600072 44042000000028700001 Full SERVER FULL
    BASE_PROD NUL 15 MB 0 Seconds 2013-04-02 21:33:01.000 2013-04-02 21:33:01.000 43963000000036800001 43992000000005700001 Transaction Log SERVER FULL
    Frédéric

Discussions similaires

  1. Récupérer des informations sur les connexions réseau
    Par Leobaillard dans le forum Delphi
    Réponses: 8
    Dernier message: 31/08/2006, 01h20
  2. des exos sur les boocles
    Par zeyd dans le forum Algorithmes et structures de données
    Réponses: 8
    Dernier message: 27/11/2005, 18h03
  3. [VB6][impression]Comment faire des effets sur les polices ?
    Par le.dod dans le forum VB 6 et antérieur
    Réponses: 11
    Dernier message: 08/11/2002, 10h31
  4. recherches des cours ou des explications sur les algorithmes
    Par Marcus2211 dans le forum Algorithmes et structures de données
    Réponses: 6
    Dernier message: 19/05/2002, 22h18

Partager

Partager
  • Envoyer la discussion sur Viadeo
  • Envoyer la discussion sur Twitter
  • Envoyer la discussion sur Google
  • Envoyer la discussion sur Facebook
  • Envoyer la discussion sur Digg
  • Envoyer la discussion sur Delicious
  • Envoyer la discussion sur MySpace
  • Envoyer la discussion sur Yahoo