About Pure Disk
Hi All, Kindly let me know the following few questions about pure disk. 1)what is pure disk? 2)About pure disk architecture? 3)About pure disk deduplication? 4)About pure disk web user interface? 5)Can i know the role of vssadminlist writers related to system state backup failures in pure disk.Solved3.8KViews3likes2Comments
Want to know the complete algorithm of upgrading Puredisk 6.5.1.2 to the latest version of 6.6
Hi All, Product in use: Veritas Netbackup Puredisk 6.5.1.2 v Installed on Suse linux: # uname -a Linux mpsc-pdisk01 2.6.16.60-0.31-smp #1 SMP Tue Oct 7 16:16:29 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/SuSE-release SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 1 # cat /proc/version Linux version 2.6.16.60-0.31-smp (gcc version 4.1.2 20070115 (SUSE Linux)) #1 SMP Tue Oct 7 16:16:29 UTC 2008 What are the precautions should I be taking? Can I directly upgrade from 6.5.1.2 to the latest version of 6.6? What is the latest version of 6.6? We are running SUSE Linux Enterprise Server 10 SP1 and PD 6.6.5 requires SP2. Since these PD servers were originally Symantec builds, does Symantec provide the SP 2 media? How long does the PureDisk server upgrade take? Do all tasks/services need to be stopped before/during the upgrade? Is there a specific sequence that we need to follow (e.g. PD source server, PD clients, PD target server)? How long does the client upgrade take and how resource intensive is it on the client (should we be concerned about impacting the clients during the middle of their business day)? Can all of the client upgrades be pushed out at the same time or is it recommended to only do several (count?) at a time? If we upgrade the servers during the day (when no backups are running), can the agents (old version) still back up to the upgraded servers (in case we can't upgrade all of the clients in one day)? What will be the impact of PD server upgrade on the agents/clients which are connected to it? Should I have to worry about compatibility issue? Are there any compatibility criteria? Please help. Thanks & Regards, Rizwan1.5KViews0likes0Comments
Puredisk Hardware Migration
The current environment consists of two all-in-one servers running Netbackup Puredisk 6.5.1.2. Server 1 replicates to Server 2. New hardware (Server 3) has been purchased to replace Server 1. What is the easiest way to do this? Someone once told me that you could enable replication from Server 1 to Server 3 and then make that the primary server. The clients would then have to be updated to point to the new server. Is it really this simple? If so, then how do I migrate the data selection templates and workflows (backup policies)? Also, my understanding is that it's better to install 6.5.1.2 on Server 3 before upgrading to 6.6.1.Solved1.3KViews0likes10Comments
After upgraded to Puredisk 6.6.4 backups stuck at 52 percent complete
Hi, I upgraded my Puredisk server from 6.6.3 to 6.6.4 because of some backups in error, nut now all my backup stuck after 52 percent complete? Job steps : "Import PO-List on the MetaBase Engine" The end of the job log *** Supportability Summary *** jobid = 20172 jobstepid = 81567 agentid = 27 hostname = SMXP002 starttimejobstep = 2012-Dec-26 11:09:32 CET endtimejobstep = 2012-Dec-26 11:10:05 CET workflowstepname = Data Backup status = SUCCESS [2012-Dec-26 11:10:06 CET] *** Start: MBImport *** ???1.1KViews0likes6CommentsMove /Storage to new Disk volume @ Puredisk 6.5 Linux Suse (PDDO)
Hi All, I have environment like this, and need best solution for this scenario. Puredisk Server has external disk (i have already use 6 slot from 12 slot). Totally existing 2 TB diskpoll for PD server. And now /Storage status is Full. We need increase this /Storage up to 4 TB. What the best solution for this scenario ? if ..... 1. Add new disk volume up to 4 TB using YAST or 2. Migrate old disk puredisk Server to new disk volume (replace to bigger disk volume) 3. Any other solution .... Please send me the best solution and step by step ? Many thanks. Regards, Ahmad1.1KViews0likes5CommentsIs there a way to speed up MSDP startup?
I am in the process of upgrading my NetBackup environment from v7.1.0.4 to v7.5.0.5. Master server on Linux is done as are some of my Linux based media servers. I am now starting on my Windows 2008 based MSDP servers with one done so far. However, I find that the bpup -v command on Windows is now taking significantly longer; seems like it now stops on the Deduplication engine (spoold) startup whereas before it didn't. It is as if it now waits for the cache load to finish before proceeding on. With a 15TB volume to load this is taking 1.5 hours or so minimum. I recall reading somewhere about the change in startup but am unable to find anything now. Is this normal now? I also find that the disk pool doesn't come online at all after startup; I have to issue a nbdevconfig -changestate -stype PureDisk -dp Dedupe-Pool -dv PureDiskVolume -state RESET command from the Master Server to get the pool back online; a simply UP doesn't work either. Symantec are looking at this fom me. Anyone have any comments or suggestions?1KViews0likes6Comments