ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Tracking the origination of a shadow copy

    IT Discussion
    volume shadow copy vssadmin windows server
    2
    4
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • art_of_shredA
      art_of_shred Banned
      last edited by scottalanmiller

      I have a client who is trying to pin the creation of a shadow copy on a particular bit of software that we're using, that I am quite sure is not the culprit. Using the "vssadmin list shadows" command, I can see the shadow copy, but I can't discern if any of the resulting information is telling me what requested said shadow copy. Can anyone offer advice as to what I am not doing that I should be, or if something like the "originating machine" is the originator of the request? Thanks!

      1 Reply Last reply Reply Quote 2
      • DashrenderD
        Dashrender
        last edited by

        You can request a shadow copy to happen on another machine other than local one? Didn't know that.

        1 Reply Last reply Reply Quote 1
        • DashrenderD
          Dashrender
          last edited by

          I suppose you could easy enough with an agent, thinking backups here.

          art_of_shredA 1 Reply Last reply Reply Quote 1
          • art_of_shredA
            art_of_shred Banned @Dashrender
            last edited by

            @Dashrender said in Tracking the origination of a shadow copy:

            I suppose you could easy enough with an agent, thinking backups here.

            Precisely. As the origination is the same machine and not the backup device, I guess that answers that.

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post