ASM backup strategies with SAN snapshots

Hello folks,
in one of our setups we have a database server (11.2) that has only binaries and config (not the datafiles) and all ASM disks that are on the SAN. The SAN has daily snapshots, so the datafiles are backed up. My question is, how do I proceed if the database server fails and needs to be reinstalled? My question is how do I tell to the grid that we have already a diskgroup with disks on the SAN. I found md_backup and md_restore, but I am not sure how / when to proceed with md_restore.
I have searched some time, but I am quite confused with the approaches, please note that RMAN is not an option in this environment.
Thanks in advance
Alex

Hi,
O.k. that changes things. You should have mentioned that in the beginning of your post, that you shutdown the database before you doing the snapshot and your are not using archivelog mode.
I would advise to also dismount the diskgroups before doing the snapshots.
However when was the last time you tried the archivelog mode? 11g increased the performance a lot.
Note: In this case the snapshot is only a point in time view. In case of an error, you will loose data. (The last hours from your last snapshot).
Now regarding your questions:
=> You will install a new system with GI and database software. You will need a new diskgroup (e.g. INFRA) for the new OCR and Voting disks (they should not be contained in the other diskgroups like DATA and FRA, so no need to snapshot the old INFRA).
=> Then simply present the LUNs from DATA and FRA diskgroup to the new server. ASM will be able to mount the diskgroups as soon as all disks are available (and have the right permission). No need for md_backup or restore. MD_BACKUP backups the contents of the ASM headers, but since you still have the disks this meta information is still intact.
=> Reregister the database and the services with the Grid Infrastructure (srvctl add database / srvctl add service etc.). Just make sure to point to the correct spfile (you can find that e.g. with ASMCMD).
=> Start database...
That is if your snapshot did work. Just have another forum thread, where a diskgroup got corrupted due to snapshot (luckily only FRA).
And just as reminder: A snapshot is not a backup. Depending on how the storage is doing the snapshot, you should take precautions to move it to separate disks and verfiy it (that it is usable).
Regards
Sebastian

Similar Messages

VSS snapshots for DPM 2010 Hyper-V backup conflict with SQL backup on a virtual SQL server

We currently use DPM 2010 to backup our virtual servers which reside on a 5 node Hyper-V clustered share volume. DPM uses the hardware VSS writer to backup the Hyper-V guests. Several of these Hyper-V guests are SQL servers (SQL 2008) and they
are all configured to run point in time SQL backups using SQL Management Plans.
The SQL backups are scheduled to run a full database backup on a Friday and differential backups on the other days of the week. Transaction backups are scheduled to run several times throughout the day.
However we have recently discovered that there is a conflict between these two methods as it seems as though when a restore is required using a differential SQL backup, it fails as the snapshot created by DPM forces SQL to believe it has had a full backup
carried out externally from the Management Plan and is therefore unable to perform the restore.
DPM backs up the Hyper-V guests on a daily basis from 8pm.
Can anyone provide any advice or guidance on this as we need both types of backup to run successfully. We are required to backup SQL with point in time backups and we also need to protect the Hyper-V guests in their entirety.

Thanks Mike,
I have tried this but unfortunately it has no effect. The VM has Oracle installed (although not the Oracle VSS Writer). It is the Oracle application server, not the database server, and the customer has a script that is used to stop and start
the Oracle application when required. Through troubleshooting this with them I have noticed that after the WLS_Reports service/process is stopped the backups run successfully but when it is running the backups fail.
I have also noticed that when I stop the Hyper-V Volume Shadow Copy Requestor the backup runs successfully, which I guess is as expected.
When the backups fail I get 2 errors in the application log:
Event Id 12293, VSS - Error calling a routine on a shadow copy provider {GUID for the Hyper-V IC Software Shadow Copy Provider}. Routine details PreFinalCommitSnapshots ({GUID}, 5) [hr = 0x800705b4, This operation returned because
the timeout period expired.]
Event Id 19, vmicvss - Not all the shadow volumes arrived in the guest operating system.
This is also part of the same problem I have posted here: Backup
fails for a Hyper-V guest with VSS Writer failures using DPM 2012 R2 - Hyper-V guest has Oracle application installed
Regards
Chris

SAN Snapshots

Does anyone know if SAN snapshot technology can be used with Oracle Databases
The 10gR2 Backup and Recovery Advanced User Guide seems to have a chapter ( CH17 ) that covers User Managed Backups which I am guessing where SAN snapshot technology would fit in ?
What I am trying to ascertain is -
1. Can SAN snapshot be used to backup a database if it is open and online ? - do you need to put the database into backup mode ?
2. Is is better to use SAN snapshot in combination with Hotbackup so you are purely snapshotting the backup itself and not directly the database ?
3. What the difference between SAN snapshot of an open database and hotbackup ?
4. What are the industry common SAN Snapshot solutions used with Oracle ?
thanks,
Jim

1. Can SAN snapshot be used to backup a database if it is open and online ? - do you need to put the database into backup mode ?yes & yes
2. Is is better to use SAN snapshot in combination with Hotbackup so you are purely snapshotting the backup itself and not directly the database ?HUH?
3. What the difference between SAN snapshot of an open database and hotbackup ?A HOTBACKUP will allow a consistent restore to be done.
A SAN Snaphot is a waste of effort.
4. What are the industry common SAN Snapshot solutions used with Oracle ?It depends

Backup strategy with no tape drives/library

Hi, I am new into the job of sys admin, so we recently setup a system with running solaris 10 and with its storage as a NetApp, but we do not have yet a library or tape drive attached to it.
So how can I approach this problem? Can I setup a LUN on NetApp and copy all important stuff to that LUN?
FR

For the oracle backup, oracle should have comands to dump or export the database to a file, and that file could be backed up. Alternately, there are problably options to put the database in read-only mode, so that you can back up the database files without worrying that they will be changed during the backup.
For other files, if you are using zfs snapshots, you could back up the zfs snapshots even if the original file is still open.
You might also want to look at the rysnc command- that should let you back up only files that have differ between the source and destination (i.e. you could do differential backups.) So maybe you could a monthly full backup with tar to NAS or SAN, a weekly rsync incremental backup, and daily zfs snapshot that is kept for a week.

2008 R2: OS(systemState/C: Drive) backup issues with VSS - 0x80042316 & 0x81080101 & 0x80080005 & 2155348001

Hi-
Looked thru the thread related to my questions and found nothing that applies yet.
Example:
http://social.technet.microsoft.com/Forums/en-US/4e4472b9-8e6f-4fdc-a287-1cc8c0f6de09/windows-2008-r2-backup-fails-with-event-521-error-code-2155348001?forum=windowsbackup
http://social.technet.microsoft.com/Forums/en-US/e8c910f7-f0dd-4613-beae-b98894fb6f23/windows-server-2008-std-backup-fails-constantly-with-error-code-2155348001?forum=windowsbackup
Here are details of the issues....
Backup - OS error - system image:
External disk - USB
Mon - Fri @ 6PM.
Windows SystemState
OS(C:)
Last backup failure...
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
[Critical error WINIMAGE_UNABLE_VSS] Unable to create VSS snapshot
- Additional information: Refer to the log for more details
- Troubleshooting link:
http://kb.backupassist.com/errormap.php?BA2512
The backup operation stopped before completing.
Detailed error: ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-12-08-2014_04-41-00.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-12-08-2014_04-41-00.log
NOTE:
The errors logs are not there?
Windows Backup timed-out before the shared protection point was created.
ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Event Viewer Log:
Sequence of Events...
1.
The Block Level Backup Engine service has successfully started.
2.
Backup operation that started...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 4:51:06 AM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The backup operation that started at '?2014?-?08?-?12T09:41:00.492000000Z' has failed because the
Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed
with following error code '2155348001'.
Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
--> Suggestion are to check Virus scanner or consult DPM forum...
3.
OS Job failed with errors...( Backup Assist is 3rd party backup - wrapper round Wbadmin/Win Backup)
Log Name:      Application
Source:        BackupAssist
Date:          8/12/2014 4:51:51 AM
Event ID:      5634
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Backup job OS backup failed with errors.
Critical error: Unable to create VSS snapshot
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
4.
Backup Assist reports via Win backup - Snapshot in progress
Log Name:      Application
Source:        BackupAssist
Date:          8/12/2014 4:52:20 AM
Event ID:      5634
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Backup job Data backup failed with errors.
Ultra critical error: Volume Shadow Copy Error 0x80042316 - snapshot set in progress
Destination: Local directory
Start time: 8/12/2014 4:52:10 AM
End time: 8/12/2014 4:52:12 AM
Duration: 00:00:02.7300000
5.
The Block Level Backup Engine service has stopped.
6.
Later...we tried manually stopping VSS and SWPRV services - only VSS had the issue.
WBengine was not running...
C:\>sc stop swprv
SERVICE_NAME: swprv
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query swprv
SERVICE_NAME: swprv
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 1 STOPPED
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query wbengine
SERVICE_NAME: wbengine
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 1 STOPPED
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query vss
SERVICE_NAME: vss
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc stop vss
[SC] ControlService FAILED 1061:
The service cannot accept control messages at this time.
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:20:33 AM
Event ID:      8225
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
The VSS service is shutting down due to shutdown event from the Service Control Manager.
7.
VSS still having issues here...not stopping!
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:42:33 AM
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service information:
The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started.
Most likely the CPU is under heavy load. [0x80080005, Server execution failed]
8.
Not sure why this is started again?
Plus a DCOM timeout...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 9:31:13 AM
Event ID:      753
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has successfully started.
Event Xml:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          8/12/2014 9:31:43 AM
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
The server {E579AB5F-1CC4-44B4-BED9-DE0991FF0623} did not register with DCOM within the required timeout.
9.
Lots more errors about VSS...repeating Event ID's 11 and 8193...
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:42:33 AM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
hr = 0x80080005, Server execution failed
. Operation:
   Instantiating VSS server
10.
Then, finally stopping again...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 9:51:13 AM
Event ID:      754
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has stopped.
11.
And still repeating 11 & 8193 at this point...as we write up this post.
12.
This was suggested by the Backup Assist - software vendor....
A.)
...for 0x81080101:
"ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try again this operation."
If you receive the above error in your report, we have recently found a registry key which
contains the timeout value set by Microsoft for VSS and found that you can edit this to extend it.
To get to the registry key, open Regedit (Start > Run > Regedit) and browse to:
"HKLM\Software\\Microsoft\\Windows NT\\CurrentVersion\\SPP\\CreateTimeout".
Change value to 1200000 (2*10*60*1000 = 20 mins).
The default for the timeout period is 10 mins so hopefully doubling this will give enough time to
complete the snapshot.
If this isn't present, you'll need to manually enter the registry key. It's a DWORD 32-bit key.
--> NOTE: HAve not done this yet.
B.)
And for 0x80080005...
http://support.microsoft.com/kb/870655/en-gb
Our server does have high CPU load at times...
13.
Another post from technet mentions system volume size - here is our layout below:
A.)
OS/system Disk...
DISKPART> list disk
Disk ### Status         Size     Free     Dyn Gpt
Disk 0    Online          278 GB      0 B    (System Vol = C: Drive - OS w/ Programs and batch jobs)
Disk 1    Online         2791 GB      0 B        *    (Data drive - DFS, rsync,etc. run on D: Drive)
Disk 2    Online         1863 GB      0 B    (USB 2/3.0 - Enclosure w/ SATA disk = 2GB formatted w/ NTFS.)
DISKPART> detail disk
DELL PERC H710P SCSI Disk Device
Disk ID: CA0DEEA5
Type   : RAID
Status : Online
Path   : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0100)#PCI(0000)#RAID(P01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 1         RECOVERY     NTFS   Partition   3072 MB Healthy    System
Volume 2     C   OS           NTFS   Partition    275 GB Healthy    Boot
B.)
Backup disk...
ST320006 41AS USB Device
Disk ID: 801AF48C
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 4     F   BACKUPS      NTFS   Partition   1863 GB Healthy
C.)
NOTE:
Also on disk 0(system Disk) - we have a small OEM partition = 39MB and a Recovery Partition = 3GB.
D.)
Issues with WBAdmin now...
C:\>wbadmin get disks
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
ERROR - A Volume Shadow Copy Service operation error has
occurred: (0x80042302)
A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
14.
Ran "Check-Disk" -no errors...
C:\>chkdsk
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
116224 file records processed.
File verification completed.
654 large file records processed.
0 bad file records processed.
0 EA records processed.
76 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
156676 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
116224 file SDs/SIDs processed.
Security descriptor verification completed.
20227 data files processed.
CHKDSK is verifying Usn Journal...
35628352 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
289233919 KB total disk space.
100241492 KB in 85477 files.
     57380 KB in 20228 indexes.
         0 KB in bad sectors.
    226627 KB in use by the system.
     65536 KB occupied by the log file.
188708420 KB available on disk.
      4096 bytes in each allocation unit.
72308479 total allocation units on disk.
47177105 allocation units available on disk.
15.
There are no backup error logs here - only .etl files...
C:\Windows\Logs\WindowsServerBackup\
Wbadmin.1.etl = 9:42AM on 8/12
Wbadmin.2.etl = 4:51AM on 8/12
Per windows Win troubleshooting:
http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
--> Related to Windows backup and not VSS?
2155348001 - 0x80780021 - Windows Backup timed-out before the shared protection point was created.
Should we run the "FIXVSS08.BAT" script - restarts services and re-registers DLL's - does this ever help?
Will this server need a reboot since VSS is in a state and we can't even test backups?
Is there a tool we can use to debug VSS or troubleshoot or OS backups further?
MSReport/Diag, VSS debugging, or another way of helping fix our OS(SystemState/C: drive) backup issues?
Any help is greatly appreciated - thx.
-SP
Scot Pichelman

Hi Scot,
Sometimes a third party backup application will change the default VSS provider adding VSS writers which causes Windows Server Backup using an incorrect component in doing backup, that's why I suggest to delete it for a test. Anyway you can reinstall it
after testing.
And as you said a high-load CPU could also be the cause of the issue so you may need to first rule hardware effective out.
If issue still exists, please try the steps below as well:
1. Please check DCOM Server Process Launcher service is started.
2. If not, try to change RPC service to run as SYSTEM account. To do this please modify the following key:
Note: Backup the key before edit incase it cause any issue.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\RpcSs\
Find "ObjectName" and change the value to LocalSystem.
Reboot to see if DCOM back to work and if Windows Server Backup starts working. If not, please provide the result if there is any new error occurs.
If DCOM still not work, please compare the content of the following key with a working server:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
Edit if there is any difference and make sure you created a backup of the key before editing.
If you have any feedback on our support, please send to [email protected]

Backup failed with Error: (-50) Creating Directory

Repeats ad nauseum.
This is backing up to a second internal drive that is an exact duplicate (in terms of HD model and size).
Does anyone know what Error -50 means? Lack of permissions? Invalid name (doesn't seem like it)?
8/30/08 9:06:37 AM /System/Library/CoreServices/backupd Starting standard backup
8/30/08 9:06:37 AM /System/Library/CoreServices/backupd Backing up to: /Volumes/Sliffy Time/Backups.backupdb
8/30/08 9:06:58 AM /System/Library/CoreServices/backupd Error: (-50) Creating directory 2008-08-30-090658.inProgress
8/30/08 9:06:58 AM /System/Library/CoreServices/backupd Failed to make snapshot container.
8/30/08 9:07:03 AM /System/Library/CoreServices/backupd Backup failed with error: 2

Hi Glenn,
Thanks for the suggestion. Nope, it's not listed. The only thing listed is my Time Machine volume.
After a reboot, Time Machine seems to be working. It's making backups on schedule and the logs look good, not reporting any strangeness.
A bit bummed about these phantom errors that go away on reboot. I'll keep on eye on the error/reboot frequency.
Rob

Data Backup Strategies in SAP

HI ALL,
What are some of the different ways of backing up SAP Data?

HI,
There are many backup strategies for SAP.
1) If you can shutdown your server at night, you can take an offline database backup with redo logs.
2) If your server needs to remain on all 24 hrs, you can take an online backup with redo logs.
3) Once in 15 days or a month, you can take an O.S. level backup.
Also devise a strategy to keep a copy of backup at a different location and follow it. There should be at least one copy of O.S. Level backup at any other location other than your office premise.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

I'm wondering about bootable backup strategies

I'm wondering what people use and recommend for backup strategies, and especially the utility of "bootable" backups.
I have an early-2011 15" MBPro, running fully updated Yosemite. My computer is apparently one of the "victims" of the recently publicized graphics system problems that has resulted in Apple's recent out-of-warranty repair offer for machines in this category. Over the past 10 months my machine has been in for repair 4 times, resulting in the replacement of my display, main logic board (x 3!!) and hard drive. These 4 repairs were the result of incidents that started with the screen graphics going crazy and ending, eventually, in an un-bootable state. Two of the 4 times I was returned a working machine with a clean new-install of OS 10. (all "free" I might add, thanks to still being on Apple Care when the whole process started!) Hopefully, my last repair will "do the trick" as it was AFTER Apple's announced repair offer for these machines. My Apple Store "genius" opined that this time my main logic board was probably an "improved" item, since the first two replacements didn't solve the problem.
So twice in the recent past I have had to completely restore my machine from my Time Machine (to Time Capsule) back-up. Both successful, thankfully! But this experience has focused my attention very sharply on my backup strategy, and made me wonder how "exposed" one still might be with "just" a Time Machine backup.
Talking informally with several more knowledgeable and experienced "Mac" people that I know, I discovered that many people don't rely on Time Machine, at least not solely. I was persuaded that the really most secure situation is to have a second back-up, preferably a bootable "disc image," stored on a separate device (and maybe preferably off site).
So, I've been looking into the options, services, etc.. There are MANY! I love the ease, automaticity and utility of having a Time Machine back-up. But I'm wondering, for those (probably few) out there that do something MORE than that: what back-up strategies do you use? Is is POSSIBLE to have a "bootable" backup on an online/cloud device (maybe not)? What systems work well and are complementary/supplementary to Time Machine?
I know, from my own experience, that HAVING a backup is fairly easy. But I've also learned that RESTORING a backup (mine's around 400 GB) is NOT "easy", at least very time consuming, and probably fraught with potential problems which won't appear until it's too late to do something else! So I'm particularly looking at the restoration features of backup software and services. Frankly, those are often largely ignored in the promotions, which mainly focus on how easy it is to DO the backup but never talk much about doing the restore!!
Any and all opinions are welcomed. I am definitely considering some redundancy in my backups after "dodging the bullet" twice in the last 3 months!

... how "exposed" one still might be with "just" a Time Machine backup.
Just one backup isn't enough. Two or more are preferable. Time Machine can back up to as many external devices as you wish. Purchase two or more inexpensive USB hard disk drives and store one of them offsite at all times. Time Machine will back up to each one "in rotation" when they're available. If the backup device it's expecting isn't available, it looks for the next one, etc.
If you want to augment Time Machine with another backup strategy, consider "clone" software such as Carbon Copy Cloner. It will create bootable copies of your existing installation if you consider that a valuable option.
"Bootable" is fine but not really necessary. Consider the possibility in which it's impossible to boot your Mac for whatever reason, or if should happen to be lost, stolen, or irreparably damaged. Consider the circumstances applicable to the way you use your Macs that might cause that event. If your disaster recovery plan addresses that contingency, it's a good plan. Recovering 400 GB is going to be time consuming no matter what method you use. An external HDD with a Thunderbolt interface would be fastest, followed by USB3, followed by USB2, followed by a directly connected (Ethernet cable) Time Capsule, followed by a wireless Time Capsule — for which a TM restoration might take an unacceptable amount of time (days).
Obviously I don't know the circumstances of the repairs you required, but I question the necessity to replace the hard disk. It's possible the same one could have been re-used, saving you the inconvenience of having to perform a restoration.

Recover a specific backup from backup history with dbmcli

hello friends,
how can i recover a specific backup from backup history with dbmcli with inizialization. in dbmcli i can only find methods for medium recovery. with dbmgui i try "instance" in menu, then "Recovery with Initialization", then i try i choose admin_state, then i choose the radiobutton recover from backup history. I get my choice with specific date.
How can I build a script in dbmcli for this scenario. when i am try the command backup_history_open and backup_history_list i cant see the specific backup, what i see in dbmgui.
the backup history item, that i need has a specific system key "492FB68F0002". with which dbmcli command i get this system key for recover.
which command i take for this scenarion db_activate RECOVER?
many thanks for suggestions,
christoph

> how can i record the staments for my script?
Do you know the "show console" feature in DBMGUI/DB Studio?
With that you can display all commands used by DBMGUI and the Recovery Wizard.
> I am looking for an automatism to recover an instance from a specific item from backup history, because we test ower deliverys with import in stms - see return codes.
Ok, but why do you need a recovery for that?
Use SNAPSHOTS instead (read the docu [here|http://maxdb.sap.com/doc/7_7/44/c4afa67ca22e17e10000000a114a6b/content.htm]!).
Create your base instance.
Create a SNAPSHOT.
Now run your tests.
When you finished your tests, simply restore the SNAPSHOT.
This takes seconds.
Bring the database online again and run some new tests.
When you want your initial instance again - just restore the SNAPSHOT once again.
Really, SNAPSHOTs are made for such a scenario.
> content for script:
>
> 1. stopsap r3 in sidadm context
> 2. db_admin of instance in dbmcli context
> 3. recover a specific item from backup history from nfs mount in dbmcli context
> 4. restartable check in dbcmcli context
> 5. restart instance in dbmcli context
> 6. logmode to overwrite in dbmcli context
> 7. db_offline in dbmcli context
> 8. startsap all in sidadm context
Ok. if you still would like to do it this way... how about this:
dbmcli -U c -i refresh_db.txt
refresh_db.txt:
==============
db_admin
db_activate RECOVER <medium_name> DATA AUTOIGNORE
db_online
db_execute SET LOG AUTO OVERWRITE ON
db_offline
I leave the stopsap/startsap and the rest of the script to you, but I guess you got the idea.
BTW: there's no need to check for restart ability of the database after the recovery since by definition all full data restores are restartable with MaxDB!
So have fun (and go for the SNAPSHOTS instead!).
regards,
Lars

Backup rserver with sticky configured

Hi,
I would like to ask regarding the configuration for the backup rserver with sticky configured.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:SimSun;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
This is not documented in the Cisco guides.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:SimSun;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Suppose the real server1 fails and connections are diverted to server2. Then server1 resumes service. What happens to existing connections on server2 and the new connections?
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:SimSun;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
serverfarm SFARM1
rserver SERVER1
backup-rserver SERVER2
inservice
rserver SERVER2
inservice standby

- Existing connections keep accessing server2.
- If a new client request (connection) matches a sticky entry for server2, ACE forwards this request to server2.
ACE looks up sticky entries and use server2 since standby state is handled as UP.
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/rsfarms.html#wp1000385
- If a new client request (connection) doesn't match any sticky entry for server2, ACE forwards this request to server1.
If you want to use server1 after coming back OPERATIONAL, I recommend you use 'backup serverfarm' without sticky option as below.
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/sticky.html#wp1137791
serverfarm SFARM1
rserver SERVER1
inservice
serverfarm SFARM2
rserver SERVER2
inservice
sticky ip-netmask 255.255.255.255 address both sticky_ip
serverfarm SFARM1 backup SFARM2
The following is a test result of standby rserver and sticky ip.
ACE20a/Admin# sh rserver
rserver              : sv1, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.11:0       8      PROBE-FAILED 0          2
rserver              : sv2, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.12:0       8      OPERATIONAL 0          8
ACE20a/Admin#
!___ access from client to ACE vip
ACE20a/Admin# sh sticky database
sticky group : sticky_ip
type         : IP
timeout      : 1440          timeout-activeconns : FALSE
sticky-entry          rserver-instance                 time-to-expire flags
---------------------+--------------------------------+--------------+-------+
13882423967172020068 sv2:0                            86384          -
!___ ACE learns client address and registers the entry
ACE20a/Admin#
ACE20a/Admin# sh rserver
rserver              : sv1, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.11:0       8      OPERATIONAL 0          2
!___ return OPERATIONAL
rserver              : sv2, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.12:0       8      STANDBY      0          9
!___ return STANDBY
ACE20a/Admin# sh sticky database
sticky group : sticky_ip
type         : IP
timeout      : 1440          timeout-activeconns : FALSE
sticky-entry          rserver-instance                 time-to-expire flags
---------------------+--------------------------------+--------------+-------+
13882423967172020068 sv2:0                            86356          -
!___ ACE keeps sticky entry to server2.
ACE20a/Admin#
!___ access from client with new syn packet
ACE20a/Admin# sh sticky database
sticky group : sticky_ip
type         : IP
timeout      : 1440          timeout-activeconns : FALSE
sticky-entry          rserver-instance                 time-to-expire flags
---------------------+--------------------------------+--------------+-------+
13882423967172020068 sv2:0                            86389          -
!___ use this sticky entry (time-to-expire flag is reset) and send packets to server2
ACE20a/Admin#
ACE20a/Admin# sh ver | i image
system image file: [LCP] disk0:c6ace-t1k9-mz.A2_3_1.bin

Not getting option to Backup Using Child Partition Snapshot DPM 2012 R2

I am running DPM 2012 R2 fully patched.
I am trying to use Backup Using Child Partition Snapshot of a Hyper-V Server 2012 R2 Datacenter Cluster using CSV.
I get no option to use Backup Using Child Partition Snapshot, just online backup.
I have gone through the steps in the Microsoft document "Configure CSV Backups"
http://technet.microsoft.com/en-us/library/hh758027.aspx (Some steps did not apply due to my not using Windows 2008 R2)
Has "Backup Using Child Partiton Snapshot" been replaced by "\Online\VMName" ?
What am I missing?

Hi,
Yes, Windows server 2012 R2 has changed the caption from "Backup Using Child Partiton Snapshot" to "\Online\VMName" - DPM is displaying the new caption when protecting Windows Server 2012 R2 guests.
MORE INFORMATION
To list Windows 2012 R2 hyper-V writer captions for guests to see if online or offline state backups will be done:
From an administrative command prompt on the Hyper-V server:
a. Type: copy con script.txt and press enter
b. Type: list writers and press enter
c. Press CTRL + Z + enter (to save)
d. Type: diskshadow /s script.txt | find /i "caption: O"
Output will be displayed for each guest as follows.
C:\temp>diskshadow /s script.txt | find /i "caption: O"
- Caption: Online\SQLSERVER
- Caption: Offline\WSS-V14
The Windows 2012 R2 Hyper-V writer adds the VM in the following format:
For offline backups: Offline\<VMName>
For online backups: Online\<VMName>
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

Time Machine Backup Failed with error: 2

I have been doing unattended continuous backups to a 1 TB drive for about 4 months via Time Machine. In the last 2 months I have been getting a dialog box with this message: "Unable to complete backup. An error occurred while creating the backup directory." In each case I have gone to Disk Utility to repair the disk, and each time have had to reboot to get the Repair Disk function to work, since without a reboot, the backup disk won't unmount. After repair, the backups resume, but the frequency of the failures is beginning to worry me. I never had problems with scheduled SuperDuper backups and am thinking of returning to that approach, albeit different.
Below is what is listed in in the system log after the backup failure. It lists "error: 2", whatever that is.
The backup disk has over 400GB space remaining.
Can anyone help me with this?
May 2 19:34:17 Macintosh /System/Library/CoreServices/backupd[12497]: Backup requested by user
May 2 19:34:17 Macintosh /System/Library/CoreServices/backupd[12497]: Starting standard backup
May 2 19:34:26 Macintosh /System/Library/CoreServices/backupd[12497]: Backing up to: /Volumes/WD1TB Backup Disk/Backups.backupdb
May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Error: (-50) Creating directory 2008-05-02-193428.inProgress
May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Failed to make snapshot container.
May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Backup failed with error: 2
Thanks,
Art

Betty - actually, no. Rebooting alone didn't resolve the problem. Time Machine still wouldn't resume backups.
Once the directory was rebuilt via Disk Utility, it is up and running again, at least for a while.

Time Machine backup fails with error 2

trying to run a backup for the first time on a new external hard-drive but backup fails to complete. Any suggestions?
Starting standard backup
Backing up to: /Volumes/FreeAgent GoFlex Drive/Backups.backupdb
Failed to create progress log file at path:/Volumes/FreeAgent GoFlex Drive/Backups.backupdb/Jones’s iMac (3)/2011-11-24-170759.inProgress/.Backup.343882684.814583.log.
Event store UUIDs don't match for volume: Macintosh HD
Error: (-50) Creating directory 6A3DF5C4-679A-4FBE-A116-218CE389908A
Failed to make snapshot.
Backup failed with error: 2

I too am having multiple problems with time machine for a couple of weeks now, however this is not my first backup. I have been using TM for over 2 years, and these are new problems. This is the last error message:
Starting standard backup
Backing up to: /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb
Failed to create progress log file at path:/Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/.Backup.344169198.317667.log.
Event store UUIDs don't match for volume: Mac 2
Event store UUIDs don't match for volume: Mac 1
Error: (-50) Creating directory 0A89DB49-A127-4ECE-8E98-65C5393BC268
Failed to make snapshot.
Backup failed with error: 2
The above came after permissions repair & disk repair. Before the messages were mostly:
Error: (-50) SrcErr:NO Copying /Applications/Font Book.app to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/E0326568-C860-4A3F-888D-9840DFF72832/Mac 1/Applications
Error: (-50) SrcErr:NO Copying /Applications/Front Row.app to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/E0326568-C860-4A3F-888D-9840DFF72832/Mac 1/Applications
Error: (-50) SrcErr:NO Copying /Applications/Full Key Codes to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-
With a whole string of different applications with the same error, then ending with:
Error: (-43) SrcErr:NO Copying /User Guides And Information to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-1407) SrcErr:NO Copying /Users to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-43) SrcErr:NO Copying /usr to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-1407) SrcErr:NO Copying /Volumes to (null)
Formulating crash report for process backupd[960]
Any help/suggestions out there ??

Practical question: How to transfer ASM backup files?

Hi friends:
A practical question:
all dev, production database using ASM for storage, production db using RMAN did full backup. (everyday night, one copy redundancy)
For example, production database is down, then in short time, it is hard to repaire back online, then, I want to transfer ASM backup files(sets) to dev database, make dev as a quick temporary production db.
question: how can you find full backup sets (location) and how to trasnfer?
thanks a lot in advance.
Message was edited by:
jerrygreat

You can find backupsets by using the
list backupset
command
and you can transfer them using the
backup backupset command.
Both commands are fully documented in the RMAN documentation for 10g.
Please read it.
Obviously changing a dev database into a production one has little to do with proper backup and recovery procedures.
Sybrand Bakker
Senior Oracle DBA

Can we schedule backup of cisco san switch 9148 through windows backup utility.

can we schedule backup of cisco san switch 9148 through windows backup utility.

sure, you can write a batch/perl/powershell/whatever script that will connect to your switch and then backup the configuration. You need to decided where you are going to back it up to, possible options include TFTP, SCP, FTP, SFTP. For example i am backing to a TFTP server, my perl script connect to the switch and runs this command:
copy startup-config tftp://tfpserver-ip/mds9513.$(TIMESTAMP).config
TIMESTAMP is actually a built-in variable that will be replaced with the date/time configured on the switch.

ASM backup strategies with SAN snapshots

Similar Messages

Maybe you are looking for