SANHQ creation of snapshots?

Similar Questions

• Creation of snapshot on ESXi 5.1 fails

  Hello

  Im having a problem creating a snapshot on a certain virtual machine on ESXi 5.1. It fails with the error "file is larger than the maximum file size supported". Now, I've read a few KB articles including "1012384"... but I can't yet absolutely determine the cause of the error.

  VM is a file server with several hard drives.

  Disk1 Disk2 of 40 GB, 1, 9 to, Disk3 1, 5 TB, 2 TB Disk4

  Machine including all disks files are on a single data store.

  Data store: VMFS 5,58, Blocksize 1 MB, 7, 81TB, used capacity 5, 45 to, free 2, 36 to

  I read an article that the 2 TB - 512 b is correct for a file in ESXi 5.1 but that a certain amount of space is required for the load of the snapshot. ~ 16 GB for a 2 TB drive. The 4th disc with a 2 TB size would be the problem?

  I've added a screenshot. Sorry, its in German... but basically, he says that a file (filename not specified) is larger than the size max data store (database not specified).

  Thank you

  David

  ... a certain amount of space is required for the load of the snapshot. ~ 16 GB for a 2 TB drive. The 4th disc with a 2 TB size would be the problem?

  It is probably the case. The maximum file size for a hard of snapshot is size provisioned to the virtual disk, more overhead (metadata), which must not exceed 2 048 GB less 512octets with ESXi versions previous ESXi 5.5 (or VMFS3 data warehouses). To create a new snapshot, actually no matter how much you have on the datatore of free space on the disk (this is to you to monitor the free space to avoid the problems of out-of-space disk), ESXi only checks if the maximum possible size is supported on the data store, to allow the snapshot to grow as required.

  André

• (Redirect) - error msg 'restore instant snapshot creation has failed.

  in my activity log, I notice one note an error msg that continues to repeat "restore instant creation of snapshot has failed.  Any suggestions as to what could be the problem? Thnx in advance...

  Padraigmaca thanks for the reply. Please repost this in the laptop computer forum for assistance.

  http://en.community.Dell.com/support-forums/laptop/

• New capture instant creation of the snapshot with the State of the computer when back

  Hello

  I am trying to create a script to remove the previous snapshot and re - create later after that I changed the virtual computer for some reason any. Have all the machines themselves up so after applying the snapshot, I can run test on them without delay.

  
  

  This is the script:

  SE connect-VIServer $server - user $username - password $password

  for ($c = 1; $c - 7; $c ++)

  {

  for ($t = 1; $t - 2; $t ++)

  {

  $VM = get-VM-name "${hostmask} c$ {c} t$ {t}.

  write-host "${hostmask} c$ {c} t$ {t}.

  $Snapshot = get-Snapshot - VM $VM - name $snapshotName

  If ($Snapshot - not $null) {}

  Remove-snapshot - cliché $Snapshot - confirm: $false

  }

  Try {new-Snapshot - VM $VM - name $snapshotName |} Out-Null}

  Catch {$_.exception | select *;} Write-Host "Unable to create the snapshot for $i" ;}

  }

  }

  If the script works fine, the only problem is that snapshots are created as if the machines have been turned off, which is not. In addition, the creation of snapshots take only a second, which is not normal.

  No idea why this might happen?

  Kind regards

  Ruben

  The default value for the switch memory on the cmdlet New-Snapshot is $false.

  So if you want to include the memory in the snapshot, you must do

  Try {new-Snapshot - VM $VM - name $snapshotName - memory |} Out-Null}

• Question about Equallogic snapshots.

  Hello forum

  I could not confirm this, but instant never need to commit anything to the basic volume?

  Lets say I have 10 snapshots and delete the oldest? There will be a load of e/s to validate these instant changes?

  Also, if someone could point me to any type of indepth explanation of this technique of snapshot, I would be interested to read all that.

  Thank you!

  N ° current data are already on the base volume.  There is nothing to commit.   Only if you are completely restoring a volume from a snapshot will be there in writing for the base volume.

  On the site of Equallogic Support KB:

  Solution title TABLE: how the snapshot reserve space is allocated and used

  Solution details Snapshot Reserve Allocation and use

  -------------------------------------

  In a series group PS, snapshots can protect against errors, of a volume

  virus or the database. A cliché represents the content of a volume

  at the time you created the snapshot. Creating a snapshot does not disturb

  access to the volume, and the snapshot is instantly available allowed

  iSCSI initiators.

  Before you can create snapshots for a volume, you must allocate space (called

  snapshot pool) for snapshots. You set the value of the snapshot reserve

  When you create or modify a volume. Snapshot reserve benefits from the same

  as the volume of the pool data.

  When snapshot data consume entire supply snapshot, the Group remove is

  the oldest snapshots to free up space for new images or sets the volume and

  snapshots offline, according to the policy you selected for instant recovery

  space.

  The functionality for creating snapshots is called hybrid allocate when writing.

  Operation of sharing and snapshot of the page

  -----------------------------------

  A PS Series Group organizes the physical storage into logical segments called pages.

  Each page is composed of several logical blocks. This is similar to the way file

  systems combine areas of physical disk in 'clusters' or 'chunks '. Each page has

  a reference count which records the number of volumes and snapshots that share

  the page.

  When you create a volume, the group creates an internal table, called the volume

  table, which contains pointers to pages that use the volume. When you create

  a snapshot of a volume, the group creates a snapshot table by making a copy of

  the volume table, which is usually an operation in memory that the Group

  run in a transactional manner. For each page of volume in use, the support group increases the

  reference count to indicate that the volume and the snapshot share page.

  Because the group does not move or copy the data or allocates a new pages, photos

  are fast and efficient.

  Reserve of the snapshot stores the differences between the data on the volume and snapshot data

  (in addition to differences between the data of multiple snapshots). When you

  first create a snapshot, the page for the volume and the snapshot tables are

  In brief identical copies and the snapshot consumes no snapshot

  reserve. A reading of the same logical block of the volume application or the

  snapshot returns the same data because the application is reading from the same page.

  However, if you write a page that has a volume and a snapshot of share, snapshot

  reserve is consumed.

  Here's a simplified example of a snapshot operation. In general, no.

  additional I/o operations are needed to manage the data volume or snapshot.

  However, other internal operations can occur due to virtualization and

  data balancing on berries of the PS Series.

  If an application performs a write to 8 KB for a volume containing a snapshot, the

  Group:

  1. determine what page is modified by the write operation.

  2 - If the page is not shared, writes the data to the page.

  3. If the page is shared:

  . (a) allocates a new page of disk space and reduces the instant to reserve

  . the volume of a single page.

  . (b) update the page of volume table to point to the newly allocated page.

  . (c) mark the newly allocated page as having new data on the volume and the references of the

  . original page for unchanged data.

  . (d) writes the data to the new page.

  When writing is complete, if you read the data on the volume, you have access to the

  new page and new data. However, if you read the same logical block of the

  Instant, you get the original data, because the snapshot will always point towards the

  original page. Similarly, if you set a snapshot online, write to the snapshot.

  feature hybrid write protects the original data volume by allocating

  a new page for the new snapshot data.

  Only the first page of writing to a volume shared (or snapshot) consumes additional

  snapshot reserve. Each subsequent entry is considered identical to a writing on a

  non-shared the page because the original data are already protected.

  Functionality similar to hybrid allocate when writing is used in cloning operations.

  However, unlike when you create a snapshot, cloning a volume immediately

  consumes space additional group. If a clone is moved to another pool, data

  is copied during the operation of moving pool.

  Restoring a Volume from a snapshot

  ----------------------------------

  Because of the layout table, restore a volume from a snapshot is very

  quick. First of all, the group automatically creates a snapshot of the volume by copying

  the volume table to a new table of snapshot. Then the Group transposes the page tables

  the volume and the snapshot you selected for the restore operation. NO.

  additional space is required, and no data is moved.

  Deletion of Volumes and Snapshots

  ------------------------------

  Because volumes and snapshots to share pages, if you delete a volume, you

  automatically remove all the clichés associated with the volume.

  You can manually delete snapshots (for example, if you need more of)

  snapshot data). In addition, the group can delete snapshots automatically in the

  following situations:

  1 - failure instant free reserve. If the snapshot data consume the snapshot

  . reserve, the group either deletes the oldest snapshots to free up space for new

  . snapshots or sets the volume and snapshots in offline mode, according to the policy

  . you have chosen for the snapshot space recovery.

  2 - maximum number of snapshots, created from an agreed timetable. If you set up a

  . timetable for the creation of snapshots, you can specify the maximum number of

  . photos you want to keep. Once the program creates the maximum number

  . clichés, the group will delete the oldest snapshot for planning

  . to create a new snapshot.

  Snapshot are deleted in the background queue. The group travels

  the snapshot page table and decremented the reference count on every shared page.

  Any page that has a zero reference count is released into free space. Pages

  with a zero reference count are not released because they are shared with

  the volume or other snapshots.

  Because stereotypes can be automatically deleted, if you want to keep the

  given to a snapshot, you can clone the snapshot.

  Reserve snapshots use agreement

  ------------------------------------

  The snapshot reserve is consumed only if you write a shared volume or snapshot

  page. However, it is difficult to establish a correlation between the amount of data written in one

  volume (or snapshot) with the amount of instant reserve consumed as a result.

  especially if you have multiple snapshots.

  Because the pages consist of several logical blocks, size e/s and distribution

  volume merge affect overall performance of e/s in addition to the snapshot

  reserve its use.

  For example, do much written about a narrow range of logical blocks in a volume

  consumes a relatively low amount of reserve of the snapshot. This is because as Scripture

  the same logic block more than once, does not require not additional snapshot

  reserve.

  However, doing random number wrote a range of logical blocks in a

  volume can consume a large amount of reserve of the snapshot, because many other

  pages are affected.

  In general, use instant reserve depends on the following:

  1. number of entries that occur in the volume (or snapshot) and at least one

  . snapshot exists. In general, more Scriptures tend to use more snapshot reserve.

  . Although multiple writes to the same logical block do not require additional

  . space.

  2 - the range of logical blocks, on which occur the Scriptures. Written in a wide range of

  . logical blocks tend to use more instant reserve written in a narrow

  . rank, because more of the written word are to different pages.

  3. number of snapshots of the volume and timing of the write operations. Most

  . snapshots that you create more snapshot reserve is necessary, unless there is

  . few entries on the volume or snapshots.

  4 - age of snapshot. Snapshots older tend to consume more snapshot reserve only

  . the clichés of recent because the group must retain the original data for a

  . longer time.

  Design Snapshot reserve

  -----------------------

  You cannot create snapshots until you book instant space. Snapshot reserve

  is set as a percentage of the reserve volume (space) for the

  volume.

  When you create a volume, by default, the volume uses instant group-wide

  reserve adjustment. (The reserve in the scale default setting is 100%. You

  can change this default value.) You can change the reserve snapshot setting when you

  create a volume or later, even if the volume is in use.

  Although the snapshot reserve is not used until the volume or writing snapshot occur, it

  is consumed immediately free pool space. For example, if you create a

  fully allocated (not thin provisioned) 200 GB volume and specify a snapshot of 50%

  pool of reserve, free space is immediately reduced to 300 GB (200 GB for the volume

  reserve and 100 GB for Snap reserve), even if there are no pages in use.

  Therefore, before you create a volume, you should consider how many snapshot

  reserves, if any, to assign to the volume. The reserve of the snapshot set to zero (0)

  If you do not want to create snapshots.

  The optimal size of the snapshot reserve depends on the amount and type of

  changes in the volume and the number of shots you want to keep.

  By example, if you set the snapshot reserve 100%, and then create a snapshot.

  You can write to each byte of the volume without missing snapshot

  reserve. However, if you create another snapshot and then write in each byte of

  the volume, the first snapshot is deleted in disk space available for the new snapshot. If

  you set the instant reserve at 200%, there would be a sufficient reserve of snapshot

  for the two snapshots.

  A very conservative strategy in terms of instant reserve sizing is to put the snapshot

  book value at 100 times the number of shots you want to keep. This

  guarantees that keep you at least the number of snapshots, regardless of the

  the number of entries on the volume. However, this strategy is generally allocates

  book an excessive amount of snapshot, because that rarely crush you all the

  the data in a volume during the lifetime of a snapshot.

  The best way to instant size reserves is to assign an initial value to the reserve

  and watch how instant you can keep over a period of time specified under a

  normal workload. If you use tables to create snapshots, allow the

  calendar of work for several days.

  To get an initial value for a snapshot reserve volume, you must estimate

  the quantity and the type of entries in volume and the number of snapshots, you want

  keep. For example:

  -If you wait a few Scriptures or writings which are concentrated in a narrow range

  . logical blocks and you want to keep only a few shots, start with a value

  . 30%.

  -If you wait several entries or entries that are random in a wide range of

  . logical blocks and you want to keep more than a few shots, start with a value

  . 100%.

  If the snapshots are deleted until you reach the desired number of snapshots,

  increase the percentage of snapshot reserve. If you reach the desired number

  shots without consuming much of the instant free reserve, decrease the

  percentage of reserve snapshot. Continue to follow instant reserve and

  adjustments as needed.

  How Thin Provisioning button Snapshot Reserve

  ----------------------------------------------

  The snapshot reserve is based on a percentage of volume reserve (allocated space

  a volume). For a volume fully provisioned, the reserve volume is equal to the

  stated volume size. However, a thin volume put into service, the volume of reserve

  is initially very inferior to the reported size (default is subject to minimum volume

  10% of the reported size) and increases as the written volume occur.

  If you change a thin volume supplied in a volume fully provisioned, the

  amount of reserved snapshot increases automatically, because the volume of reserve

  increase in the size of the stated volume.

  If you change a volume of fully provisioned to thin-provisioned, the amount of

  snapshot of reserve decreases automatically, because the volume of reserve declines.

  However, if the snapshot resulting reserves will be too small to store all the

  existing snapshots, the group will automatically increase the instant reserve

  percentage of value that preserves all existing snapshots.

  Reducing the use of instant reserve

  -------------------------------

  Over time, you can reduce the use of instant reserve by periodically (for example,

  Once a month) defragmentation of databases and file systems. Defrag operations

  try to consolidate segments of files in a volume and, consequently, to reduce the scope

  logical blocks addresses used in the pages of the volume.

  Defragment the data read operations from one place and then write data to a new

  location. So increased use of instant reserve during and immediately

  after defragmentation, because existing snapshots will use more of the usual

  amount of the snapshot reserve. However, snapshots created after defragmentation

  operation must use less instant reserve, because the data on the volume are more contiguous.

  When a volume is highly fragmented, potential reduction of the snapshot reserve

  use can be dramatic, especially after removing the large before you defragment

  snapshots. Defrag operations can also reduce the I/O load on the group,

  because the contiguous data makes more efficient i/o operations, in order to improve the

  e/s overall performance.

  Latest defragmenters are good to reduce the fragmentation that is not seeking to be

  too thorough. Some defragmenters also try to combine the inactive data

  further restricting the likelihood of changes to shared pages. However, are not

  Defragment too frequently.

  Sector alignment may also affect the use of snapshot of the space, especially in

  larger volumes. File systems must be correctly aligned with the sector. It comes

  described in technical reports for VMware and Windows environments.

• The list of all snapshots wth Orchestrator with

  Hello

  I'm doing a script to list all snapshots of a vcenter Orchestrator with javascript. It's easy with powershell, but we changed our vcenter for vcsa 5.5 windows so I can't use it.

  I would like to have the date of creation of snapshots, snapshot size and vm. I would like to have the output to a file to send it, or in html format.

  I have to say that I'm not good with orchestrator, this is a new product for me, and I know not how to send an e-mail and how to make a script of ' hello world! '

  Someone at - it a script like this?

  Thank you to

  Try this workflow attached... Recently, I helped someone with a similar request.

• ERROR: New-Snapshot (the operation is not valid due to the current state of the object)

  Hello guys!

  I've been googlin everywhere, but impossible to find a solution to my problem. I hope that one of you, qualified people can point me in the right direction :)

  I created a powerCLI script to take a snapshot of our most important servers before we do our weekly maintenance. The idea to run the script as regular powershell script and then have

  1. Add snap-ins powercli and connect to virtualcenter servers
  2. ask the VC servers to virtual machines in a perticular folder
  3. Loop foreach on these servers to create a snapshot with the name $snapshotname

  Currently, I just do it turn on a test folder that I created in vSphere that contains 3 test VMs:

  • Testmagne1 - normal operation
  • Testmagne2 - I renamed the folder for this virtual machine in the data store to generate an error.
  • testmagne3 - normal operation

  Since the servers (not the test servers, but good ones) is the most important servers in our environment, I want to be able to catch exceptions and errors when I run this script. I do this with the Try - Catch - Finally works.

  The strange thing is:

  The release of Powershell/PowerCLI is different from the output in VirtualCenter (!)

  In virtualcenter, the output is as follows

  • Testmagne1 - snapshot is created successfully - as expected
  • Testmagne2 - the snapshot creation fails because it cannot find the files .vmx - as expected
  • Testmagne3 - snapshot is created successfully - as expected

  However, the exit in powercli is slightly different:

  • Testmagne1 - snapshot is created successfully - as expected
  • Testmagne2 - creation of the snapshot fails because it cannot find the files .vmx - as expected
  • Testmagne3 - snapshot fails with the error message: operation is not valid due to the current state of the object - huh?

  
  

  Apparently once the first error is generated all succeeding VMs get error "the operation is not valid due to the current state of the object"

  
  

  I've been pulling trying to figure this problem on my hair, but I'm not getting anywhere

  
  

  Here is some additional information:

  1. the Script (abridged version of it. It generates the same error):

  -STARTUP SCRIPT-

  $ErrorActionPreference = "stop".

  Add-PSSnapin VMware.VimAutomation.Vds, VMware.VimAutomation.Core | Out-Null

  SE connect-VIServer VIRTUALCENTER1, VIRTUALCENTER2 | Out-Null # Sensored VirtualCenter names

  $servers = get-VM-location 'testfolder '.

  $snapshotname = 'Testsnapshot '.

  $verifycreatesnapshot = Read-Host "you are about to create snapshots for $servers. Do you want to continue? o/n.

  If ($verifycreatesnapshot - eq 'y') {}

  Write-Host "snapshots of creation...". »

  {ForEach ($i in $servers)

  Write-Host "instant Creation for $i."

  Try {new-Snapshot - VM $i - name $snapshotname |} Out-Null}

  Catch {$_.exception | select *;} Write-Host "Unable to create the snapshot for $i" ;}

  }

  Write-Host "command finished.

  }

  else {Write-Host "Operation canceled by user"}

  Read-Host "end of the script. Press ENTER to close. "

  ------------------ END SCRIPT -------------------

  2. the PowerCli error messages:

  Error for Testmagne 2 (as expected):

  File: [DATASTORE114] testmagne2/testmagne2.vmx

  DynamicType:

  DynamicPropertyInternal:

  FaultCause:

  FaultMessage:

  ErrorId: Client20_TaskServiceImpl_CheckServerSideTaskUpdates_O

  perationFailed

  ErrorCategory: NotSpecified

  TargetObject:

  RecommendedAction:

  SessionId:

  ConnectionId: /VIServer = SENSORED: 443 /

  Severity: error

  Message: 31/10/2013-10:52:16 New-Snapshot the operat

  ion for the entity 'testmagne2' failed with the follo

  the wing's message: "file [DATASTORE114] testmagne2/testmagn".

  E2.vmx was not found.

  Data: {ParameterValues}

  InnerException: VMware.Vim.VimException: exploitation of the entity

  'testmagne2' failed with the following message: 'thread '.

  testmagne2/testmagne2.vmx e [DATASTORE114] was not crazy

  ND ".

  TargetSite:

  StackTrace:

  HelpLink:

  Source:

  Failed to create the snapshot for testmagne2

  Error for testmagne3:

  Creation of snapshot for testmagne3

  ErrorId: Core_BaseCmdlet_UnknownError

  ErrorCategory: NotSpecified

  TargetObject:

  RecommendedAction: An error occurred when executing command: new-Snapshot. I have check

  f exception for more details.

  SessionId:

  Login ID:

  Severity: error

  Message: 31/10/2013-10:52:17 instant New-capture operation is not

  valid due to the current state of the object.

  Data: {ParameterValues}

  InnerException : System.InvalidOperationException: operation is not valid from

  e to the current state of the object.

  at VMware.VimAutomation.ViCore.Impl.V1.Task.ViCoreTaskCo

  reServiceProviderImpl.BeginTaskCompletionPoll (list 1 taskLi

  St)

  at VMware.VimAutomation.Sdk.Impl.V1.Task.CoreTaskService

  Impl.WaitForTask (IEnumerable 1 taskList, ProgressCallback p

  rogressCallback)

  at VMware.VimAutomation.Sdk.Util10Ps.BaseCmdlet.BaseCmdl

  and. EndProcessingErrorHandled()

  at VMware.VimAutomation.ViCore.Util10Ps.BaseCmdlet.BaseC

  mdlet. EndProcessingErrorHandled()

  TargetSite: Sub ThrowTerminatingError (System.Management.Automation.Err

  orRecord)

  StackTrace: At System.Management.Automation.MshCommandRuntime.ThrowT

  erminatingError (ErrorRecord errorRecord)

  HelpLink:

  Source: System.Management.Automation

  Failed to create the snapshot for testmagne3

  3 PowerCLI version

  PowerCLI Version

  ----------------

  VMware vSphere PowerCLI 5.5 Release 1 build 1295336

  ---------------

  Versions of the snap

  ---------------

  VMWare AutoDeploy PowerCLI component 5.5 build 1262826

  VMWare ImageBuilder PowerCLI component 5.5 build 1262826

  License of VMware PowerCLI component 5.5 build 1265954

  VDS's VMware PowerCLI component 5.5 build 1295334

  VMware vSphere PowerCLI component 5.5 build 1295334

  
  

  4 VirtualCenter version

  VMware vCenter Server Version 5.0.0 Build 913577

  vSphere Client Version 5.0.0 Build 913577

  Hosts: VMware ESXi 5.0.0 Build 914586

  If you need additional information, let me know

  Any help is greatly appreciated

  Thank you!

  -Loincloth

  
  

  
  

  Definition - ErrorAction Stop locally on the cmdlet will not solve the problem. We have found and solved the problem and the fix will be available in the next version. Until then, you can use the $error variable to detect whether the cmdlet was successful or not. You can clear the $error variable before calling the cmdlet and check if it's still empty after the call.

• Deletion of snapshots automatically using the Snapshot Manager

  Hello

  I am very new and VMware Vsphere. I use vSphere 4.0 with ESXi 4 (I think). I managed to create a snapshot via the scheduled task in vSphere and I get a new every day; However, I would like to keep only one or two days worth of snapshots. The scheduled task is adjustable to delete snapshots after that whether a day or two old. Again, I am super new VMware vSphere and would appreciate any help that can be provided for the simplest solution. (Hoping that this can be done from the GUI somewhere)

  Thanks in advance

  Although it is possible to predict the creation of snapshots, I'm afraid there is no possibility to plan their removal.

  André

• Automate the VMware Snapshots

  I'm looking to automate a task with regard to snapshots in 5.0. Before launch us updates Windows take us a snapshot of each system manually. I would like to have a script that can automate the creation of snapshots and then run another to remove the next day. I found a script that will take a glance of all my servers, but I was looking for a way to do it by a list. Does anyone have any suggestions? I am new to scripting.

  you could do something like this in excel, csv

  Column1 Column2 Column3

  New-Snapshot -VM    VM        -Name BeforePatch
  

  then the export in Notepad, remove the comma and then save it as ps1.

  do something similar with the removal of the snap

• FrontView reboot from OS 6.6

  Hello!

  Since 6.6 I often see the message in the newspapers:

  > System: ReadyNASOS (readynasd) process or service has been restarted.

  The admin page is suspended and content under actions, backup and so on is empty...

  After a short time, the message is in the newspaper and the admin page works again...

  For the most part, which occurs after the creation of snapshots

  Kai

  the problem is solved by Skywalker, thx.

• Server 2003 R2 ntbackup operation failed

  Hi support them.

  I keep getting this error everytime I backup (ntbackup) for my windows server 2003 R2. tried applying the fix still "(windows serverr2003-kb940349-v3-x86-enu.exe) after reboot." Here's the code errors, need your urgent help.

  The backup status

  Operation: backup

  Active backup destination: file

  Media name: "GDF-svr01 - 5.bkf created on 29/09/2014 at 09:44"

  Creation of snapshots snapshots volume: 1 attempt.

  Error returned while creating the volume shadow copy: 0x8004230f.

  Error returned while creating the volume shadow copy: 8004230f

  Aborting backup.

  ----------------------

  The operation has successfully completed.

  ----------------------

  Try to post your problem on the Forum Pro of COMPUTING, you will have a better change to get the problem solved: http://social.technet.microsoft.com/Forums/windows/en-US/home?forum=w7itproinstall

  J W Stuart: http://www.pagestart.com

• NTBackup access denied errors using VSS

  I have a reception "access denied" errors using ntbackup on Windows Server 2003. This server is part of a domain, but not a controller domain.  All patches and updates are applied. The backup log is as follows:

  The backup status
  Operation: backup
  Active backup destination: file
  Media name: "Test Sybil Backup.bkf created 20/05/2011 at 10:43"

  Creation of snapshots snapshots volume: 1 attempt.
  Backup (via shadow) "C:".
  Backup set #1 on support #1
  Backup description: "Set created on 2011-05-20 at 10:43"
  Media name: "Test Sybil Backup.bkf created 20/05/2011 at 10:43"

  Backup type: Normal

  Backup started on 20/05/2011 at 10:44.
  WARNING: Could not open "C:\WINDOWS\system32\config\systemprofile\Local Settings\Temporary Internet Files\Content.IE5\desktop.ini" - skipped.
  Reason: Access is denied.

  WARNING: Could not open "C:\WINDOWS\system32\config\systemprofile\Local Settings\Temporary Internet Files\Content.IE5\index.dat" - skipped.
  Reason: Access is denied.

  WARNING: Could not open "C:\WINDOWS\system32\config\systemprofile\Local Settings\Temporary Internet Files\Content.IE5\CLMBKHQZ\desktop.ini" - skipped.
  Reason: Access is denied.

  WARNING: Could not open "C:\WINDOWS\system32\config\systemprofile\Local Settings\Temporary Internet Files\Content.IE5\CPMZ0DUR\desktop.ini" - skipped.
  Reason: Access is denied.

  WARNING: Could not open "C:\WINDOWS\system32\config\systemprofile\Local Settings\Temporary Internet Files\Content.IE5\KLY7W5UN\desktop.ini" - skipped.
  Reason: Access is denied.

  WARNING: Could not open "C:\WINDOWS\system32\config\systemprofile\Local Settings\Temporary Internet Files\Content.IE5\O1UF4L6Z\desktop.ini" - skipped.
  Reason: Access is denied.

  Backup completed on 20/05/2011 at 10:44.
  Directories: 12
  Files: 1
  Bytes: 1 031
  Time: 1 second

  ----------------------

  Check the status
  Operation: Verify after backup
  Active backup destination: file
  Active backup destination: J:\Test Sybil Backup.bkf

  Check the "C:".
  Backup set #1 on support #1
  Backup description: "Set created on 2011-05-20 at 10:43"
  Verify started on 20/05/2011 at 10:44.
  Check completed on 20/05/2011 at 10:44.
  Directories: 12
  Files: 1
  Various: 0
  Bytes: 1 031
  Time: 1 second

  ----------------------

  In looking at RSOP (resultant set of policy) shows that the local and domain administrator users have full control over these files. I tried this using the two connections to user with the same result.

  Any ideas anyone?

  Thank you

  Michael Salvaggio

  Hi MichaelSaffold,

  The question you have posted is better suited in the TechNet Forums. Please see the following link for more information.

  Category of the Windows Server

• HIT / ME for Dell EQL - this will improve line performance and capacity

  Hello

  I'm new to Dell EQL. Got a server running VMware ESXi 5.1 U1 executes a single virtual machine with Windows 2008 R2 and MS SQL 2008 R2.

  Tried the replication between the size of the replica EQLs has reached 500 MB to 1 GB despite the growth of the database per day is around 50 MB only.

  I read about a white paper, which suggests to use the direct storage. In short I will introduce a volume of the virtual machine directly via the Windows iSCSI initiator.

  In fact, I did already saw minimal improvement.

  Will install HIT / solve ME my problem of replication?

  What KEY / to ME in order to protect MS SQL?

  He is able to save only the changes to the SQL database and not these useless bits that are my replication problem...

  Thank you

  Paul

  Hello

  No. HIT / ME and VSM allow the creation of snapshots and much more consistent replicas.  Since the cached are flushed to storage before the process of creation.  HIT / VSM and I do very differentlly under the covers, but the end result is the same.

  HIT / the advantage ME in addition to work directly with SQL, Exchange, and SharePoint.  The HIT / ME docs have more information on the benefits of the use of HIT / me.

  Nor will affect the size of the replication. EQL table is a block storage device. The blocks are organized in large pages.  When you edit a page, the entire page is allocated.

• Computer performance are slow and unresponsive in the middle of the running applications

  Original title: Volsnap error, VSS, registry handle leaks, the drivers won't load is not etc.

  Little by little over the last few months, my computer has been slowing down, suddenly "not responding" in the middle of a program and a few other oddities.  I can't identify when this started because he was progressive.  I had to replace an old drive SSD C and when I did, I also bought a new copy of Windows 7 Prof 64 bit SP1.  Drive C is now SATA 6.

  Specs are adequate, CPU i7 930, 16 GB ram, 2 7200 1 TB WD drives each, 1 WD 'green' 2.5 SATA 6 GB, an Intel SSD SATA2 M225 and a Corsair Force SATA 6, which is the 'new' drive C.

  First mistake, as mentioned above is:
  Log name: System
  Source: volsnap
  Date: 28/08/2012-06:46:26
  Event ID: 8
  Task category: no
  Level: error
  Keywords: Classic
  User: n/a
  Computer: mg - PC
  Description:
  Flush and hold writes operation on E: has timed out while waiting for a written statement of the volume control.
  The event XML:
  
   
     
      8
      2
      0
      0 x 80000000000000
     
      131589
      System
      mg - PC
     
   
   
     
     
      E:
      000000000200300000000000080006C 0000000000000000005000000000000000000000000000000
   
  

  Following error, which is quite common VSS:
  Log name: Application
  Source: VSS
  Date: 27/08/2012-22:38:52
  Event ID: 12341
  Task category: no
  Level: WARNING
  Keywords: Classic
  User: n/a
  Computer: mg - PC
  Description:
  Volume Shadow Copy WARNING: VSS past seconds 0x000000000000002b try to rinse and keep the volume \\?\Volume{51e5830d-560c-4d2f-9ed8-343e5dbe5b8c}\.  This could cause problems when the other parts in the cliché of the time-out value for the phase of release-written, and it can cause the creation of snapshots to failure.  Try again when the disk activity is less can solve this problem.

  Operation:
  The execution of an asynchronous operation

  Context:
  Current status: flush and hold writes
  Volume name: \\?\Volume{51e5830d-560c-4d2f-9ed8-343e5dbe5b8c}\
  The event XML:
  
   
     
      12341
      3
      0
      0 x 80000000000000
     
      73849
      Application
      mg - PC
     
   
   
      0x000000000000002b
      \\?\Volume{51e5830d-560C-4D2F-9ed8-343e5dbe5b8c}\
     

  Operation:
  The execution of an asynchronous operation

  Context:
  Current status: flush and hold writes
  Volume name: \\?\Volume{51e5830d-560c-4d2f-9ed8-343e5dbe5b8c}\
      2D20436F64653A20434F524C4F564C4330303030303239302D2043616C6C3A20434F524C4F564C4330303030303233332D205049443A202030303030323632382D205449443A202030303030353532302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820
   
  

  Following error - register cast handles
  Log name: Application
  Source: Microsoft-Windows-user profiles Service
  Date: 30/08/2012 20:07:49
  Event ID: 1530
  Task category: no
  Level: WARNING
  Keywords:
  User: SYSTEM
  Computer: mg - PC
  Description:
  Windows detected your registry file is still in use for other applications or services. The file will be unloaded now. Applications or services that keep your registry file may not work properly thereafter.

  DETAIL-
  Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3328621373-938311138-4019764245-1001:
  800 (\Device\HarddiskVolume2\Windows\System32\winlogon.exe) process has opened \registry\user\s-1-5-21-3328621373-938311138-4019764245-1001-cles

  The event XML:
  
   
     
      1530
      0
      3
      0
      0
      0 x 8000000000000000
     
      74995
     
     
      Application
      mg - PC
     
   
   
      Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3328621373-938311138-4019764245-1001:
  800 (\Device\HarddiskVolume2\Windows\System32\winlogon.exe) process has opened \registry\user\s-1-5-21-3328621373-938311138-4019764245-1001-cles
  
   
  

  Next error - another problem of registry on the leak and be in use
  Windows detected your registry file is still in use for other applications or services. The file will be unloaded now. Applications or services that keep your registry file may not work properly thereafter.

  DETAIL-
  Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3328621373-938311138-4019764245-1001:
  800 (\Device\HarddiskVolume2\Windows\System32\winlogon.exe) process has opened \registry\user\s-1-5-21-3328621373-938311138-4019764245-1001-cles

  Last error I hope - system boot or boot startup failed to load drivers
  The next (s) starting or starting system could not load:
  UimBus
  Uim_IM
  Uim_VIM

  I apologize for this long post, but I thought that some of them might be related, and I'd appreciate any help I can get like this had been a machine very good and fast until the last month or two.

  33000

  Hello
  The three files that does not loaded at startup proved a Paragon backup facility that I had deleted.  I found in the registry and is more had this error.

  Slow and sudden episodes of "not responding" continues in safe mode, safe mode with network and boot.

  Mr. Fixit noted that I had too many programs loaded on startup that I already knew and will work hard to stop.  It has been useful in this gave me a list of the programs that did not need to start.  Some of this list was a distant base such that suggests my AV does not need to start, but some of it was useful.

  I then started to keep track of programs that seemed more likely to slow down or freeze the machine.  I reduced to one of my drives 3 1/2 inch WD 7200 and my 25 M Intel SSD.

  I ran Intel SSD toolbox and it showed no errors and no updates.  Estimated of life was about 95% and I had the car for 2 years.  There is an option to click that says "SSD Optimizer", and I suspect it is similar to a manual pad because it is one of their first records.  I "optimized" and it was immediately faster.  Intel said to do once a week or two and I never did.

  I ran HD Tune Pro on the WD and it showed a bad CRC so that a warning on the drive, which is less than a year. HD air said the drive is bad OR a cable is bad.  I had a backup, Acronis Disk which took most of the data and I also had the cloud with versioning backup.

  Knowing that the food had been replaced by a technician who had twisted power cables, because most of the readers had been asked in reverse, I attacked this first.  I turned every drive so that the connection of the power supply has been on the same side and reconnect the cable after doing my best to straighten out and flatten the wire.  I then installed a new SATA cable on the WD drive in question.

  Then, wanting to be done with it once and for all and ensuring that I could save between Acronis and my backup of cloud, I used the command line in Administrator, then to Drive E tools mode, error checking.  I ticked the boxes: analyze and attempt to recover bad sectors and automatically fix file system errors.  A reboot and the process had started.

  When you are finished, I seemed to have a catchy machine and some of the programs which often hung, is done in two days.  Programs were pretty much intact, but most of the files had been erased from the disk.  I have restored all wiped files and files of Acronis and the cloud and everything seems to work perfectly.

  Unable to help me, I ran HD Tune Pro and made a mistake (not fast) full scan on the E drive.  She came back without error.

  I know that this drive can fail again, and above all, I couldn't have been this aggressive if I had not had 2 backups.

  Do you think it will fail again?  I decided that, if so, I'll get another SSD (or two) to replace.  Although it will cost you much, I fear that hard drives are not very well made and I don't want to go through this again - and maybe not be so lucky.

  Thanks for your help and I'll post again if it fails in the near future.  Someone knows something about the new SSD Plextor?  Or would you go with Samsung?

  Thanks again.

• Cannot backup VMs to the NFS server

  Hi all

  really stuck GhettoVCB script configuration to back up virtual machines...

  I only have a single physical hard drive "datastore1" on my 6.0 ESXi host. I also have NFS server:

  
  

  /NFS

  IP address: 192.168.3.200

  First of all, I did a little test: I added this NFS server (file system is ext4) as a new 'teststorage' using vSphere Client storage. When I type in console

  # mkdir/vmfs/volumes/datastore1/somefolder

  # mkdir/vmfs/volumes/teststorage/newfolder

  everyghing is ok. Also:

  # esxcli storage nfs add h 192.168.3.200 v s/nfs/backup - backup

  # mkdir/vmfs/volumes/backup/tesfolder

  Well obviously, everything works. I so disassembled vSphere Client NFS.

  Next step, I tried to configure the script:

  VM_BACKUP_VOLUME = / vmfs/volumes/datastore1/autobackup

  DISK_BACKUP_FORMAT = thin

  VM_BACKUP_ROTATION_COUNT = 1

  POWER_VM_DOWN_BEFORE_BACKUP = 0

  ENABLE_HARD_POWER_OFF = 0

  ITER_TO_WAIT_SHUTDOWN = 3

  POWER_DOWN_TIMEOUT = 5

  ENABLE_COMPRESSION = 0

  VM_SNAPSHOT_MEMORY = 0

  VM_SNAPSHOT_QUIESCE = 0

  ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP = 1

  NFS_SERVER = 192.168.3.200

  NFS_MOUNT = / backup/nfs

  NFS_VM_BACKUP_DIR = auto save

  ENABLE_NON_PERSISTENT_NFS = 0

  UNMOUNT_NFS = 1

  SNAPSHOT_TIMEOUT = 15

  EMAIL_LOG = 1

  EMAIL_SERVER = mail. Core.local

  EMAIL_SERVER_PORT = 25

  EMAIL_DELAY_INTERVAL = 1

  [email protected]

  [email protected]

  VM_SHUTDOWN_ORDER =

  VM_STARTUP_ORDER =

  and they started with a command using SSH:

  # /ghettoVCB-master/ghettoVCB.sh g /ghettoVCB-master/my.conf f/ghettoVCB-master/my.list > /ghettoVCB-master/ghettoVCB14.log

  So, I got the following output:

  Recording output to ' / tmp/ghettoVCB-2016-03-31_04-34-07-3440436.log '...

  2016-03-31 04:34:07 - info: = ghettoVCB NEWSPAPER BEGIN =.

  2016-03-31 04:34:07 - info: CONFIG - CONFIGURATION GLOBAL GHETTOVCB = /ghettoVCB-master/kanon.conf FILE using

  2016-03-31 04:34:07 - info: CONFIG - VERSION = 2015_05_06_1

  2016-03-31 04:34:07 - info: CONFIG - GHETTOVCB_PID = 3440436

  2016-03-31 04:34:07 - info: CONFIG - VM_BACKUP_VOLUME = / vmfs/volumes/datastore1/autobackup

  2016-03-31 04:34:07 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 1

  2016-03-31 04:34:07 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2016-03-31_04-34-07

  2016-03-31 04:34:07 - info: CONFIG - DISK_BACKUP_FORMAT = thin

  2016-03-31 04:34:07 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0

  2016-03-31 04:34:07 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0

  2016-03-31 04:34:07 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3

  2016-03-31 04:34:07 - info: CONFIG - POWER_DOWN_TIMEOUT = 5

  2016-03-31 04:34:07 - info: CONFIG - SNAPSHOT_TIMEOUT = 15

  2016-03-31 04:34:07 - info: CONFIG - LOG_LEVEL = info

  2016-03-31 04:34:07 - info: CONFIG - BACKUP_LOG_OUTPUT = /tmp/ghettoVCB-2016-03-31_04-34-07-3440436.log

  2016-03-31 04:34:07 - info: CONFIG - ENABLE_COMPRESSION = 0

  2016-03-31 04:34:07 - info: CONFIG - VM_SNAPSHOT_MEMORY = 0

  2016-03-31 04:34:07 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 0

  2016-03-31 04:34:07 - info: CONFIG - ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP = 1

  2016-03-31 04:34:07 - info: CONFIG - VMDK_FILES_TO_BACKUP = all

  2016-03-31 04:34:07 - info: CONFIG - VM_SHUTDOWN_ORDER =

  2016-03-31 04:34:07 - info: CONFIG - VM_STARTUP_ORDER =

  2016-03-31 04:34:07 - info: CONFIG - RSYNC_LINK = 0

  2016-03-31 04:34:07 - info: CONFIG - BACKUP_FILES_CHMOD =

  2016-03-31 04:34:07 - info: CONFIG - EMAIL_LOG = 1

  2016-03-31 04:34:07 - info: CONFIG - EMAIL_SERVER = mail.core.local

  2016-03-31 04:34:07 - info: CONFIG - EMAIL_SERVER_PORT = 25

  2016-03-31 04:34:07 - info: CONFIG - EMAIL_DELAY_INTERVAL = 1

  2016-03-31 04:34:07 - info: CONFIG - EMAIL_FROM = [email protected]

  2016-03-31 04:34:07 - info: CONFIG - EMAIL_TO = [email protected]

  2016-03-31 04:34:07 - info: CONFIG - WORKDIR_DEBUG = 0

  2016-03-31 04:34:07 - info:

  2016-03-31 04:34:08 - info: power out put in place to

  backup will not start until the virtual machine is turned off...

  2016-03-31 04:34:08 - info: VM is powerdOff

  2016-03-31 04:34:11 - info: start the backup for Debian_Experimental

  2016-03-31 04:34:11 - info: creation of snapshot "ghettoVCB-snapshot-2016-03-31" for Debian_Experimental

  2016-03-31 04:34:12 - info: ERROR: bad DISK_BACKUP_FORMAT "thin".

  ------specified for Debian_Experimental

  2016-03-31 04:34:13 - info: Instant withdrawal of Debian_Experimental...

  2016-03-31 04:34:13 - Info: backup time: 2 seconds

  2016-03-31 04:34:13 - info: ERROR: Debian_Experimental could not backup because of the error in VMDK backup!

  2016-03-31 04:34:13 - info: # final status: ERROR: No. VMs saved! ######

  2016-03-31 04:34:13 - info: = ghettoVCB JOURNAL END =.

  2016-03-31 03:21:30 - info: # final status: ERROR: all virtual machines failed! ######

  2016-03-31 03:21:30 - info: = ghettoVCB JOURNAL END =.

  I tried:

  DISK_BACKUP_FORMAT = zeroedthick, eagerzeroedthick, thin, 2gbsparse

  VM_SNAPSHOT_MEMORY = 0/1

  VM_SNAPSHOT_QUIESCE = 0/1

  Still the same error in VMDK format.

  WM works fine, no damage.

  There is no no snapshot. VM version: 11

  Any ideas?

  Thanks in advance for the help.

  The solution was simple: my notebook + in Windows curled some symbols 'hidden' at the end of the first line, before that I sent this file via WinSCP.

  1. use only vi on your ESXi because different EOL codes (CR + LF/LF). Also don't let useful space and the end of the lines.

  2 set the async on your NFS server instead of synchronization that increases the speed of copy.

  3. place your script of ghettoVCB on your data store. For example: / vmfs/volumes/datastore1

  Hope this helps others.